Privacy Policy — iPhone & iPad

1. What we do and don't collect

• No sign-up — no name, email, or phone number is required, and there is no account to create or delete.
• Your worship records, notes, bookmarks, reading positions and settings are never sent to any server.
• No advertising, no advertising identifier (IDFA), no device fingerprinting, no tracking as defined by Apple's App Tracking Transparency.
• We do not build individual user profiles and we sell data to no one.
• The app uses Google Firebase for anonymous usage statistics and announcements (section 8a).
• The optional “Nearby mosques” page uses your location while it is open, and with internet sends it through our server to Google Places (section 6a).

How this matches the App Store “App Privacy” label. None of the data below is linked to your identity (the app has no account, name or email to link it to), and none of it is used to track you.

2. Permissions the app asks for, and why

Every permission below is optional and can be changed at any time in the iOS Settings app → নামাজ শিক্ষা. If you decline one, only the feature that needs it stops working — the rest of the app continues normally. The app never makes access to its content depend on granting a permission.

3. Location

• Location is used to calculate prayer times and the Qibla direction, for the optional weather display, and on the optional “Nearby mosques” page.
• Prayer times and Qibla are calculated entirely on your device — for these, your location is not sent anywhere.
• If the optional weather display is on, a coarse coordinate (rounded to roughly 11 km) is sent to the weather sources (section 7).
• On the “Nearby mosques” page, while it is open and you are online, your coordinates are sent through our server to Google Places to find mosques around you (section 6a). This is the only case in which precise coordinates leave your device.
• For statistics, the district/area you selected in the app is sent to Firebase, and Google derives a coarse country/city-level location from the IP address (section 8a). GPS coordinates are never sent to Firebase.
• Location is used only while you are using the app. There is no background location access.
• The app works without location permission; it then uses the place you select.

4. Data stored on your device

Everything below is written to the app's own sandboxed storage on your iPhone or iPad. The app does not send any of it to a server, and we cannot see any of it.

• Worship records: which prayers you ticked, missed-prayer (qaza) counts, fasts, taraweeh nights and daily deeds.
• Reading state: bookmarks and last-read verse.
• Your own writing: personal notes — duas, intentions and goals you type in.
• Counts and settings: tasbih totals, theme, chosen translation and reciter, calculation method, reminder preferences.
• Downloads: Quran translations, recitation audio, Hafezi Quran pages and adhan tones you download.
• Prayer-time location: the place you picked; if you use “current location”, also the last location fix, so times stay correct the next time you open the app. It stays on the device only.
• Some of this reflects your religious practice. It is exactly the kind of information we made sure the app never sends anywhere — it is not included in statistics and is sent to no server. (It leaves the device only if you yourself create and share a backup file — section 5.)
• iCloud / computer backups: if iCloud Backup (or a Finder/iTunes backup) is turned on for your device, iOS itself may include the app's data in that backup of your own device, so it can be restored on a new iPhone. That copy belongs to your Apple Account; we cannot see it.

5. Sharing, copying and backup — actions you start

Nothing here happens on its own. Each of these runs only when you tap the button, and the data goes only where you send it — never to us.

• Share: you can share a verse, hadith, quotation, dua or name of Allah to another app through the iOS share sheet. Only the text you chose is passed on.
• Copy: tapping “copy” puts that text on your clipboard, as any app does. The app does not read your clipboard.
• Backup: creates a single .json file containing your bookmarks, prayer tracker, qaza counts, fasts, taraweeh, daily deeds, reading positions, reminder preferences, app settings — and your personal notes, so that everything comes back on a new device. It is handed to the iOS share sheet — you decide whether it goes to Files, iCloud Drive, a chat or elsewhere. We never receive it.
  Note: because the backup file contains the duas, intentions and goals you wrote in your personal notes, think before sharing it with anyone.
• Restore: reads a backup file you pick. If the file is not recognised, nothing is changed at all.
• External links: the Facebook group link, the App Store page and directions in Google Maps open outside the app. From that point their own policies apply.

6. When the internet is used, and who receives what

The app connects to the services below. As with visiting any website, the service you connect to can see your device's IP address and the file requested. Every connection uses HTTPS.

Once content is downloaded, everything works fully offline. Apart from Firebase (section 8a) and the random, app-generated ID that the Nearby mosques page sends to our own server (section 6a), no identifier of yours is sent to any of these services.

6a. Nearby mosques (optional)

• On the device: to show how far away nearby mosques are and in which direction, the app uses your location, only while the page is open. Distances and directions are calculated on your device. The built-in mosque list comes from OpenStreetMap (and Overture Maps).
• Nearby search (with internet): to show all mosques around you, the app sends your latitude/longitude to our server namaj-config.duetrackbd.workers.dev (hosted on Cloudflare), together with a random anonymous ID that the app generates itself — it is not a hardware ID and not the advertising identifier. Our server forwards only the location to the Google Places API, which returns the nearby mosques.
• What our server keeps: neither your location nor Google's results are stored on our server. The anonymous ID is hashed immediately and used only to count how many searches a device made that day, so the free daily quota stays available for everyone; that count expires after about 2 days.
• Area list: to fetch the up-to-date OpenStreetMap list for your area, only the number of a grid cell of about 28 km is sent — not your coordinates.
• “Add a mosque here”: only if you tap it yourself, the mosque name you type and your current location (as the mosque's location) are sent to our server. The proposal is stored with a short hash of the anonymous ID and a short hash of your network address (never the raw ID or IP address) — used only to count proposals per day and to prevent abuse. After review, the mosque (its name and location only) may appear in everyone's list. Your name or any other information about you is not sent.

7. Weather (optional)

• The home-screen sky shows temperature and clouds using two open sources — MET Norway and Open-Meteo.
• Only a latitude/longitude rounded to one decimal (a cell of roughly 11 km) is sent. No name, ID or device identifier accompanies it.
• Requested at most once every 15 minutes while the app is open; the last result is cached on the device.
• Weather can be turned off in Settings → Weather (inside the app), after which no request is made.

8. Notifications

• Prayer-time reminders and adhan alerts are scheduled on your device; no internet is required for them.
• We may occasionally send an announcement through Firebase Cloud Messaging and Apple's push service — for example a Ramadan or Eid date, a government holiday or a correction.
• Notifications are never used for advertising, promotion or marketing, and never carry personal information.
• Reminders can be turned off inside the app, all together or per prayer. All notifications from the app, including announcements, can be turned off in iOS Settings → Notifications → নামাজ শিক্ষা.

8a. Usage statistics and announcements (Google Firebase)

The app includes Google Analytics for Firebase and Firebase Cloud Messaging. Google processes this data as our service provider.

• What is collected: app-lifecycle events such as app opens, screens viewed and session length; notification received/opened events; app version, iOS version and device model; a random per-installation identifier (the Firebase app-instance ID); Apple's identifier for vendor (IDFV), which Firebase uses on iOS; a coarse location Google derives from the IP address; and the district/area you selected in the app.
• Not collected: the advertising identifier (IDFA). The iOS app is built without advertising-ID support, does not link Apple's AdSupport framework and does not ask for tracking permission. Ad-personalisation signals are switched off.
• Notification token: Cloud Messaging creates a token linked to Apple's push token so announcements can reach the device. All installations are subscribed to one shared topic, plus a topic for the country of the location you picked (for example “Bangladesh”, or an “expatriate” topic when abroad) — country only, never city or location. We never keep a list of tokens.
• Why: to know how many people use the app, which features and districts need the most attention, and to send important announcements.
• What we see: aggregated numbers only (for example active users or how many devices opened an announcement). We cannot see your name, and nothing tells us what you read or how you pray.
• Never sent to Firebase: worship records, notes, bookmarks, Quran reading positions, GPS coordinates, contacts or the advertising identifier.
• Retention: Google deletes event-level data after the retention period set in Google Analytics (at most 14 months).

9. Apple and device services

• Rating prompt: after some use, Apple's own rating prompt may appear. Apple decides when and how often it is shown, no question is asked before it, and we are never told who rated or what they rated.
• Read-aloud: reading the Bengali meaning of the Quran aloud uses the text-to-speech voices built into iOS; the app itself sends nothing for this.
• Any data handling by these Apple services is governed by Apple's privacy policy, not ours.

10. Data retention, withdrawing consent and deletion

• We keep no database of users, and none of your writing, records or reading data is stored on any server. Our settings server stores app settings and the names and locations of mosques that users have proposed (section 6a), each with short hashes for abuse prevention — never anyone's name or identity. Approved mosques (name and location only) are shown to all users; rejected proposals are deleted.
• For the nearby-mosque search, your location and Google's results are not stored on our server; the hashed per-device daily search count expires after about 2 days. Cloudflare may keep short-lived technical request logs, as any web host does.
• Usage statistics are retained by Google Firebase as described in section 8a.
• Withdrawing consent: you can stop each kind of data from leaving your device at any time — location: iOS Settings → Privacy & Security → Location Services → নামাজ শিক্ষা → Never (or turn Precise Location off); notifications and announcements: iOS Settings → Notifications → নামাজ শিক্ষা; weather: in the app, Settings → Weather; nearby search: simply don't open the Nearby mosques page.
• Deleting data on your device: delete the app (touch and hold the icon → Remove App → Delete App). This permanently removes everything the app saved, and also resets the Firebase app-instance ID. (Note: iOS “Offload App” keeps your data; choose Delete App to remove it.) Downloaded files can also be removed individually inside the app (More → Downloads · আরও → ডাউনলোড).
• Asking us to delete data: if you proposed a mosque and want it removed, or have any other deletion request, email support@duetrack.bd. Because we hold nothing linked to your identity, please describe the data (for example the mosque name and area); we will delete anything we can find and reply within 7 days.
• There is no account to delete.

11. Security

• All network requests use HTTPS (encrypted in transit).
• App data is kept in the app's iOS sandbox, which other apps cannot read, and is protected by iOS data protection when the device is locked.
• We hold no user database of our own, so there is no store of personal data on our side that could be breached.

12. Third parties, sharing and selling

• No advertisers or data brokers receive anything. The app contains no advertising SDK, and we transfer no data for advertising or marketing.
• Google Firebase processes usage statistics on our behalf as a service provider (section 8a).
• Data is shared with other companies for exactly two features: the coarse weather coordinate sent to MET Norway and Open-Meteo (section 7), and, on the optional Nearby mosques page, your location sent through our server to Google Places (section 6a). Both are used only to make that feature work.
• We use only third parties whose published privacy commitments provide the same or equal protection of user data as this policy, and we pass them only the data described here, only for the purpose described here.
• We would only disclose information if legally compelled — and we hold none linked to you to disclose.

13. Children's privacy

• The app's content is suitable for all ages, but it is not directed at children under 13 and is not in the App Store's Kids category.
• We ask no one — including children — for personal information. There are no ads and no in-app purchases.

14. Religious content and its sources

• Every Quran verse, hadith and quotation in the app carries its reference.
• The full list of sources, translators, reciters and licences is published at Sources & Licences.

15. What this app never does

• It does not access your camera, microphone, contacts, calendar, photos, health data or files — except files you pick yourself (a custom adhan tone or a backup file to restore).
• It does not track you, does not use the advertising identifier and never shows the tracking-permission prompt.
• It sends us no crash reports or diagnostics. (If you have turned on “Share With App Developers” in iOS, Apple may share crash reports with us under Apple's own terms.)
• It shows no advertising and has no account, no login and no in-app purchase.

16. Changes to this policy

• If this policy changes, the updated version will be posted on this page with a new date, and material changes will be mentioned in the app's release notes.
• We will not start using data in a new way without asking for your permission first.