Summary
Divya Mala is a mala bead counter and personal practice companion. We have designed the app to keep your practice data on your device and to use the minimum amount of third-party services needed to keep the app stable and improve it over time:
- Your practice data stays on your device. Your mantras, counts, history, reminders, and language/theme preferences are stored locally using on-device storage (MMKV). They are not synced to any server.
- We use Google Firebase for crash reporting, basic usage analytics, and remote feature configuration. Firebase processes a limited set of technical data on Google's servers, described in detail below. It does not receive your mantras, counts, history, or any content you create in the app.
- We do not sell your data, run advertising, or use any third-party advertising or tracking SDKs.
- We do not require an account. You can use the app fully without signing in.
1. Information Stored Only on Your Device
The following information is created and stored only on your device, and is never transmitted to us or to any third party:
| Data | Stored where | Why |
|---|---|---|
| Mantras you add and their names | On-device (MMKV) | To let you switch between practices |
| Daily and lifetime tap / round counts | On-device (MMKV) | To track your practice history |
| Practice history (up to last 365 days) | On-device (MMKV) | To display the Records screen |
| Language, theme, vibration & sound preferences | On-device (MMKV) | To remember your settings between sessions |
| Daily reminder time and toggle state | On-device (MMKV) | To schedule the local reminder |
You can delete all of this at any time from Settings → Clear all data. Uninstalling the app also removes it.
2. Information Processed by Google Firebase
Divya Mala integrates the following Google Firebase services. Each one is processed by Google as a service provider on our behalf, under Google's privacy and security commitments.
2.1 Firebase Crashlytics — crash reporting
When the app crashes or hits an unhandled error, Crashlytics sends a crash report to Google so we can diagnose and fix the issue. A typical report contains:
- The stack trace and error message
- App version, build, and bundle identifier
- Device model, OS version, available RAM/disk, orientation, and locale
- A randomly generated Crashlytics Installation UUID (resets if you reinstall)
- The truncated IP address from which the report is received (used for delivery, not stored long-term by us)
Crash reports do not include your mantras, counts, history, or any text you enter in the app.
2.2 Firebase Analytics — basic usage analytics
Analytics records aggregate, non-identifying signals so we can understand how the app is used (for example, which screens people open, whether the daily reminder is enabled, app version distribution). The data collected includes:
- Screen views (the name of the screen you navigated to)
- A small number of custom events that describe in-app actions (not the content of those actions)
- App version, OS version, device model, country/region (derived from IP), language, and a Firebase-generated App Instance ID
- Approximate location at the country/region level only, derived from the IP address
- The Google Play install referrer (which Play source or campaign an install came from), used only for aggregate install measurement
We have not enabled Google's Advertising ID (AD_ID) collection, and Analytics is not used for advertising, profiling, or audience-targeting. Recent versions of the Firebase Analytics SDK include Android "Ad Services" attribution permissions (ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_AD_ID) by default; these support Google's privacy-preserving aggregate measurement and are not used by us to show you ads or to build an advertising profile.
2.3 Firebase Remote Config — server-controlled settings
The app fetches a small configuration payload from Firebase on launch so we can adjust non-sensitive settings (for example, default behavior or a future welcome message) without shipping an update. The request sends the App Instance ID, app version, OS, and language. It does not send any of your practice data.
2.4 Where this data is processed
Google operates Firebase from data centers worldwide, including the United States and the European Union. Submitting data to Firebase therefore involves an international transfer for users outside Google's local regions. Google provides Standard Contractual Clauses and other safeguards required by GDPR. For details, see Google's Firebase privacy documentation: https://firebase.google.com/support/privacy.
3. Information We Do Not Collect
We do not collect, process, or receive:
- Your name, email address, phone number, or other contact details
- Your precise location (GPS)
- Your contacts, photos, camera, microphone, files, calendar, or SMS
- The Android Advertising ID (we have not enabled it)
- The text of your mantras, your counts, or your practice history
- Any identifier that on its own personally identifies you to us
4. Permissions Used by the App
Divya Mala requests only the minimum Android permissions needed:
INTERNETandACCESS_NETWORK_STATE— Used by Firebase services described in Section 2 to send data and check connectivity, and reserved by React Native.VIBRATE— Provides haptic feedback when you tap a bead, if vibration is enabled.POST_NOTIFICATIONS(Android 13+) — Displays the local daily practice reminder you schedule. The reminder is generated entirely on your device; no push-notification service is used.SCHEDULE_EXACT_ALARM,RECEIVE_BOOT_COMPLETED,WAKE_LOCK, andFOREGROUND_SERVICE— Added by the on-device notification library so your daily reminder fires at the exact time you set and is automatically re-scheduled after your device restarts. These are used solely for the local reminder; nothing is sent off your device.
We have explicitly removed the Advertising ID (AD_ID) permission that Firebase Analytics would otherwise add, because the app does not use advertising or ad-based tracking. The Firebase Analytics SDK also contributes system-level measurement permissions — ACCESS_ADSERVICES_ATTRIBUTION and ACCESS_ADSERVICES_AD_ID (Android Ad Services attribution APIs) and a binding to the Google Play install-referrer service. These support only Google's aggregate, privacy-preserving install and usage measurement described in Section 2.2; they do not deliver ads to you or identify you to us.
5. Third-Party Libraries
The app is built on open-source libraries. The ones that transmit data off the device are listed in Section 2 (Firebase). The following operate locally and do not transmit your data:
- Notifee — Schedules and displays local notifications on your device only.
- MMKV — Fast local key-value storage on your device.
- React Native Localize — Reads your device's preferred language to pick a default app language.
- React Native Device Info — Used solely to display the installed app version on the Settings screen.
6. Notifications
If you enable the daily reminder, Divya Mala will schedule a local notification on your device. It is not a push notification — nothing is sent to or from our servers (we have none of our own). You can turn it off at any time from Settings → Daily reminder, or from your device's system settings.
7. Children's Privacy
Divya Mala is suitable for users of any age. We do not knowingly target the app at children under 13. Because we do not collect names, contact details, or other directly identifying data, we do not knowingly profile or identify children. If you are a parent or guardian and have questions, contact us through our Google Play Store listing.
8. Data Security
Practice data is stored locally on your device and protected by the security features of your device's operating system (Android). Data sent to Firebase is transmitted over HTTPS and protected by Google's security commitments for Firebase. We do not operate our own servers and do not export Firebase data to any third party.
9. Your Rights
Where applicable, residents of jurisdictions such as the EU/EEA (GDPR), the United Kingdom (UK GDPR), California (CCPA/CPRA), and India (DPDP Act, 2023) have rights regarding their personal data. For the limited data Firebase processes on our behalf:
- Access / portability: Contact us through our Google Play Store listing and we will request the available Firebase records associated with your App Instance ID or Crashlytics UUID where you can provide them.
- Deletion: Uninstalling the app stops further data collection. To request deletion of historical Firebase records tied to identifiers you can supply, contact us through our Google Play Store listing and we will forward the request to Google as required.
- Opt-out: You can disable diagnostic data collection at the OS level by turning off "Usage and diagnostics" in your device's Google settings, which limits what Crashlytics and Analytics can send.
For the data stored locally on your device, you are fully in control: use Settings → Clear all data or uninstall the app to remove it immediately.
10. International Users
Divya Mala is offered worldwide through the Google Play Store. As described in Section 2.4, Firebase services involve processing on Google's servers, which may be located outside your country. Google relies on Standard Contractual Clauses and equivalent safeguards for international transfers.
11. Changes to This Policy
We may update this Privacy Policy from time to time. If we ever change the categories of data we (or our processors) collect — for example, by adding accounts, cloud sync/backup, advertising SDKs, or new analytics events — we will update this policy and revise the Last updated date above before such changes take effect. Material changes will be highlighted in-app or in the Play Store listing.
This document is the version in effect as of the Effective date above.
12. Contact
If you have any questions or requests regarding this Privacy Policy or your privacy while using Divya Mala, you can reach us through the developer contact details published on our Google Play Store listing.
Divya Mala is an independently developed app. It is not affiliated with or endorsed by any religious organization.