Muslim Companion Privacy Policy
Effective Date: July 3, 2026 — Privacy-first Muslim Companion app by MS DevX.
Muslim Companion is designed as a privacy-first application. Your personal data stays on your device. We do not operate any servers that collect, store, or process personal information.
1. Overview & Offline Architecture
Muslim Companion is designed as a privacy-first application. Your personal data stays on your device. We do not operate any servers that collect, store, or process personal information. All prayer time calculations, Qibla direction, and app functionality run entirely on-device.
2. Data We Process
Location (GPS & Manual Coordinates)
What: Device GPS coordinates (latitude and longitude) or manually entered location coordinates (latitude, longitude, and an optional city name).
Why: To calculate accurate prayer times and Qibla direction.
Where: Used entirely on-device. Never transmitted to any server.
Storage:GPS coordinates are not persisted (recalculated fresh on each app launch). Manually entered coordinates are stored locally in the device's private storage (SharedPreferences) and are never uploaded to the cloud.
Notification Permission
What: The Android system permission to post local notifications.
Why: Required on Android 13+ (API 33+) to display prayer time alerts and daily reminders.
Where: Managed entirely by the Android OS. Not transmitted anywhere.
Prayer Completion Log
What: A record of which prayers you have marked as completed each day.
Where: Stored locally in SharedPreferences on your device only.
Retention: Automatically truncated by the OS. Not backed up to any cloud service.
App Settings & Preferences
What: Your calculation method, Asr method, notification toggles, reminder times, Hifz progress.
Where: Stored locally in SharedPreferences. Never leaves your device.
Tasbeeh / Dhikr Counter Data
What: Active preset selection, custom dhikr phrases, current session counts, daily recitation history (logs per day), and vibration/haptic preference.
Where: Stored locally in SharedPreferences. Never leaves your device.
Local User Profile
What: Display name, avatar emoji, avatar color, city label, and preferred location mode (GPS vs. manual).
Why: To personalize the Today screen dashboard (e.g., displaying greetings and avatar icons) and store your preferences for location lookup.
Where: Stored locally in SharedPreferences. This data is strictly offline and is never transmitted to any server.
Local Data Backup (Export & Import)
What: A serialized JSON string containing your settings, custom reminders, bookmarks, Hifz progress, custom dhikr phrases, session counts, and recitation history.
Why: To allow you to manually copy your data to another device or backup locally.
Where: Handled strictly on-device. The data is copied to your clipboard when exporting and read from your input field when importing. It is never transmitted to any cloud server or database.
In-App Purchase (when enabled)
What: Purchase status of the “Remove Ads” product.
Why: To determine whether to show App Open Ads.
Where: Verified against the Google Play Billing Library on-device. A local cache flag is stored in SharedPreferences. Purchase receipts are handled entirely by Google Play. We do not receive or store payment information.
3. Data We Do NOT Collect
Muslim Companion never collects, transmits, or stores the following data:
- Name, email address, phone number
- Device identifiers (IMEI, Android ID)
- Browsing history, contacts, microphone, camera
- Crash reports sent to any cloud service
- Analytics or usage telemetry
- Quran reading history uploaded to any server
- Hifz progress synchronized to any cloud
- Islamic calendar notes or events synced to any cloud
4. Advertising (App Open Ad)
When enabled at build time (ENABLE_ADS=true): We display App Open Ads only, provided by Google AdMob. Google may use your Advertising ID to serve personalized ads. The ad is shown at most once every 4 hours and never to users who purchased “Remove Ads”. Google's privacy policy applies to AdMob data: policies.google.com/privacy. When ENABLE_ADS=false (the default for development builds), no ad SDK is initialized and no data is shared with Google AdMob.
5. Permissions Explained
| Permission | Required | Purpose |
|---|---|---|
| ACCESS_FINE_LOCATION | Yes* | Prayer time calculation, Qibla direction. (Graceful failure if denied) |
| ACCESS_COARSE_LOCATION | No | Fallback location when GPS unavailable. |
| POST_NOTIFICATIONS | No | Prayer time alerts on Android 13+. (Reminders silently skipped if denied) |
| SCHEDULE_EXACT_ALARM | No | Precise prayer time scheduling. (Falls back to inexact) |
| USE_EXACT_ALARM | No | Precise alarms on Android 14+. (Falls back to inexact) |
| INTERNET | Conditional | AdMob and IAP when enabled. |
| RECEIVE_BOOT_COMPLETED | No | Reschedule notifications after reboot. |
| VIBRATE | No | Notification vibration & Tasbeeh tactile feedback. |
* ACCESS_FINE_LOCATION is conditionally required — needed for GPS-based location but gracefully disabled when using manual coordinates.
6. Children's Privacy
Muslim Companion does not knowingly collect any data from children under 13. The app contains no content directed at children in the sense of COPPA.
7. Contact Us
If you have any questions or concerns about this Privacy Policy, please reach out to us at msdevxsupport@gmail.com.