← AL-Qamar

Privacy Policy

Last updated: 6 April 2026

AL-Qamar ("the App") is developed by Muntakhab Hasani. This policy explains what data the App collects, how it is used, and your rights.

1. Account and Authentication (Optional)

The App offers optional sign-in via Apple, Google, or email/password. Signing in enables:

• Cloud sync of your settings, bookmarks, and reading progress across devices
• Community features (creating events, mosque voting, group Quran reading)

If you choose not to sign in, you can still use all core features (prayer times, Quran, duas, calendar, etc.) without any account. When you sign in, we store your email address and a unique user ID in Firebase Authentication (operated by Google).

2. Data We Collect

For all users (no account required):

• A random device identifier (UUID) stored locally — not linked to your identity
• App settings, bookmarks, reading progress — stored on your device only
• An Expo Push Token for receiving push notifications — stored in Firebase Firestore alongside your app language and platform (iOS/Android)

For signed-in users:

• Email address (from your Apple, Google, or email sign-in)
• Settings, bookmarks, and reading progress synced to Firebase Firestore
• Community contributions (events you create, mosque votes, group memberships)

3. Location Data

The App requests location permission solely to calculate prayer times, determine Qibla direction, find nearby mosques, and compute the local Hijri date. Your location is processed on your device and stored in encrypted local storage (SecureStore). Location data is not synced to the cloud. When you search for a location, your search query is sent to the Photon geocoding service (komoot.de) and mosque data is fetched from the Overpass API (OpenStreetMap). You can use the App without granting location permission by searching for a city manually.

4. Data Stored on Your Device

The App stores your preferences and reading data locally, including: settings, bookmarks, reading progress, notes, prayer tracker counts, calendar events, starred events, and downloaded audio files. Sensitive data (location) is stored in encrypted storage (SecureStore). This data never leaves your device unless you enable cloud sync.

5. Cloud Sync

When you sign in, your data is synced to Firebase Firestore (operated by Google). Sync uses real-time listeners with a 3-second debounce. Location data is excluded from cloud sync. You can sign out at any time to stop sync.

6. Community Events

When you create community events, the data you provide (title, description, dates, location, Instagram handle, poster image) is stored in Firebase Firestore and visible to other users. Event posters you upload are compressed and stored as part of the event data. Community contributions are associated with your user ID. Events can be edited or deleted by the creator.

7. Image Processing (AI)

When you upload an event poster for auto-fill, the image is sent to the Google Gemini API for text and detail extraction (event title, description, dates, location, Instagram handle). The image is also sent to the Google Cloud Vision API for safety checks (detecting inappropriate content). These services process the data according to Google's Cloud Privacy Notice. Images are not stored by us beyond the event posting.

8. Push Notifications

The App collects an Expo Push Token on launch (with your permission) to enable remote push notifications. Tokens are stored in Firebase Firestore with your app language and platform. Push notifications may be sent by administrators for announcements, event reminders, and Islamic occasion alerts. Notification content may be auto-translated to your app language using the Google Gemini API. You can disable notifications at any time in your device settings.

9. Content Moderation

Community content is moderated by administrators and moderators. Uploaded images are checked for inappropriate content using AI (Google Vision SafeSearch). Text content is checked against a keyword filter. Users who violate community guidelines may have their content hidden and their account suspended. Moderation records and audit logs are retained for safety purposes.

10. Third-Party Services

• Firebase (Google) — Authentication, Firestore database, Cloud Functions, Hosting. Firebase Privacy.
• Google Gemini API — Event poster text extraction and push notification translation. Gemini Terms.
• Google Cloud Vision — Image safety checks for event posters. Privacy Notice.
• Expo Push Notifications — Delivery of remote push notifications. Expo Privacy.
• Photon (komoot.de) — Location search autocomplete and reverse geocoding.
• Overpass API (OpenStreetMap) — Mosque and community centre data.
• quran.com API — Word-by-word Quran data and audio.
• alquran.cloud — Quran text and translations.
• Apple/Google Maps — Map display, subject to their privacy policies.

11. Analytics

The App sends a single anonymous network request on launch to track general usage counts. This request contains no personal data, no device identifiers, and no location information. You can opt out of this in Settings.

12. Data Retention

• Local data: Stored until you uninstall the App or clear its data.
• Firestore sync data: Stored while your account is active. Deleted within 30 days of account deletion request.
• Push tokens: Automatically removed when they become invalid (device unregistered).
• Community contributions: Events are automatically cleaned up (poster images removed) 1 month after the event date.
• Reports and moderation data: Retained for as long as needed for safety and legal compliance.

13. Your Rights

You have the right to:

• Access your data: Use the in-app backup/export feature to download your settings and reading data.
• Delete your account: Go to Settings and tap "Delete Account". Your account will be deactivated immediately and local data cleared. Server data is retained for 30 days for recovery, then permanently deleted.
• Withdraw consent: You can sign out, disable cloud sync, disable notifications, or revoke location permission at any time.
• Data portability: Export your data via the in-app backup feature.

To exercise any of these rights, use the in-app settings or contact us at info@djali.co.uk.

14. Children's Privacy

The App does not knowingly collect personal data from children under 13 (or under 16 in the EU/UK). If you believe a child has provided us with personal data, please contact us.

15. Changes to This Policy

We may update this policy from time to time. The latest version will always be available at this page with the updated date above.

16. Contact

If you have questions about this policy or wish to exercise your data rights, contact us via the in-app feedback form or email info@djali.co.uk.