Facemosque · Last updated: 5 September 2026
This Privacy Policy explains how Facemosque ("the app", "we", "us") handles your information. Facemosque is a prayer companion app that helps you find your local mosque, view prayer times, receive prayer reminders, and use a digital tasbih.
The data controller for the purposes of the EU General Data Protection Regulation (GDPR) is:
Contact: facemosque@gmail.com
If you grant location permission, the app uses your device location to sort the mosque directory by distance and to show how far each mosque is from you. The app requests location only while it is in use, and it is never collected in the background.
Your coordinates are not stored on our servers. However, to find mosques near you that are not yet in our own directory, the app sends your approximate coordinates to the Google Places API as part of a "search nearby" request. Google processes that request as an independent controller under Google's Privacy Policy. No identifier of you or your device is attached to the request.
You can deny or revoke location permission at any time in your device settings — the app will still work, but mosques will not be sorted by distance.
When you search the directory by city or place name, that text is sent to the Google Places API so results can be returned. We do not store your search history, and search text is never included in analytics or crash reports.
The following are saved locally on your device, not on our servers, so the app remembers your choices: your pinned mosque, your selected language, your theme, your notification and tasbih settings, your mosque announcements choice, and your analytics choice. The app also generates a random identifier for this installation, used only if you turn mosque announcements on (see section 2.5). This data stays on your device and is removed when you uninstall the app.
All prayer time, iqamah, Jummah and fasting reminders are scheduled and delivered locally on your device. They are calculated from prayer times the app has already downloaded, they work with no internet connection, and no server is involved in sending them. Disabling notifications in your device settings stops these reminders.
Separately from the reminders above, your mosque can send you announcements — Eid prayer times, changes to the Jummah time, funeral prayers, classes and similar notices. Because these are written by your mosque after you installed the app, they have to be delivered from a server, which means the app must be reachable. This is off by default. Nothing described here happens unless you turn it on, either from the prompt shown after you pin a mosque or from the switch in Settings → Notifications.
If you turn it on, the following is sent to our backend and stored there:
Only the verified administrators of your pinned mosque can send these announcements. They are never used for advertising or marketing, and the record is never combined with crash reporting or analytics data. Turning the switch off in Settings → Notifications, unpinning your mosque, or revoking notification permission in your device settings deletes the stored record. Uninstalling the app has the same effect once Apple or Google reports the device as unregistered.
To show mosque information, prayer times, events, and announcements, the app requests this content from our backend service. These requests do not include your identity or your coordinates; they contain only the standard technical details that any internet request requires, such as your device's IP address and the app version.
So that we can find and fix the faults that make the app freeze or close unexpectedly, Facemosque uses Firebase Crashlytics, a service provided by Google. When the app crashes or encounters a handled error, the following is sent:
Crash reporting contains nothing that identifies you and nothing that reveals your religious practice. This is why it can run without asking you first — see section 4.
Facemosque can also collect anonymous usage statistics through Google Analytics for Firebase, so we can see which features are actually used and where people get stuck.
This is switched off by default. It is disabled at the operating-system level from the moment the app starts, so nothing is collected before you have answered. The first time you open Facemosque you are shown a consent screen with two equally weighted choices and no way to skip past it. Nothing in this section is collected unless you choose "Allow".
If — and only if — you allow it, the following is collected:
| What | Details included |
|---|---|
| Screens you open | The name of the screen, e.g. "prayer times", "tasbih" |
| Language changed | The language you changed from and to |
| Mosque pinned or unpinned | The mosque's id, name, and city |
| Prayer alerts set up or toggled | Which prayer, whether it was turned on or off, and the pinned mosque |
| Tasbih session finished | The final count, your target, which dhikr, and rounds completed — sent once when the session ends. Individual taps are never recorded. |
| Attached to every event | App version, release version, and whether the build is development or production |
| Collected automatically by Google | A random app-instance identifier, device model, operating system version, and an approximate country or region that Google derives from your IP address on its servers |
Your precise location is never sent to analytics, with or without consent.
The app checks for over-the-air content updates from Expo's update service
(u.expo.dev). That check sends the app's runtime version and basic device
platform information so the correct update can be returned. Where the operating system offers
one, the app may also use the platform app store's own in-app update mechanism, which is
handled entirely by that store.
For users in the European Economic Area and the United Kingdom, we rely on the following legal bases under Article 6 GDPR:
Why analytics and announcements are treated differently. Knowing which mosque a person follows can reveal their religious beliefs, which Article 9 GDPR treats as a special category of personal data requiring your explicit consent. Both features touch it: the analytics events name the mosque you pinned, and an announcement registration stores that mosque's id next to an identifier for your installation. So both are off until you actively turn them on, both are explained in the app before anything is sent rather than only here, both present their options with nothing pre-selected, and declining either is never re-asked. Crash reporting — which runs without consent — is designed so it can never carry that information: it records only whether a mosque is pinned, never which one.
We do not share your personal information with third parties for their own marketing purposes, and we never sell it. Data is shared only with the following service providers, only for the purposes described above:
| Recipient | What it receives | Why |
|---|---|---|
| Google (Firebase Crashlytics) | Crash and error reports, and the diagnostic details in section 2.7 | Diagnosing and fixing faults |
| Google (Analytics for Firebase) | The events in section 2.8 — only with your consent | Understanding feature usage |
| Google (Places API) | Approximate coordinates or your city search text | Finding nearby mosques |
| Expo | App runtime version and device platform | Delivering app updates |
| Our own backend | Standard request metadata such as IP address. Additionally, only if you turn mosque announcements on: your push token, the random installation identifier, your pinned mosque's id, platform, app version and language | Serving mosque and prayer time content, and sending mosque announcements |
| Expo (Expo Push Service) | Your push token and the content of an announcement — only if you turn mosque announcements on | Delivering announcements to your device |
| Apple (Apple Push Notification service) | Your push token and the content of an announcement, on iOS — only if you turn mosque announcements on | Delivering announcements to your device |
| Google (Firebase Cloud Messaging) | Your push token and the content of an announcement, on Android — only if you turn mosque announcements on | Delivering announcements to your device |
We may also disclose information if we are legally required to do so.
Google, Apple and Expo may process the data described above on servers outside the European Economic Area, including in the United States. Those transfers are covered by the European Commission's Standard Contractual Clauses and, where applicable, by the recipient's certification under the EU–U.S. Data Privacy Framework. You can read Firebase's privacy documentation for details of how Google handles this data.
Requesting deletion. Turning the analytics switch off in Settings → Privacy triggers Google's data-deletion request for your installation. Turning the mosque announcements switch off in Settings → Notifications deletes the registration from our servers. Uninstalling the app removes everything held locally. If you would like us to confirm deletion or to handle a request manually, email facemosque@gmail.com and we will respond within 30 days.
If you are in the EEA or the UK, you have the right to access, rectify, erase, restrict, and object to the processing of your personal data, and the right to data portability. Where we rely on consent, you may withdraw it at any time without affecting processing already carried out. To exercise any of these rights, contact facemosque@gmail.com.
Please note that because Facemosque has no accounts and collects no identifiers that point to you personally, we are usually unable to locate a specific individual's records. In practice this means that turning analytics off and uninstalling the app is the most complete way to exercise your right to erasure.
You also have the right to lodge a complaint with your national data protection authority.
Facemosque is suitable for a general audience and is not directed at children. We do not knowingly collect personal information from children, and the app does not require any personal details to be used. If you believe a child has provided us with personal data, please contact us and we will delete it.
Requests between the app and our server, and between the app and the services listed in section 6, use encrypted connections (HTTPS/TLS). While no method of transmission over the internet is completely secure, we take reasonable measures to protect the limited data the app handles, and we minimise what is collected in the first place.
We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page. If a change materially expands what we collect, we will ask for your consent again before it takes effect.
If you have any questions about this Privacy Policy or how your data is handled, contact us at: