Anonymous purchase, usage and review statistics
So that we can see where a purchase fails, whether a review prompt could be shown and whether the app runs fast and reliably, the app reports a few fixed events to our backend operated on Cloudflare: technical purchase steps such as purchase page shown, price loaded, purchase started, cancelled, failed or restored, and whether a review prompt was possible, requested, suppressed or unavailable, and a failed sign-in or account deletion. Once per installation, the app also reports whether the introduction was started, skipped or completed; we delete these counts after at most 120 days. Also, each at most once a day: where the purchase page was opened from (a fixed category such as start page, settings, introduction or a locked feature), whether Buy was tapped there and whether a purchase was made from it, which fixed steps occurred on the purchase page (for example purchase status checked, unlock shown or restore without result), whether the optional cloud backup could be uploaded or restored or, if it failed, the coarse reason (for example network, timeout, server or sign-in), the coarse start time until the app can be used (for example “1 to 2 seconds”) and whether the reminder is on, was switched or opened the app. With a purchase, the app also sends which purchase page it came from along with the purchase verification; we store this fixed category with the purchase data so that purchases per page cannot be miscounted, and delete it together with them. Each event contains only the event name, fixed categories, platform, app version and app language; no habits, names, notes, reflections or history, no input and no purchase receipts. The event itself contains no sign-in, account or device identifier. If the app already has a sign-in (including an anonymous one), it sends that session’s credential along for authentication; our backend uses it only for short-term rate limiting and to match a purchase report with a purchase the server verified for the same sign-in. Stored with the event is only whether it was signed in, neither identifier nor session; so that a confirmed purchase counts only once, a hashed reference to that purchase is kept with it for at most 8 days. Current app versions also send with every event the coarse origin of the installation (store, test or developer installation) so that test traffic is counted separately; it is determined on the device, without any device or installation identifier. If an event comes from the networks Google publishes for its automated pre-launch tests (Firebase Test Lab), our backend also counts it as test traffic; the IP address is only compared for this and not stored. We delete individual events after seven days. Daily totals of review prompts and of the daily events are deleted after at most 120 days; aggregate daily counters of purchase steps and of purchase and account-deletion errors are kept without a fixed deletion date. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is finding errors and purchase problems and improving the app. Because the events contain no identifier, we cannot link them to a person (Art. 11 GDPR). You can object under Art. 21 GDPR at any time by emailing apps@bitbeans.de. A failed report has no effect on using the app or on purchases.
Updated: 20 October 2026
1. Controller
Christian Hermann & Martina Hermann GbR, An Rainen 3, 72525 Münsingen, Germany; email: apps@bitbeans.de.
2. Data processed
Habits, entries and settings are stored locally by default.
Notes and reflections on entries, the optional app lock, the ritual timer and the theme choice stay on the device. Notes are stored encrypted, are part of the encrypted backups and go into an export file only if you explicitly choose so when exporting. The app lock uses your device’s screen lock (Face ID, fingerprint or device PIN); the operating system performs the check, the app only receives “unlocked” or “not unlocked” and stores no biometric data and no code of its own. The timer stores only its start time on the device; lock, timer and theme are not part of export or backup.
The optional cloud backup is end-to-end encrypted. The server stores only encrypted content and technical version data; the recovery phrase never leaves the device and cannot be read by us or our providers.
Depending on use, we process optional account IDs, purchase status, technical receipts, support messages and limited diagnostic data.
Purchase and sign-in diagnostics: the app reports a few fixed technical events to our Cloudflare backend – purchase steps such as purchase page shown, price loaded, purchase started, cancelled, failed, pending or restored, and a failed sign-in. Only the event name, a fixed stage, a fixed failure reason, platform and app version are stored, without sign-in, account or device identifiers, without habit content and without purchase receipts. Individual events are deleted after seven days; aggregate daily counters of purchase steps and purchase errors are kept without a fixed deletion date (Art. 6(1)(f) GDPR). Further anonymous counters on the introduction, start time, reminder, cloud backup and review prompt are named in the section “Anonymous purchase, usage and review statistics”.
3. Purposes and legal bases
We process data to provide the app, verify purchases, deliver online features you actively use, maintain security, resolve errors and answer voluntary requests. Depending on the operation, the legal bases are Article 6(1)(b), (f) or, where expressly requested, (a) GDPR.
4. Recipients and service providers
We use Cloudflare for encrypted backup and backend, Firebase/Google for optional sign-in, and Apple and Google for store services.
5. International transfers
Some providers may process data outside the EU or EEA. Where no adequacy decision applies, transfers rely on appropriate safeguards, in particular EU Standard Contractual Clauses, or on applicable statutory exceptions.
6. Advertising and tracking
The app contains no third-party advertising. We do not create advertising profiles, sell personal data or use advertising tracking.
7. Retention and security
Local data remains on the device until it is removed in the app or through system settings. Server data is retained only for as long as required for the respective function, security and statutory evidence. Transfers are encrypted.
8. Delete data and account
Local data can be removed in the app or through the device’s system settings. Where an account or cloud data exists, deletion can be requested in the app or by emailing apps@bitbeans.de. Store purchases are managed separately by Apple or Google.
9. Your rights
Subject to the statutory requirements, you have rights of access, rectification, erasure, restriction, portability and objection. Consent can be withdrawn for the future. You may also lodge a complaint with a data-protection authority; the LfDI Baden-Württemberg is the authority responsible for our registered office.