Your Dhikr Is None of Our Business

A privacy policy you can actually verify

Most privacy policies ask for trust: "we collect X but promise to handle it carefully." Ours describes an absence. We can't mishandle your data because we never receive it.

What "on device" means, concretely

Every count you make, every streak, every goal, every setting is stored in your iPhone's local storage — the same protected sandbox iOS gives every app. There is no Just Tasbih server. There is no database with your name in it. There is no analytics dashboard where we watch usage graphs.

When you count 99 Subhanallah after Fajr, the only two parties who know are you and Allah. We built the app specifically so that we are not a third.

The only place your data goes is your own iCloud

Honesty requires precision: your counts and custom dhikr are mirrored to your personal iCloud key-value storage, so a reinstall or a new phone brings them back. That backup belongs to your Apple account. It travels between your device and Apple — it never touches a server of ours, because we don't have any.

That's also exactly what our App Store privacy label says: no data collected. Nothing else to disclose.

No crash reporters, either

We went further than most: there's no crash reporting SDK, no Firebase, no Mixpanel, no Meta SDK. When developers add these "harmless" tools, they open a channel from your device to third-party servers — and every SDK is code we'd be shipping inside a worship app without being able to read it line by line.

If the app crashes, you can tell us the old-fashioned way: email. We read every one.

Why this matters more for a tasbih app

Dhikr is intimate. How often you remember Allah, when, which phrases — this is between a person and their Lord. An app that positions itself inside that moment carries a real amanah. The strongest way we could honor it was to make surveillance architecturally impossible, not just contractually promised.