Tasbihat has no account and no server of its own. Your dhikr counts, goals, streaks, reminders and settings live only on your phone. The app does use three limited services described below: your device’s speech recognizer (to count your dhikr), your device location (to calculate prayer times), and Google’s crash-reporting service (to fix crashes). We never sell your data. Today the app shows no ads and has no paid subscriptions; if we introduce them in future we will update this policy first (see “Changes” below).
1. Who we are
This Privacy Policy explains how the Tasbihat — Voice Dhikr Counter mobile application (“Tasbihat”, “the app”, “we”, “us”) handles information. It applies to the app on Android and iOS. If you have any questions, contact us at devfaisalj@gmail.com.
2. The short version by design
3. Information the app handles
3.1 Voice / microphone audio
To count your dhikr, the app listens through your microphone while you have counting active. Audio is analysed to recognise the dhikr you are reciting and increment a counter.
- The app does not record, save, or store your audio. Only a short live transcript is used, in memory, to detect a match; it is discarded as you go.
- Recognition runs on your device whenever your phone’s offline speech model for your language is installed. In that case audio is processed locally and does not leave the device.
- If an on-device model is not available, the app falls back to your platform’s standard speech recognition service (Google on Android, Apple on iOS). In that fallback mode, speech audio is sent to that provider to be transcribed, exactly as it is for the keyboard dictation button on your phone. This is handled by the operating system, subject to that provider’s privacy policy (Google, Apple).
3.2 Location
If you enable prayer-time features or prayer-linked reminders, the app asks for your device location. Your coordinates are used on the device to calculate local prayer times — that calculation happens entirely offline.
- The app never sends your location to us; we operate no server and receive no location data.
- To label your prayer times with the correct region, the app asks your device’s built-in geocoder to turn your coordinates into a country/place name. On most devices this step sends your coordinates to your platform provider (Google on Android, Apple on iOS), the same way the system Maps app resolves a place name, subject to that provider’s privacy policy (Google, Apple). This is best-effort and prayer times still work if it fails.
- You can decline the location permission and still use dhikr counting and manual reminders.
3.3 Counts, reminders and settings (stored on your device)
The following are stored in a private database on your phone and are not transmitted to us:
- Dhikr counts, daily totals, goals, streaks and lifetime statistics
- Reminders you create and their schedules
- Your in-app notification inbox messages
- App settings (haptics, sound, sensitivity, and similar preferences)
This data stays on the device. Deleting the app removes it. We have no copy and no way to recover it.
3.4 Crash and diagnostic reports
To find and fix crashes, the app uses Google Firebase Crashlytics. When the app crashes or hits a serious error, a diagnostic report may be sent to Google. These reports contain technical information such as the type of crash and stack trace, your device model and operating-system version, the app version, and a random Crashlytics installation identifier. They do not contain your dhikr counts, your microphone audio, or your name.
Crash reporting is disabled in development builds. Data sent to Crashlytics is processed by Google under its Firebase privacy terms and Google Privacy Policy.
4. What we do NOT do (as of today)
- No account, login, or user profile.
- No advertising networks and no ad tracking.
- No analytics SDKs building a profile of your behaviour.
- No paid subscriptions or in-app purchases.
- No selling or renting of personal information to anyone.
- No syncing of your counts or reminders to a server we control (we have no such server).
This describes the app as it works today. We may add advertising or optional paid subscriptions in the future — see “Changes to this policy”.
5. Permissions we request and why
| Permission | Why |
|---|---|
| Microphone | To listen and count your dhikr while counting is active. |
| Speech recognition (iOS) | To transcribe your recitation for counting. |
| Notifications | To deliver the reminders you schedule. |
| Location (optional) | To calculate local prayer times on your device. |
| Run in background / foreground service | To keep counting when the screen is locked. |
| Ignore battery optimisation (optional, Android) | To stop the system killing counting in the background. |
| Run at startup (Android) | To restore your scheduled reminders after a reboot. |
| Internet | Used only for: online speech fallback, resolving a place name from your coordinates (geocoding), and crash reports. |
6. Data sharing
We do not share your information with third parties, except the limited, purpose-specific processors described above:
- Your device platform (Google / Apple) — to transcribe speech when on-device recognition is unavailable, and to resolve a place name from your coordinates for prayer times (geocoding).
- Google Firebase Crashlytics — to receive crash and diagnostic reports.
We do not sell personal information.
7. Data retention
On-device data is kept until you delete it or uninstall the app. Microphone audio is not retained at all. Crash reports are retained by Google according to Firebase Crashlytics’ standard retention (typically up to 90 days).
8. Children
Tasbihat is suitable for all ages and does not knowingly collect personal information from children. Because the app does not require an account or gather identifying information, it does not build profiles of any user, including children.
9. Your rights
Depending on where you live, you may have rights under laws such as the GDPR (EU/UK) or the CCPA/CPRA (California), including rights to access, correct, or delete personal data.
- Data held on your device is fully under your control — edit counts in the app, or uninstall to erase everything.
- For crash-report data held by Google, you can contact us and we will help you exercise your rights with respect to reports tied to your installation identifier where technically feasible.
To make a request or ask a question, email devfaisalj@gmail.com.
10. Security
Because your dhikr data never leaves your device, it is protected by your device’s own security (lock screen, encryption, sandboxing). Data in transit to Google’s speech and crash services is encrypted by those services.
11. Changes to this policy (including future ads & subscriptions)
We may update this policy as the app evolves. Material changes will be reflected here with a new “Last updated” date. Continued use of the app after an update means you accept the revised policy.
In particular, the app may in the future introduce advertising and/or optional paid subscriptions or in-app purchases. Those features would involve additional processing that does not happen today — for example, an advertising provider receiving an advertising identifier and basic device data, or an app store (Google Play / Apple) processing your payment and sharing purchase confirmation with us. If and when we add such features, we will update this Privacy Policy to describe the data involved and the third parties concerned, and — where the law requires it (for example, for personalised ads under the GDPR) — we will ask for your consent before that processing begins. We will never retroactively apply new data uses to information collected under an earlier version of this policy without an appropriate legal basis.
12. Contact
Questions about privacy? Email devfaisalj@gmail.com.