Dhikr - Tasbeeh & Zikr Counter

Privacy Policy

Developer: arifz
Last updated:

This policy explains how arifz ("we", "us") handles information in the Android app Dhikr - Tasbeeh & Zikr Counter ("Dhikr"), package xyz.arifz.dhikr.

1. Information stored on your device

Dhikr stores completed sessions (including preset titles, counts, and completion times), unfinished session progress, custom presets (including titles, Arabic text, transliteration, and target counts), and app preferences in its private Android storage. Streaks and activity summaries are calculated from these records.

There is no Dhikr account or developer-operated cloud sync for these records. However, selected details about your activity are sent to Firebase when analytics is enabled, as explained below. Local storage does not mean that no activity information leaves your device.

2. Usage analytics

Dhikr uses Google Analytics for Firebase to understand feature usage and improve the app. Analytics is enabled by default, including on first use. You can turn it off using the Analytics toggle in Settings.

The app records events such as screens viewed, preset selections, free counting, completed sessions, streak milestones, custom preset creation or deletion, changes to language, theme, sound, haptics or reminders, and use of the Share App button. Event details can include preset identifiers and names, total completed counts, streak length, and selected settings.

Custom preset titles are included: when you select or complete a custom preset, the title you entered can be sent with the event. These titles and activity events may reveal information about your religious practice or anything personal you put in a title. Arabic text and transliteration are not deliberately attached as separate analytics fields.

The Analytics SDK also collects app-instance identifiers, app and device information, interaction timestamps, session and engagement information, and installation or referral information. It can derive approximate location, such as country or city, from your IP address. Google states that Analytics does not log or store individual IP addresses. Dhikr does not request GPS location access.

These records use identifiers and are not completely anonymous. Dhikr does not ask you to register a name, email address, or phone number, and does not set an account-based user ID. The app is configured to disable Analytics collection of the Android advertising ID.

Turning analytics off stops future Analytics collection once the setting takes effect; the app logs the opt-out action before disabling collection. Turning it off does not automatically delete data already collected and does not disable crash reporting. Offline collection may be queued for later transmission when a connection is available.

3. Crash and diagnostic reporting

Dhikr uses Firebase Crashlytics to diagnose crashes, app unresponsiveness, and stability problems. Automatic reporting is enabled, and the current app does not offer a switch to disable it.

Reports and associated diagnostics may contain error stack traces, event times, app version and state, device model, operating-system version, memory and storage information, and installation or session identifiers. When Analytics is enabled, recent analytics events and their parameters may also appear as diagnostic breadcrumbs.

Diagnostic information may be saved locally and uploaded later, including on a subsequent app launch. Crashlytics and its supporting services can collect installation and session information as part of their operation, not only at the instant a crash occurs.

4. Service providers and other disclosures

Google receives and processes analytics and diagnostic information through Firebase and Google Analytics. We use the resulting reports to understand usage and resolve problems. Google may process information on servers outside your country under its applicable terms and privacy safeguards.

Dhikr also uses Google Play's in-app update service to check for and offer updates. Google Play handles update delivery under its own terms and privacy practices.

There are no advertising placements in Dhikr. We do not sell your data. Information may also be disclosed where required by applicable law or to protect legal rights and security.

5. Android backup and device transfer

Android backup is enabled for the app. Depending on your Android version, device, and settings, the system may back up app records and preferences to your Google account or transfer them to another device. Restoring a backup may restore previously saved records and settings.

You control system backup through Android and your Google account. Clearing app storage or uninstalling the app does not necessarily remove existing backup copies. Manage or delete those copies through your backup provider's controls.

6. Permissions and reminders

Notification permission is used for daily reminders. These reminders are scheduled and generated on your device using local session and streak information; they do not require a remote notification server. A reminder may include a preset title and may appear on your lock screen, depending on Android settings. You can turn reminders off in Dhikr or manage notification access and visibility in Android settings.

Internet and network-state access support online services such as analytics and diagnostics. Android libraries may also use background-work, boot, foreground-service, installation-referral, and related system permissions. Core counting features remain available offline.

Dhikr does not request access to your contacts, camera, microphone, precise location, or shared photos and files.

7. App sharing and messages to us

Share App opens Android's share interface with a short message and a Play Store link. Dhikr does not receive the recipient's identity or your conversations. The receiving app handles that sharing under its own privacy policy. Use of the share button may be recorded as an analytics event.

If you email us, we receive your email address, message, and any information or attachments you choose to send. We use them to respond to questions, suggestions, feature requests, and privacy inquiries. Our email provider processes those messages. Please include only information needed for your request.

8. Retention, deletion, and your choices

Depending on your location, you may have rights to access, correct, delete, or restrict the use of personal data, or object to its processing. Contact us to make a request. We do not have access to the records stored only on your device, and without an account we may be unable to identify which installation-based analytics or diagnostic records belong to you. We will explain what can be identified and addressed rather than promise deletion of records we cannot locate.

Clearing app storage resets preferences, so default analytics settings may apply on a fresh start unless a saved setting is restored. Review Settings after reinstalling or restoring the app.

9. Security

Local records are protected by Android's app storage isolation and your device's security settings. Firebase services use encrypted network transport. No storage or transmission method guarantees absolute security; secure your device and any account used for system backups.

10. Children and privacy

Dhikr does not ask for age or date of birth and does not create user accounts. The analytics and diagnostic collection described above can occur for anyone using the app; absence of an account does not make that information anonymous. A parent or guardian with concerns about information relating to a child can contact us for assistance and available deletion options.

11. Changes to this policy

We may update this policy as the app or its data practices change. Updates will be posted on this page with a revised date. Where required, we will provide additional notice or request consent before a change takes effect.

12. Contact

For privacy questions, data requests, suggestions, or feature requests, contact arifz, developer of Dhikr - Tasbeeh & Zikr Counter:

[email protected]