Google Play Data Safety Summary
Based on verified code and permission paths for io.meeddev.qalby. The Play Console form must match the final shipped AAB.
| Data type | Collected? | Shared? | Purpose | Required? |
|---|---|---|---|---|
| Precise location | Yes, transmitted only when the feature is used | No; geocoding/Aladhan process it as feature providers | City and prayer times | Optional |
| User content (Munajat) | No | No | Private on-device journal | Optional, local |
| App activity (mood, counters, favorites) | No | No | Local personalization | Optional, local |
| Personal info / account | No | No | No account feature | Not applicable |
| Diagnostics, advertising ID, payment info | No | No | No related SDK or flow | Not applicable |
Security and deletion
- Network requests use HTTPS.
- Munajat text is in secure local storage; Android backup is disabled.
- In-app item deletion and system-level full data deletion are available.
Child safety and target audience
The target audience and age declaration must match the app's actual content in Play Console. Claims about knowingly collecting data from children, child-directed advertising, or anonymous/random chat may be made only after verifying the real product behavior and applicable Play policies.
Policy and release consistency
This summary must remain consistent with the privacy policy, in-app disclosures, permissions, third-party SDKs, and the current binary release. Revisit the Play Console Data Safety form whenever those facts change.