Last updated: September 15, 2026
The controller responsible for data processing under the GDPR is: Louis Krause, Rehwechsel 11, 21224 Rosengarten, Germany. Email: coreelements.ce@gmail.com.
EndoFriendly stores all log data, settings, and custom categories exclusively on your device. There is no user account and no server where your health data is stored. Your entries leave your device only if you export or share a backup yourself (see section 7), or when you make a purchase or start a subscription (see section 13) — your health data is never affected by this.
This includes, in particular, health data you enter (cycle, bleeding, pain, mood, bowel movements, discharge, urine, intimacy, medication, food, weight, activity), optional photos attached to food entries, app settings, and — if you enable app lock — a salted hash of your passcode, stored exclusively in your device's secure system storage (iOS Keychain / Android Keystore), never in plain text and never off the device.
The health data you enter is a special category of personal data (Art. 9 GDPR). We process it on the basis of your explicit consent (Art. 9(2)(a), Art. 6(1)(a) GDPR), which you give by creating entries and can withdraw at any time with future effect — for example by deleting the relevant entries or uninstalling the app. Because processing happens exclusively on your own device, we as the provider never have possession of this data.
The camera is used to scan barcodes and, optionally, to take photos for food entries; you can alternatively grant access to your photo library to add existing photos instead. Photos you take are stored exclusively in the app's local sandbox storage and are never transmitted to us or any third party.
The following features send requests to independent third-party servers with their own privacy policies: (a) barcode scanning and product search send the scanned barcode or your search term to Open Food Facts (Open Food Facts non-profit, France/EU); (b) recipe search sends search terms to TheMealDB, whose server location we do not control — a data transfer outside the EU/EEA is possible; (c) if we have configured a DeepL API key, recipe text is sent to DeepL (Germany/EU) for translation. In all three cases, no health data, name, or device identifier is transmitted to us in plain text — only the respective search term or barcode, plus technically unavoidable connection data (e.g. IP address), reach the respective provider. You can disable these features under Settings → Privacy (Scanner).
Via "Settings → Backup/Export" you can generate a local file (JSON, CSV, or PDF) of your data, which may include embedded photos. This file is handed to your device's native share sheet — where you save it or with whom you share it (e.g. iCloud, Google Drive, email) is entirely up to you; we have no access to and no influence over that.
Reminders are scheduled as purely local, on-device notifications. No data is transmitted to us or any third party in the process.
Your data stays on your device until you edit or delete it yourself, or uninstall the app. There is no server-side storage, so the question of a server-side retention period does not arise.
You have the right to access, rectification, erasure, restriction of processing, data portability (the backup export feature described in section 7 already fulfills this directly), and objection to processing. Since your data lives exclusively on your device, you can exercise these rights yourself at any time within the app — access and editing directly in your logs, complete and irreversible deletion via "Settings → Danger Zone". You also have the right to lodge a complaint with a data protection supervisory authority, e.g. the Landesbeauftragte für den Datenschutz Niedersachsen, which is responsible for our location.
EndoFriendly is intended for people aged 16 and over. People under 16 may only use the app with a parent's or guardian's consent.
If an optional cloud sync feature is introduced in the future, you'll be actively asked for separate consent beforehand. This policy will be updated accordingly before the feature becomes usable for you.
For in-app purchases and subscriptions we use the service RevenueCat, Inc., which manages your purchase status (active/inactive, current plan) and reports it back to the app as a simple yes/no. This involves sending an anonymous device identifier generated by RevenueCat itself, plus purchase receipts from Apple or Google, to RevenueCat — the health data that otherwise stays exclusively on your device is not affected. Payment itself is handled entirely by Apple (App Store) or Google (Google Play) through your account there; neither we nor RevenueCat ever receive any payment or card details.
We update this privacy policy when the app's feature set or the legal situation changes; the current version is always available in the app. For privacy-related requests or to exercise your rights, reach us at coreelements.ce@gmail.com.