HEPLANO Rhythm — Privacy Policy
Last updated: October 29, 2026
1. Controller
The controller for the processing of personal data in connection with HEPLANO Rhythm is:
HEPLANO
Owner: Jürgen Heuft
Heinrich-Heine-Str. 15
50389 Wesseling
Germany
Email: dev@heplano.com
2. Summary
HEPLANO Rhythm is a diary for eating times for Android. Your entries and settings stay encrypted on your device. HEPLANO runs no servers of its own for this data, requires no user account, shows no ads and uses no analytics or tracking services.
Data leaves the device only when you cause it: when you export, create a backup file or share. The purchase of Premium runs through Google Play (section 9).
3. Data HEPLANO Rhythm stores on your device
- Entries: type (meal or snack), time and, if you wish, how long the meal lasted
- Urges: category (for example physical hunger, appetite, habit, boredom, stress or emotion, no hunger, or your own entry with the name you give it) and time
- Movement: type (walk, strength training, other), time and, if you wish, the duration
- Marks of days as “fully documented”
- Settings: language, hide timer, show points, app lock and screen protection, reminders (type, times, rhythm, name or text, pause, quiet hours)
The data is stored in an encrypted database (SQLite3 Multiple Ciphers). The key is random and kept in the Android keystore of your device. The data may contain indications about your health, for example urges of the category “physical hunger” or “stress or emotion” and movement. HEPLANO does not transmit it to us and has no access to it.
4. Permissions
The app only requests permissions it needs for a feature. You can revoke them at any time in the Android settings.
- Notifications: for reminders. HEPLANO only asks when you turn on a reminder.
- Biometrics (fingerprint, face, device PIN): only for the optional app lock. Android performs the check; HEPLANO only receives the result, no biometric data.
- Start after restart: so that reminders keep running after the device restarts.
- Vibration: for notifications.
- Internet, network state and billing (Google Play): for buying Premium (section 9). The app uses them only to process and check the purchase through Google Play.
5. Reminders
HEPLANO schedules reminders as local notifications on your device. There is no server for this. The text never contains data from your diary. A notification can be visible on the lock screen; so do not write anything private in the name or text of your own reminder.
6. App lock and screen protection
The optional app lock uses the sign-in of your device (fingerprint, face or PIN). The screen protection prevents screenshots and the preview image in the app switcher. Both work locally.
7. Backup, export and sharing
A backup is a file encrypted with a password you choose (Argon2id and AES-256-GCM). You store it yourself, HEPLANO does not transmit it anywhere. The password cannot be recovered; without it the file cannot be read.
An export (JSON or CSV) is not encrypted. You trigger it yourself and decide through the Android share menu where the file goes. From there the privacy policy of the recipient applies.
HEPLANO Rhythm does not take part in the automatic Android backup of your Google account.
8. Home screen widget
A widget is optional; you place it on the home screen yourself. While it is there, HEPLANO stores the type and time of the last entry and the start of the running break unencrypted in the private storage of the app so the widget can show it. With the app lock on, HEPLANO sends no entry data and the widget only shows “Open”. “Delete all data” empties the widget.
9. Purchase of Premium (Google Play)
Premium can be bought through Google Play as a yearly subscription, a monthly subscription or a one-time purchase. Google handles the payment; HEPLANO receives no payment data such as card numbers. For this the app contacts Google Play, asks whether a purchase exists and remembers locally only whether and which purchase applies. Entries, urges, marks and settings are not transmitted. The privacy policy of Google applies. The app shows the price, term, renewal and cancellation before the purchase; you cancel a subscription in Google Play.
10. Contact by email
If you write to us at dev@heplano.com, we process your email address and the content of your message to answer your request. HEPLANO transmits no data to this address; you decide what you send us. Please do not send health data unless necessary.
11. Crash reports
HEPLANO uses no analytics or error-reporting software. If you have allowed sharing of usage and diagnostic data on your device, Google may transmit crash data to the Google Play Console, which we can access.
12. No ads, no tracking, no account
HEPLANO Rhythm shows no ads, requires no user account, uses no analytics or tracking services and creates no usage profiles.
13. Storage period and deletion
The data stays on your device until you delete it in the app under “Delete all data” or in the Android settings (“Clear data”) or uninstall the app. “Delete all data” removes the database, the key and the widget data; this cannot be undone. Backup files and exports you stored or passed on yourself you delete yourself.
14. Your rights
Subject to the legal requirements you have the right of access, rectification, erasure, restriction of processing, objection and data portability, and the right to lodge a complaint with a data protection supervisory authority. Send requests to dev@heplano.com. Since HEPLANO transmits no data to us, we cannot provide information about locally stored data. You see it in the app and can export and delete it yourself.
15. Children
HEPLANO Rhythm is aimed at adults and is not meant for children. HEPLANO does not knowingly collect data from children.
16. International use
HEPLANO Rhythm can also be used outside Germany. For users in Switzerland the revised Swiss Data Protection Act also applies; the statements apply accordingly there.
17. Website heplano.com
For visiting the website, the privacy policy of heplano.com applies.
18. Changes
We adapt this policy when HEPLANO Rhythm or the legal situation changes. The version published here applies.