Data Safety

Helper summary for the Google Play Console Data safety form. This page does not replace the form — declare accurately based on your build.

Full details: Privacy Policy. App is not for children.

Does the App collect user data?

The App processes location (with permission) and stores app activity / preferences on device. It does not require account sign-in.

Suggested Data safety declarations

Location

  • Approximate location — Yes (for prayer times / place label)
  • Precise location — Yes (for Qibla accuracy), if your build requests fine location
  • Collected / processed — for App functionality
  • Ephemeral / on-device — primarily processed on device; not used to build a cloud movement profile by us

App info & performance / App activity

  • App interactions / settings (language, prayer toggles, dhikr history) stored on device
  • Crash logs — may be collected by Google Play / Android if enabled by the platform

Personal info / Financial / Photos / Contacts / etc.

  • Account info — No (no accounts)
  • Name, email inside App — No (email only if user contacts support)
  • Financial info — No
  • Photos, videos, contacts, SMS — No
  • Health / fitness — No

Security practices

  • Data is encrypted in transit — when the device uses HTTPS OS APIs (e.g. geocoding)
  • Users can request deletion — see Data Deletion (on-device clear / uninstall; no cloud account)
  • Committed to Google Play Families Policy — No (App not for children)

Data sharing

  • We do not sell data
  • We do not share user data with third-party advertisers
  • Platform service providers (Google) may process data as needed to provide OS / Play features

Permissions typically used

  • Location (coarse / fine)
  • Notifications / alarms for Azan reminders
  • Vibrate (alerts)
  • Internet (geocoding / platform services as applicable)