Privacy policy

The data controller is de.load coaching. For matters concerning personal data, write to [email protected].

Full registration details and a postal address will be added here before the app launches.

A coach gives their name, email address and city (required), and optionally a phone number and specialisation. A client gives an email address and city, optionally a first name. We collect no payment card details and no health data at the sign-up stage.

This concerns the sign-up on this site. The de.load app itself collects more — including health and fitness data — and sections 8–13 describe it.

We process the data on the basis of your consent (Art. 6(1)(a) GDPR) for a single purpose: contacting you about early access to the app and the founding-package terms. You can withdraw consent at any time with one email — we then remove you from the list.

Until you withdraw consent, and at most 24 months from sign-up. After that we delete the contact from the sign-up list.

We keep the data on servers in the European Union. We use an email provider and a hosting provider as processors — we do not sell or share data for advertising purposes.

Essential files (login session, theme choice, form protection) always work — the app will not run without them. We start Google Analytics and the Meta Pixel only after you consent in the banner, and we do not load them earlier.

Regardless of consent we count page views in our own database — no cookies, no IP address, no personal identifier. That is statistical data, not personal data.

You can withdraw consent at any time — without writing to us.

When resolving a ticket, support may open your account and see it as you see it — otherwise there is no way to establish what exactly is broken. This access has three hard limits:

Read only. In view mode support cannot save, change or send anything on your behalf — the block sits at the database level, not on hidden buttons.

Fifteen minutes. Access expires on its own and has to be opened again.

A record. We log every entry: who, when, and whose account they viewed. You can ask for a list of such entries for your account — just as you can for the rest of your data.

The app runs on an account, so everything below is tied to your account and you can download or delete it at any time (section 12).

Account: email address, optionally a first name, an account identifier, and — when signing in with Google or Apple — the permanent identifier those providers issue. Plus language, time zone and the name of the device holding the session (so you can end it remotely).

Health and fitness data: sex, age and height (needed for the metabolic-rate formula), weight and target weight, workouts with their sets, loads and repetitions, meals and macronutrients. This is a special category under the GDPR and we treat it as one — which is why the servers sit in the European Union and why we pass none of it to anyone for advertising.

Purchases: whether you have an active PRO subscription and until when. Payment is handled entirely by Google Play or the App Store — we neither see nor store your card details.

Referrals: if you use a friend's invitation, we store the referral code and who invited whom — without that there is no way to grant the reward.

The free version of the app shows advertising delivered by Google AdMob. To display it, Google uses your device's advertising identifier and data about your use of the app. These are the only data we pass to a third party for advertising, and the only ones that can serve cross-app tracking.

Before we show the first advert, we ask for consent. In the European Union a Google form (UMP) does this, and on iPhone the system's „Ask App Not to Track" dialog does so as well. Refusing blocks nothing — the app works the same and the adverts are then non-personalised.

We never pass your workouts, weight or meals to advertisers. The health category is excluded from personalisation in AdMob and that is how we have it configured.

The PRO version shows no advertising at all and passes on no advertising identifier.

We enable analytics (Firebase Analytics) only after you consent, which we ask for in the app, and you can switch it off at any time under „More → Privacy". We collect only events such as „someone finished a workout", with no number from your workout, weight or diet.

Crash reports (Firebase Crashlytics) are on by default and you can also switch them off in the same place. They say where in the code the app stopped working — not your data.

Neither of these is linked to your account: we pass no user identifier to them, so Google sees an anonymous installation, not you.

When you search for a food product, you send us a name or a scanned barcode. We then ask the open Open Food Facts database about it — without your identifier. The database sees one server of ours and the word „cottage cheese"; it does not see who is asking. That is exactly why the query goes through us and not straight from your phone.

The camera turns on only on the scanner screen and serves to read a barcode. The image never leaves your phone — only the string of digits reaches our server. We store and send no photograph.

When you scan a barcode Open Food Facts does not know, you can add the product yourself. That entry — name, brand, pack weight and nutrition values — goes into a shared catalogue: once we have checked it, other people using the app see it too. Until then it is visible only to you.

We store who added the entry — without that we could not show you your own entries or let you withdraw them. We do not show other users who added a product. Responsibility for the content of an entry is described in the terms §6.

When you report a product in the database (e.g. wrong nutrition values), we store the product code, the reason for the report, the date and your account identifier — solely to hide or correct the entry. We do not show the report to the entry's author or to other users; we delete it together with your account.

Product data comes from Open Food Facts and is made available under the Open Database License (ODbL).

You delete the account from inside the app: „More → Delete account". The request has a seven-day grace period — you can cancel it during that time, because deletion is irreversible. After the grace period we erase everything: profile, workouts, meals, weigh-ins and the account itself.

You can do the same without installing the app, through the account deletion page.

Database backups roll over on a cycle of up to 30 days — deleted data disappears from them by that point at the latest.

We sell data to nobody. We use providers who process it on our behalf: database and server hosting in the European Union region, a transactional email provider, Google (analytics, crash reports, advertising and Google Play payments) and Apple (App Store payments). The open Open Food Facts database receives only the content of a product query, with none of your data — see section 11.

The app collects no location, does not reach into contacts, photos or the microphone, and does not read data from the phone's health store (Health Connect, Apple Health).

de.load is not a medical device and does not replace advice from a doctor or a trainer.

You have the right to access your data, to rectify it, to erase it, to restrict processing, to data portability, and to lodge a complaint with a data protection authority — either your own national one or, for us, the President of the Personal Data Protection Office in Poland. One email is enough: [email protected].