Zen Bell Last updated: July 17, 2026
Zen Bell (“the App”) is developed by Khanh Mai. We are committed to protecting your privacy. This policy explains what data we collect, how we use it, and your rights.
This data is stored locally on your device using an encrypted database. It is never shared with third parties.
If you enable cloud sync, your observations, settings, and acknowledgments are encrypted and stored on Supabase (our cloud provider). Data is encrypted before leaving your device. You can delete all cloud data at any time from Settings > Account > Delete Account.
We use TelemetryDeck for pseudonymous, aggregated usage analytics. “Pseudonymous” means signals carry a one-way hashed identifier so we can count distinct users — we cannot reverse it to identify you. TelemetryDeck is a privacy-first analytics service that:
What is collected: in-app events such as screen views, feature usage counts, bell schedule shape (interval and window — never journal content), purchase funnel outcomes (success/cancel/failure category — never payment details), plus automatic session signals sent by the TelemetryDeck SDK itself (app launch, session start, app version, OS version, device model class, language).
Analytics is on by default and disclosed here. You can turn it off at any time in Settings › Privacy › Usage Analytics. Turning it off takes effect immediately: custom events stop instantly and the analytics SDK is shut down, so its automatic session signals stop too. While analytics is off, the SDK is never started on later launches.
Retention: analytics signals are retained by TelemetryDeck in aggregated form; raw signals age out per TelemetryDeck’s privacy policy. We store your consent choice (on/off, version, timestamp) only on your device.
Google Analytics (Firebase). We also use Google Analytics for Firebase (GA4) as a second analytics service, running in parallel with TelemetryDeck under the same on/off switch. Firebase Analytics collects a pseudonymous app-instance identifier — a random, app-scoped ID that is reset when you reinstall the app; it is not your advertising identifier (IDFA) and is not used to track you across apps or websites — together with the same in-app usage events described above, and sends them to Google acting as our data processor. It is configured without advertising-identifier (IDFA) support and without Google “signals,” so no App Tracking Transparency prompt is shown. Because analytics is on by default, Google receives data from your first launch unless you turn analytics off; the same Settings › Privacy › Usage Analytics switch stops Google Analytics collection too. Data is handled per Google’s Analytics data-retention controls and Firebase’s privacy and security terms.
We do not use Apple’s App Tracking Transparency (ATT) because we do not track users across apps or websites.
(Note: our analytics services use pseudonymous, non-advertising identifiers — a hashed TelemetryDeck signal id and a Firebase app-instance id — as described in the Analytics section. These are not linked to your identity and are not used for tracking.)
| Service | Purpose | Privacy Policy |
|---|---|---|
| Apple StoreKit | Subscription purchases | Apple Privacy |
| RevenueCat | Subscription management | RevenueCat Privacy |
| Supabase | Cloud sync (optional) | Supabase Privacy |
| TelemetryDeck | Pseudonymous usage analytics | TelemetryDeck Privacy |
| Google Analytics (Firebase) | Pseudonymous usage analytics (no IDFA/ads) | Google Privacy · Firebase |
None of these services receive data for advertising purposes.
The App does not knowingly collect data from children under 13.
We may update this policy from time to time. Changes will be posted on this page with an updated date.
If you have questions about this privacy policy, contact us at: blueblazedev@outlook.com