Effective: 16.11.2026 · Data controller: BUSATER YAZILIM A.Ş.
In short
Prayer times and the Qibla direction are calculated on your device. Your location is used for that calculation and is not sent to our server; only when you tap Find nearby mosques is an approximate location (~1 km) sent for the mosque search, and it is not stored. An account is optional: prayer times, Qibla, notifications, the Ramadan timetable, the Quran, personal khatm, the journal and the zakat calculator work without one. Your worship records (missed prayers log, prayer and fasting journal) never leave your device unless you explicitly allow it. The free version shows Google AdMob ads; there are no ads on the prayer times, Qibla and notification screens, and none at all with EzanQ Pro (section 8). Your data is not sold.
1. Location
Location permission is requested only when you tap Use my location, and location is used only while the app is open (never in the background). Coordinates are rounded to about 1 km and used on your device to calculate prayer times and the Qibla. To turn the location into a place name, your device's operating system (Apple on iOS, Google on Android) uses its geocoding service. You can also pick a city from the list; then location permission is never requested. The location sent for the mosque search is described in section 6.
2. Notifications
Prayer notifications are scheduled on your device; nothing is sent to our server for them. If you have allowed notifications, the app stores your device's notification token, platform, app version and language together with your installation ID on our server so that it can send you a single "A new update is available" notification when a new version is released in the store. Delivery goes through Expo and Apple/Google notification services. The token is used for this purpose only; no other notifications or ads are sent. If you turn notifications off, none arrive; deleting your installation data or account also deletes the token.
3. Account (optional)
You can sign in with Apple or Google. Signing in syncs your saved cities and preferences across your devices and links Pro to your account.
- The identity token from Apple/Google is verified on our server and not stored. Your account is kept as a one-way hash (SHA-256) of your provider identifier; your name and email are not stored on our server and are only shown on your device.
- Synced settings are stored on our server: your saved cities (name, country, approximate coordinates and time zone), selected city, calculation method, notification preferences, theme and language. Only you can read this document.
- With Sign in with Apple, the refresh token Apple issues is stored encrypted so that we can revoke it with Apple when you delete your account.
4. Worship records (only with your explicit consent)
The missed prayers log and the prayer and fasting journal reveal religious belief, so they are special-category personal data (GDPR Art. 9, KVKK Art. 6). By default they are kept only on your device. If, after signing in, you turn on Settings → Account → Sync missed prayers log and journal and accept the separate consent dialog, they are stored on our server with your account so they sync across your devices, together with the time of your consent. You can withdraw consent at any time with the same switch; the copy on our server is then removed. Signing out resets the consent, and deleting your account deletes the records. These records are never added to product usage data.
5. Group khatm (optional, requires an account)
When you create a group khatm or join one with an invite code, our server stores the group name, your optional display name, the juz you take and finish, and when. Other members see only your display name and juz status; your account ID and email are never shown. Leaving the group or deleting your account deletes your membership.
6. Nearby mosques
When you tap Find nearby mosques, your location is rounded to about 1 km (0.01°) and sent to our server, which searches OpenStreetMap data (the Overpass service) for mosques. No account or installation ID is sent with this request and the location is not stored; the response is cached for that ~1 km area only, not tied to any person, for up to one week. Directions open in your device's maps app.
7. Product usage data
To improve the app, the following is sent to our server:
- a randomly generated installation ID (a new one is created when the app is reinstalled; it is not your name, email or a device identifier),
- the name and time of product events: first open, app open, onboarding started and completed, sign-in, Qibla opened, notifications enabled, Pro screen opened, plan selected, purchase started/completed/cancelled/failed, restore, opening the Quran, khatm, group khatm, mosque search, journal and zakat screens, language change, ad events (format and outcome only, section 8); small details tied to the event (plan type, where the screen was opened from, whether results were found). Which surah you read or which prayer you mark is never sent,
- platform (iOS/Android), OS and app version, build number, device type (phone/tablet), whether it is a simulator, and your device's region and language settings,
- the country the connection comes from (two-letter code; the IP address is not stored),
- if you are signed in, your account hash (the SHA-256 hash above),
- if an error occurs in the app, only the error type (e.g. “TypeError”) and whether it closed the app; the error message and screen content are never sent,
- that the store’s rating prompt was requested (the rating you give never reaches us).
Location, saved cities, worship records, name and email are never added to these events.
Install source. To measure whether you installed the app from an ad, once after installation: on iPhone and iPad our server asks Apple about Apple’s Apple Ads attribution token; only the campaign, ad group and keyword IDs, the campaign’s country and whether the ad was tapped are stored, and the token itself is not. On Android, Google Play’s install referrer is read on your device; only the source, medium and campaign name and whether there was a Google Ads click are sent, and the click ID is not. No advertising identifier (IDFA/GAID) is used for this measurement; this information is stored with the installation ID, is not shared with anyone and is deleted when the installation or the account is deleted.
8. Ads (Google AdMob)
The free version shows ads through Google AdMob: a banner at the bottom or top of some screens, an occasional full-screen ad between screens, an app open ad when you return to the app, and, if you choose, a rewarded ad you watch for 10 minutes without ads. There are no ads on the prayer times, Qibla, notifications, purchase, tasbih counter and Quran reading screens; no app open ad is shown when you open the app by tapping a prayer notification. EzanQ Pro owners see no ads at all. Ads start on Android with version 1.1.5; on iPhone and iPad the iPhone/iPad rules below apply once a version with ads is released.
To show and measure ads and to prevent abuse, the Google Mobile Ads SDK sends the following directly from your device to Google: your IP address (to estimate general location), ad interactions (impressions, taps, video views), diagnostic information about the performance of the app and the SDK, and device identifiers (on Android the advertising ID and app set ID; on iPhone and iPad the advertising identifier only if you allow it). This data does not reach our server; Google processes it under its own policies: How Google uses information from ads · Google Privacy Policy.
Consent and permission. In the European Economic Area, the United Kingdom and Switzerland, Google's consent message is shown before any ad is requested; you can refuse personalised ads. On iPhone and iPad, Apple's tracking permission prompt appears after the welcome steps; if you do not allow it, only non-personalised ads are requested and the app works the same. You can change it later in iPhone Settings → Privacy & Security → Tracking. On Android you can reset or delete your advertising ID in your phone's Settings → Google → Ads.
Our server records only the ad format (banner, interstitial, app open, rewarded) and the outcome (seen, reward earned, failed to load), as product usage data linked to your installation ID (section 7). The advertiser, the ad content, the ad unit and earnings are not recorded.
9. Purchases
Pro purchases are processed by Apple and Google; your card details never reach the app. Entitlement is verified through RevenueCat, which processes the purchaser ID (random when not signed in, your account ID when signed in), store, product, price and country. Store notifications are recorded on our server with transaction ID, product, store, country, amount and environment (live/test).
10. Official prayer time data
When data from the Presidency of Religious Affairs (Diyanet) is connected, the app requests the monthly times for the selected location in Türkiye from our server using only the province and district name (e.g. "Ankara/Keçiören"). Neither your coordinates nor your identity are sent.
11. Quran reading and zakat
In Türkiye, Quran reading opens the Quran portal of the Presidency of Religious Affairs (kuran.diyanet.gov.tr) in an in-app browser; the portal's own privacy terms apply on that page. Bookmarks, where you left off and personal khatm are kept only on your device. Amounts you enter in the zakat calculator are not stored and not sent anywhere.
12. Infrastructure and transfers
Our server runs on Cloudflare (Workers and D1); purchase verification uses RevenueCat; sign-in uses Apple and Google services; ads in the free version are served by Google AdMob; the mosque search queries the OpenStreetMap community's Overpass servers with an approximate location. These providers may be located outside Türkiye, so processing may involve transfers abroad. Your data is not sold. Data on our server is not shared for advertising or marketing; the only data that goes to Google for ads is described in section 8 and is sent directly by the Google Mobile Ads SDK.
13. Retention
Your account, synced settings and group khatm membership are kept until you delete the account; synced worship records are deleted when you withdraw consent or delete the account. Usage records are kept until you delete them; no automatic deletion is applied on the server today. Store transaction records are kept for the legally required period as financial records.
14. Children
The app is intended for a general audience and does not knowingly collect account data from children under 13.
15. Your rights
You have the right to access, correct and delete your personal data, to object to processing and to data portability. You can delete your account in the app: Settings → Account → Delete account. If you are not signed in, Settings → Account → Delete usage data for this device deletes this installation's records. Details: Account and data deletion. For other requests: bsdigitalapp@gmail.com.
16. Changes
If this policy changes, the effective date is updated and the current version is published at this address.
Contact
BUSATER YAZILIM A.Ş.
Etlik Mah. Etlik Cad. Çulha No: 114 İç Kapı No: 1, Keçiören / ANKARA 06010, Türkiye
bsdigitalapp@gmail.com
EzanQ is an independent app and is not the official app of the Presidency of Religious Affairs (Diyanet). “Diyanet method” names the calculation method.
