Privacy policy

This privacy policy applies to the Reach: Weight app and to this website, reachyourgoals.app. The website is hosted on Cloudflare. When you visit, Cloudflare processes technically necessary server log data (including IP address, timestamp, page requested) for secure and stable delivery. The legal basis is Art. 6(1)(f) GDPR. No cookies are set and no tracking is used.

Last updated: 22 October 2026 · Applies to: Reach: Weight (iOS and Android)

This privacy policy is available in German, English, Dutch, Swedish, French, Spanish and Greek. In case of any discrepancy between the versions, the German version prevails.

1. The most important points first

Reach: Weight stores and processes your data locally: your data stays on your device. In the current version we do not transmit your health data to any server. We do not operate any server that could store it either. The only service we operate is a small relay for the Withings sign-in that stores no tokens. No health data passes through it (sections 6d and 8).

We do no tracking, no analytics tools, no advertising and we do not sell any data. The app contains no third-party components for these purposes.

Planned, not active today (entitlement management via RevenueCat): Once Reach Pro is available for purchase in the App Store, the app will verify your purchase receipt through our processor RevenueCat, Inc. (USA). The RevenueCat SDK is technically part of the app, but is not configured in the current version. No data is sent to RevenueCat at present. When you buy Reach Pro, payment is handled entirely by Apple or Google. RevenueCat only checks the purchase receipt for us, without seeing your health data. You will see a notice inside the app before this happens. Details in section 8.

Important exception in planning (not active today): Optional AI-assisted analyses would, once you activate them, transmit selected data to a server, because the analysis does not happen on the device. That is when data first leaves your device. Such features are currently not part of the app and would only be introduced after we have updated this policy and obtained your separate, explicit consent (see section 13).

2. Which data the app processes

a) Health and body data (special category, Art. 9 GDPR): weight, body fat percentage, fat mass, lean mass as well as values and trends derived from them, including estimates of the likely composition of weight changes (fat and lean mass share). Optionally, notes and tags you add to a calendar day, and your goals.

The tags include optional cycle context tags (for example period, PMS, ovulation). If you mark several consecutive days as period, the app groups these days into a span for display (first to last marked day). These entries are health data about your cycle. They are stored exclusively locally and used only to help you make sense of weight fluctuations (such as cycle-related water retention). From this the app calculates no cycle prediction, no cycle length, no phase estimate and no fertility window. Reach only stores new cycle tags once you have given your consent. If you have already set cycle tags and decline consent, they stay stored but are not analyzed until you delete them in Profile under “Cycle”.

The app calculates the estimates mentioned above locally on demand from the values you have already recorded and does not store them permanently. They are an orientation, not a measurement and not a medical assessment.

b) Profile data (optional, for matching reference ranges): biological sex and year of birth. These entries are voluntary and serve only to display age- and sex-specific reference ranges correctly.

c) Technical data, exclusively local: app settings, a random device-internal identifier for internal data management, and local diagnostic logs for troubleshooting. The settings include the unit, the active data source, your reminder setting, whether haptics and audio charts are enabled, and your self-chosen weigh-in moment (habit anchor) together with an optional note you write about it. This data does not leave your device. The app also stores locally the date and version of your consent to the processing of your health data and, if given, your consent date for cycle tags. This information is visible in the profile and does not leave your device.

d) Access tokens of connected data sources (only with a Withings connection): if you connect your Withings account, the app stores the access tokens issued for it in encrypted form on your device. They are used exclusively to fetch your measurements and to renew the sign-in (sections 6d and 8). If you disconnect, they are deleted.

e) Purchase data (only when you buy Reach Pro, which cannot be purchased yet in the published app version): when you purchase, renew or restore a purchase, the receipt issued by the app store (purchased product, time, term, a store transaction number) and a random, device-internal identifier that the app itself generates are processed. This identifier contains neither your name nor your email address. There is no user account. Your health data is not part of the purchase data and is not linked to it. What you measure and analyze in the app stays on your device, whether you use Free or Pro.

f) Entitlement identifier (only if you buy Reach Pro, not yet active in the published app version): Once Reach Pro is available for purchase, the app will transmit at the time of purchase, renewal or restoration the random, device-internal identifier from section 2e together with technical information (platform, app version) to RevenueCat. In the published app version this transmission does not take place. Your Early Access free status is currently stored exclusively on your device. Health data is not affected. There is no advertising identifier.

3. Purposes and legal bases

• Core function of the app (recording, displaying and analyzing your measurements): processing of your health data on the basis of your explicit consent (Art. 9(2)(a) GDPR) in conjunction with Art. 6(1)(a) and (b) GDPR. The app asks you for this consent explicitly, in a step of its own, before it stores or analyzes any values.

• Optional profile data: likewise on the basis of your consent. Without this information the app continues to work, only without reference ranges based on age and sex.

• Cycle context tags (only if you use them): processing on the basis of your explicit consent (Art. 9(2)(a) GDPR) for the sole purpose of making sense of cycle-related weight fluctuations. Before you set your first cycle tag, the app explains in a separate step what it stores and why, and asks for your explicit consent. Without it, the app sets no cycle tag. If you had already set cycle tags before, the app asks you once. If you do not consent, the app no longer uses these tags and offers to delete them, right away or later in the profile. No cycle prediction or phase estimate takes place. You can remove these tags from a day individually at any time. Earlier entries then remain in the internal change log of the app. You delete them completely in the profile under “Cycle”, all at once. This withdraws your consent (section 11). You can hide the entire category in the profile.

• Withings sign-in via the relay (only with a connection): processing of the sign-in tokens and, technically necessary, your IP address, in order to establish the connection you requested (Art. 6(1)(b) GDPR in conjunction with your consent when connecting the data source). Details in sections 6d and 8.

• Purchase handling and entitlement management (only if you buy Reach Pro): processing of the purchase data (section 2e) in order to confirm your purchase, provide your Pro entitlement and restore purchases on a new device (Art. 6(1)(b) GDPR, performance of a contract), as well as for the prevention of misuse and fraud and for aggregated, non-personal sales figures (Art. 6(1)(f) GDPR, legitimate interest). Health data is not affected.

• Entitlement management (only if you buy Reach Pro, not yet active in the published app version): Once Reach Pro is available for purchase, we process the entitlement identifier (section 2f) on the basis of our legitimate interest (Art. 6(1)(f) GDPR) in providing the app's feature tiers without a user account, in preserving a permanent free status earned during the Early Access phase even after switching devices, and in avoiding the need to re-establish a lost free status via support. In the published app version this processing does not take place. Until then your Early Access status is stored exclusively on your device. Once the processing is active, you can object to it (section 10). The core functions of the app then remain fully usable, only purchasing and restoring Reach Pro technically require the entitlement check. Health data is not affected.

• Troubleshooting (local logs): legitimate interest in a working, stable app (Art. 6(1)(f) GDPR). The logs stay local.

Providing your data is neither legally nor contractually required. You decide yourself whether and which values you record or import. If you do not enter any data, the app has nothing to display or analyze. No other disadvantages arise for you.

You can withdraw your consent at any time with effect for the future (see sections 10 and 11).

4. Where your data lives

Your measurements and your profile live in a local database on your device. Nothing is transmitted to us automatically. This also applies to cycle context tags: if you create a manual, encrypted export (section 7), they are included in it and stay wherever you place the export file.

On iOS this local database is excluded from the automatic iCloud device backup, so that your health data does not end up in iCloud unintentionally, whether you enter it yourself or import it from Apple Health (Apple App Store Review Guideline 5.1.3).

On Android the automatic device backup (Google Auto Backup) for the app is fully disabled. Your health data is therefore not automatically transmitted to Google Drive or to another device.

The intended route to a new device is, on both platforms, the manual, encrypted export (section 7).

5. Access protection (app lock)

You can optionally lock the app with a PIN and, if your device offers it, with biometrics (for example Face ID or fingerprint). This feature is off by default and is only activated if you set it up.

The app lock is an access protection, not an encryption of your data. It prevents someone from opening the app and seeing your values if your unlocked device falls into the wrong hands. It does not protect against a technical readout of the device storage.

• PIN: your PIN is not stored in plain text. A salted verification value (HMAC-SHA256) is computed from it and placed in the operating system's secure key store (iOS Keychain or Android Keystore). After several failed attempts, each further attempt requires a longer wait.

• Biometrics: the biometric comparison is performed exclusively by the operating system. Your biometric features do not leave the device and are at no time accessible to the app. The app only receives the response “confirmed” or “not confirmed” from the system.

• Forgotten PIN: for security reasons a forgotten PIN cannot be recovered. Then the only option is to reset the app. All local data is deleted in the process. You can then restore your data from a previously created encrypted export (section 7).

You can disable the app lock again at any time in the settings.

6. Data sources in detail

You choose where your measurements come from. At most one automatic source is active at a time, or none. Manual entry is always possible. If an automatic source is running, the measurements in question do not come from your direct input but from that source (Art. 14 GDPR). The data involved is described in the following paragraphs and in section 2.

a) Manual entry: you enter values yourself. They stay on the device.

b) Apple Health (iOS): with your explicit consent in the system dialog, the app accesses weight, body fat and lean mass in Apple Health read-only. This data is processed on the device and not transmitted by us to any server. Data read from Apple Health is not used for advertising or marketing and is not stored in iCloud. You can revoke access at any time: in the iOS settings under “Privacy and Security”, then under “Health”.

c) Health Connect (Android): with your explicit consent, the app accesses the data types weight, body fat and lean mass in Health Connect read-only, in order to display and analyze them. Processing takes place locally on the device. You can revoke the permissions in Health Connect at any time.

d) Withings (optional): if you connect your Withings account, you sign in to Withings and authorize the app to fetch your measurements from the Withings cloud (OAuth, scope: read measurement data). Your measurements are loaded directly to your device. We do not transmit your health data to any server of ours in doing so. Only the sign-in process itself (issuing and renewing the access tokens) runs, for security reasons, through a small relay operated by us, so that a secret access key does not have to sit inside the app. Through this service only sign-in tokens pass, no health data. The tokens are not stored there (details and hosting in section 8). Withings is independently responsible for the processing in its cloud. The Withings privacy policy applies in addition. The access tokens are stored in encrypted form on your device. You can disconnect in the app at any time.

7. Backup and data portability

The app offers a manual, encrypted export of your data (.reachbackup). You trigger the export yourself, it is encrypted, and you decide where to store it. It serves the move to a new device and at the same time gives effect to your right to data portability (Art. 20 GDPR). We do not receive a copy.

The export is secured with a recovery code that is shown to you once at creation. Only someone who knows this code can open the file. We do not know the code and cannot recover it: if you lose it, no one can access the data in the backup file any more, including us.

In addition, the app offers a user-initiated export of your measurements as an open CSV table file (unencrypted), for example for your own analyses in a spreadsheet. Here too you choose the destination yourself via your device's share dialog. We do not receive a copy. Since this file is unencrypted, protecting the chosen storage location is up to you.

8. Disclosure to third parties

We do not disclose your health data to third parties, do not sell it and do not use it for advertising. These are the places where third-party technology is involved:

• Withings: only if you connect your account, and only to fetch your own measurement data (section 6d).

• Cloudflare (only with a Withings connection): our relay for the Withings sign-in (section 6d) is operated at Cloudflare. In doing so, the sign-in tokens and your IP address are technically processed. The service stores no tokens and no payload data. For operations, Cloudflare keeps short-lived technical invocation logs (time, IP address, response status) that are deleted automatically after no more than seven days. The contents of requests are not logged. Your health and measurement data does not pass through this service, but is exchanged directly between your device and Withings. Cloudflare processes this data on our behalf (Art. 28 GDPR). Cloudflare is a US company. The transfer is safeguarded by Cloudflare's certification under the EU-US Data Privacy Framework as well as EU standard contractual clauses. Cloudflare is additionally certified under the UK Extension to the Data Privacy Framework and the Swiss-US Data Privacy Framework. This also applies if you live in the United Kingdom or Switzerland.

• Apple or Google: provision and delivery of the app via the respective app store. In doing so Apple/Google do not receive any of your health data stored in the app from us. If you buy Reach Pro, Apple or Google handle the payment (their own responsibility and their own privacy policy). We do not receive payment data such as credit card numbers.

• RevenueCat (planned entitlements processor, not active in the current build): RevenueCat, Inc. (USA) is planned as a processor (Art. 28 GDPR) for verifying purchase receipts and managing Reach Pro. The RevenueCat SDK is technically part of the app, but is not configured in the current version and sends no data. No data flows to RevenueCat at present. Once Reach Pro is available for purchase in the App Store, the app will transmit at the time of purchase, renewal or restoration the random, device-internal identifier from section 2f, technically necessary your IP address, technical information such as app version and platform, and the store purchase receipt (product, time, term, transaction number, see section 2e). You will see a notice inside the app before the first activation. RevenueCat receives no health data, no advertising identifiers and no information about how you use the app. Since RevenueCat is a US company, a transfer to the USA will take place upon activation. It is safeguarded by EU standard contractual clauses. We have additionally assessed the transfer ourselves: because no health data is transmitted and the identifier is random, the risk to you is low. If you want to have data deleted or object to processing, write to us at hello@reachyourgoals.app. We will forward your request to RevenueCat.

• Expo / EAS Update: to deliver app updates, the app checks with an Expo service whether a new app version is available. In doing so, technical information (for example the version of the app and the runtime environment) and, for technical reasons, your IP address are transmitted, but no health data. Expo (650 Industries, Inc.) is a US company. The transfer to the USA is safeguarded by EU standard contractual clauses.

9. Controller

Controller for the data processing within the meaning of the GDPR:

Charalampos Theocharidis
Schleiermacherstr. 123
44869 Bochum
Germany
hello@reachyourgoals.app

We are currently not required to designate a data protection officer (Art. 37 GDPR, Sec. 38 BDSG) and have not appointed one. Please send data protection requests to the email address above. No special keyword is needed.

10. Your rights

Under the GDPR you are entitled to: access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21) as well as the right to withdraw consent at any time (Art. 7(3)). You withdraw your consent to cycle tags by deleting them in the profile under “Cycle” (section 11). You do not need to write to us for this.

Because your data lives locally on your device, you exercise most of these rights directly in the app: view, change, delete, export values, and reset the app entirely. For anything else you can reach us at hello@reachyourgoals.app.

You also have the right to lodge a complaint with a data protection supervisory authority. The authority responsible for us is the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (LDI NRW), Kavalleriestraße 2-4, 40213 Düsseldorf, www.ldi.nrw.de. You can also contact the supervisory authority of your place of residence.

The app makes no automated decisions that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR). All computed trends, forecasts and notices are orientation values for your own interpretation, not assessments and not decisions.

11. Storage period and deletion

Your data stays on your device until you delete it.

Removing individual measurements: if you remove a measurement in the app, it is thereafter no longer visible in the app and no longer flows into any analysis. The associated entry, however, remains in the internal change log of the app, marked as inactive. This log lives in the local database on your device. The log keeps a traceable record of what has changed, and allows a backup to be fully restored. The inactive entries do not leave your device and are no longer used by the app.

Removing labels from a day (tags): labels for a calendar day are stored separately from measurements. Deleting a measurement leaves the labels of that day untouched. To remove the labels of a day, open that day in the history and remove all markings in the tag area. The earlier entry then remains in the internal change log, as with removed measurements. You remove cycle tags from it with “Delete cycle tags” in Profile. When you delete your last measurement, you can remove all tags shown in the history in the same step. Cycle tags that the history does not show (without your consent or with cycle influences switched off) stay saved. You delete them in Profile under “Cycle”. If the history shows them, they are physically removed from the internal change log of the app, as described under “Deleting cycle tags”. Your consent remains in place.

Deleting cycle tags: you can delete all cycle tags (period, PMS, ovulation) at once in Profile under “Cycle”. This also withdraws your consent. Unlike removed measurements, cycle tags are physically removed from the internal change log of the app (Art. 17 GDPR). A deletion marker remains in the log to record that a deletion took place. It contains no cycle information, only the time of the deletion and the time of your first entry in the app, so that your Early Access status is kept. If you later restore an older backup on this device, Reach does not bring back the deleted cycle tags. A backup you created before deleting still contains them, though. If you restore such a backup on a new device or after resetting the app, the cycle tags can come back. You delete such backups yourself at their storage location.

Deleting completely: if you want to remove your data from your device permanently, tap “Delete all data” in Profile (which deletes the local database together with the change log) or uninstall the app. If you have saved an encrypted export yourself, delete it at its storage location.

12. Children

The app is not directed at children. It is intended for persons aged 16 and over. This threshold is based on the highest age of consent the GDPR allows member states to set (Art. 8(1) GDPR) and applies regardless of the age that governs in your country. Tracking weight and body fat is not suitable for children. The app's reference ranges and trend analyses are designed for adults.

13. Planned features, not active today

These features are not part of the app today. Before we introduce them, we will adapt this policy and obtain the necessary consent.

a) AI-assisted analysis (two possible variants). Unlike the rest of the app, AI features would transmit selected data to a server, because the analysis does not happen on the device. That is why they are strictly optional and disabled by default.

• Reach's own AI: Reach would transmit selected data to an AI processor that processes it on our behalf (processing on behalf, Art. 28 GDPR). We will describe the provider, the place of processing and the safeguards for a transfer to a third country (Art. 44 et seq. GDPR) here before the feature is available.

• Bring Your Own AI: you provide your own AI provider. The selected data then goes to the provider you chose, whose data protection terms apply in addition.

In both cases the following applies: activation only by you, separate explicit consent (Art. 9(2)(a) GDPR) before the first transmission, data minimization (only the data necessary for the analysis), no use for advertising, no profiling beyond the analysis you requested, and no training of AI models. Withdrawal at any time with effect for the future.

b) Further possible features (for example an encrypted cloud synchronization): would likewise be optional, and we will describe them here before we introduce them. The paid additional features (Reach Pro) including payment handling via the app stores are described in sections 2e, 3 and 8.

c) Local reminders: would be optional and run exclusively on your device. No push token is created and nothing is transmitted to us or third parties. We describe them here in more detail before we introduce them.

14. Changes to this privacy policy

We adapt this policy when the app or the legal requirements change. The current version is always available directly in the app (More, Privacy) and at reachyourgoals.app/datenschutz. The date at the top identifies the version.

15. Contact

Questions about data protection: hello@reachyourgoals.app.

If you contact us by email, we process the information you provide (your email address, the content of your message and the technical details the app appends to the email (app version and platform)) exclusively to handle your request (Art. 6(1)(b) or (f) GDPR). Please do not send us health data by email. It is usually not required to handle your request. After your request has been concluded, the messages are deleted, unless statutory retention obligations exist.