1. Summary
- There is no account, and you never sign in with Google or any other account. We never ask for a name, e-mail or password, and no personal profile is kept on a server.
- Your source preference, optional personal details and worship records are stored only on your phone; they are not sent to the ad system or to our server.
- The free version of the app shows ads through Google's AdMob advertising technology (Google Mobile Ads SDK). When ads are requested or shown, this SDK collects approximate location, app interactions, diagnostics and device identifiers (including the Advertising ID) and shares them with Google. Purposes: advertising, analytics (ad measurement), and fraud prevention, security and compliance. The app has no analytics or tracking tool of its own; only Google's ads SDK collects the advertising data above, and with Premium there are no ads and no such data. Details are in sections 3 and 7.
- Ads are requested in a non-personalised way; you are never asked your age and no age information is added to ad requests. No ads appear on verse, hadith and supplication reading pages, in Settings or in notifications. On Today, Worship and Calendar there can be a fixed ad strip at the top and a banner at the end of the content. No new ad is started or loaded while the adhan plays or in Worship mode, and no full-screen ad is started in the first 10 minutes after a prayer time begins. Banner ads may appear around prayer times outside those moments.
- Premium (Monthly Supporter / Lifetime Supporter) is sold through Google Play in Türkiye only. If you buy it, your purchase history (the purchase token) is processed only to verify your entitlement; it is not shared.
- Location permission is used only when you ask, once and in the foreground; raw coordinates are neither stored nor leave the device. There is no background location permission.
- Internet connections are encrypted in transit (HTTPS/TLS).
- Our server holds no account or profile of yours. If you bought Premium, you can save your purchase record to a file or have it deleted from within the app; you delete data on the device from within the app or by clearing the app's data (see sections 8 and 12).
- This website sets no cookies and loads no third-party services.
2. Who is responsible
The app is developed and published by, and the data controller is: Celaleddin Ünal and Burak Cem Yaman. The app and this website are published under the Ufkun Yolu brand. Ufkun Yolu is a brand name, not a separate company or legal entity.
Privacy questions and requests about your legal rights: destek@namazinikacirma.com
Legal bases: Premium purchase history is processed to enter into and perform the contract (KVKK Art. 5/2-c; GDPR Art. 6(1)(b)). Ad data in the European Economic Area, the United Kingdom and Switzerland relies on your consent (GDPR Art. 6(1)(a)); in other countries, the legal bases required by the law of the country you are in apply to the processing of ad data.
International transfers: Premium and (previously granted) access verification run on Supabase infrastructure in Ireland (EU), and the encryption keys used for purchase verification run on Google Cloud in Belgium (EU); ad data may be processed by Google outside Türkiye. We answer requests within 30 days at the latest. You keep the right to complain to the Turkish Personal Data Protection Board or to the data protection authority in your country.
3. Data collected and shared (Google Play declaration)
The table below corresponds one-to-one to our Data safety declaration on Google Play. "Collected" means the data leaves your phone; "shared" means the data is passed to Google. This data is encrypted in transit.
| Data type | When and how | Purpose | Collected / shared |
|---|---|---|---|
| Approximate location | When an ad is requested or shown, Google's ads SDK derives an approximate country- or city-level location from your IP address. GPS or precise location is never given to the ad system. | Analytics (ad measurement); advertising; fraud prevention, security and compliance | Collected and shared with Google; required in the free version |
| App interactions | The ads SDK records interactions such as app launches, ad views and taps on ads. What you read on which screen, your source preference and your worship data are not added to these records. | Analytics (ad measurement); advertising; fraud prevention, security and compliance | Collected and shared with Google; required in the free version |
| Diagnostics | The ads SDK sends performance, error and crash information about its own operation. | Analytics (ad measurement); advertising; fraud prevention, security and compliance | Collected and shared with Google; required in the free version |
| Device or other IDs | In the free version, the device's Advertising ID and Google's ad-measurement requests may be sent with an ad request; Google's ads technology may process device and app identifiers (which may include the Advertising ID). | Analytics (ad measurement); advertising; fraud prevention, security and compliance | Collected and shared with Google; required in the free version |
| Purchase history | Only if you buy Premium: the purchase token and product information issued by Google Play are sent to our server to verify your entitlement. | App functionality (Premium entitlement) | Collected, not shared; optional (only if you buy) |
The data in this table is not declared as ephemeral (processed only in memory and discarded). The app has no account creation and no sign-in with an external account. You can ask for your purchase history to be deleted from within the app (Settings → Support us → Purchase data → “Delete purchase data”) or by e-mail; all deletion options are in section 12.
Ad data is sent only in the free version and only when an ad is requested or shown (a request may return no ad, and full-screen ads and the rewarded video may be loaded in advance, before they are shown); purchase history is sent only if you buy Premium; with Premium no ad data is collected. Prayer-time and content packages are not downloaded from a server (see section 6).
4. Data stored on your device
The following is stored in the app's private storage on your phone so the app can work. None of it is sent to an ad network or to our server.
| Data | Purpose | How it is stored |
|---|---|---|
| Interface language | Showing the app in your language | On device |
| Selected country / province / district | Prayer times and approximate qibla for your place | On device; excluded from cloud backup and device-to-device transfer |
| Prayer-time and content source preference | Showing times and content according to Diyanet or the community method you chose | On device; excluded from backup and transfer. Not a declaration of membership |
| Notification preferences (types, times, muted days, sound) | Sending only the reminders you want, when you want them | On device; excluded from backup and transfer |
| Optional first name, last name, date of birth, gender | A warm greeting and, if you wish, days to your birthday | On device, encrypted with a device key (Android Keystore, AES-256-GCM); excluded from backup. Each field can be skipped and deleted later |
| Your worship goals and the days you tick | Optional personal tracking | On device, encrypted with a separate key; excluded from backup. Deletable in one step |
| Calendar reminders and optional notes | Reminding you on the chosen day and time | On device; the note appears only in your own notification and inside the app |
| Theme, appearance and widget settings | How the app looks | On device |
| Diagnostic status counters (last widget refresh state; number of prayer alerts that arrived late in the last 7 days and the starting day) | Showing the status code in Settings → About | On device only; contains no name, place, prayer time or other personal data, is not included in cloud backup, is not written to any log and never leaves the phone |
| Prayer-time and content packages | Offline use | On device, signature-verified cache |
| Adhan delivery log (record of the last 40 prayer-time alerts: prayer name, planned time, how many seconds early or late the alert was posted, trigger) | Showing you how early or late the adhan alert arrived relative to the prayer time | On device only; not included in cloud backup or device-to-device transfer, never sent anywhere, and removed together with the app's data |
| Ad-frequency counters | Keeping full-screen ads rare | On device; contain no content or identity data and never leave the phone |
| Rewarded-video record (view times of the last 24 hours (at most ten), end time and total of the ad-free period, time the Today-screen balloon was hidden) | Enforcing the limit of 10 uses per rolling 24 hours, the ad-free period of 2 hours per view (at most 8 hours) and the 7-day hiding of the balloon | On device only; carries no identity or content data, is not included in cloud backup and never leaves the phone |
| Ramadan marks (fast, tarawih) and the make-up (kaza) record (entered and completed make-up counts and their history) | Optional personal tracking | On device, encrypted with a separate key (Android Keystore, AES-256-GCM); not included in cloud backup or device-to-device transfer and never sent to a server. Deleted separately with “Delete Ramadan records” and “Delete make-up record” on the make-up record page in the Worship tab. You may export only a CSV summary of the counts to a location you choose; that file is outside the app's encryption; the app keeps no copy of it, does not back it up and sends it nowhere |
| Ramadan settings (Ramadan mode on/off, sahur reminder and its lead time, start-day adjustment, your answer to the Ramadan invitation) | Running Ramadan mode and the sahur reminder as you chose | On device only, not encrypted (they contain no fast, tarawih or make-up data); excluded from cloud backup and device-to-device transfer and never sent to a server. Changed in the Ramadan mode and sahur notification settings in Settings; deleted when the app data is cleared |
Uninstalling the app, or clearing its data in Android settings, removes all of this data from your device.
5. Location
- Location permission is requested through Android's own dialog only when you tap "Use my location". If you decline, you pick your province and district from a list; the app works the same way.
- When granted, location is read once, only while the app is open, and matched to a province/district on the phone. Optionally a more precise qibla direction is computed.
- Raw coordinates are never stored permanently, logged, or sent to a server or ad system. Only the selected province/district is kept. For this reason precise location is not listed as "collected" in our Google Play declaration.
- When an ad is requested or shown, Google's ads SDK derives an approximate location from your IP address (country or city level), which is visible in every internet connection. This is not GPS or permission-based location; the app never adds the device location to an ad request (see section 7).
- The app has no background location permission (
ACCESS_BACKGROUND_LOCATION); there is no travel or movement tracking. - The compass sensor for the qibla arrow is read only while the Today screen is visible; sensor data is not stored.
6. Internet use, encryption and package downloads
Calendar and date calculations happen entirely on the device. All of the app's internet connections are encrypted in transit (HTTPS/TLS); the app does not allow unencrypted HTTP connections. The internet is used only for:
- Serving ads (free version only; see section 7).
- Verifying a Premium entitlement (only if you purchased or were previously granted free access; see section 8).
Prayer-time and content packages are not downloaded from a server: packages ship inside the app and are refreshed with app updates; the app does not connect to our server for this. If server package downloads are added later, this policy and the Google Play Data safety declaration will be updated together before they are switched on.
7. Advertising (Google AdMob)
The free version of the app includes Google's advertising service Google AdMob (Google Mobile Ads SDK). The rules below apply to ads in the free version.
- Data collected and shared: when an ad is requested or shown, Google's SDK collects approximate location (from the IP address), app interactions (app launches, ad views and taps), diagnostics (SDK performance, error and crash information) and device identifiers (device and app identifiers, which may include the Advertising ID), together with technical information such as device model and operating system version, and passes them to Google. Because the app does not add a child or age-restricted treatment to ad requests, in the free version the device's Advertising ID and Google's ad-measurement requests may be sent with an ad request; with Premium no ad request is made and none of this is sent.
- Purposes: serving ads and capping their frequency (advertising); measuring and reporting ad impressions, clicks and performance (analytics); preventing invalid traffic and fraud, keeping services secure and meeting legal obligations (fraud prevention, security and compliance). Google processes this data under its own policies, including on servers outside Türkiye: Google Privacy Policy, How Google uses information from sites or apps that use its services.
- Ad requests: ads are requested as non-personalised, with the maximum ad content rating set to "PG". The app does not add a child or age-restricted treatment to ad requests; your age is not asked, not inferred and not added to requests. With non-personalised ads Google does not use the data for interest profiles or personal targeting; it may use it for frequency capping, measurement and fraud prevention.
- Your source preference, city, prayer times, qibla use, notification and worship data are never added to an ad request, keyword or targeting. Religious usage is not used as an ad segment. You are not asked your age for advertising, and your profile date of birth is not used for ads.
- Sensitive ad categories: alcohol, gambling/betting, dating and similar sensitive categories, and ads with religious content, are blocked in our ad network settings. This does not mean that no unsuitable ad can ever appear; if you see an unsuitable ad, you can report it to destek@namazinikacirma.com.
- Consent (EEA and UK): in regions that require consent, such as the European Economic Area, the United Kingdom and Switzerland, Google's consent form (User Messaging Platform) is shown; where consent is required, no ad is requested before you make a choice in the form, except in the one case described below. When you open or return to the app, Google refreshes your consent information. Before that refresh finishes, the app may already request ads if the information kept on your phone from earlier use allows it (you made a choice in the form before, or consent was not required where you were last time). If the refreshed information does not allow ads, all ad areas close and no ad loaded earlier is shown. The one exception: if you moved from a country where consent is not required to one where it is, non-personalised ads may be requested and shown until the refresh succeeds and the consent form is shown. You can change your choice in the app under Settings → Privacy → Check privacy options.
- You can reset or delete your Advertising ID in Android settings (Settings → Google → Ads; menu names vary by phone).
- Where and when no ad is ever shown: Ads never appear inside or between verses, hadith, prayers or guidance texts; reading pages are ad-free. No ads are shown on the Settings screen or in notifications. No new ad of any format, including banners, is started or loaded while the adhan plays or in Worship mode (also when Do Not Disturb is on); any banner already on screen is removed. A full-screen ad or rewarded video you were already watching when a prayer time begins is not interrupted by the app, so a full-screen ad that started just before a prayer time can still be on screen while the short adhan plays. Because the short adhan plays when a prayer time begins, banners are also not shown in the first 2 minutes after a prayer time begins.
- Ads around prayer times: There is no general ad-free window around prayer times; banner ads may appear then, except in the adhan and Worship-mode moments above. Full-screen ads (app-open and interstitial ads, including video) are never started in the first 10 minutes after a prayer time begins, nor while the adhan plays, in Worship mode or when Do Not Disturb is on.
- Entering from a notification or widget: when you open the app from a prayer-time (adhan) alert notification, no ads at all are shown in that session. When you open it from the ongoing prayer-times notification or from a home-screen widget, no full-screen ad is shown in that session; banners and the optional rewarded-video entry are offered as usual.
- Ad formats: The free version may show banner ads and full-screen ads; which of these formats is active at any time can change with the app version. Banners: on Today, Worship and Calendar there can be a fixed ad strip at the very top and a banner at the end of the content. There is no ad area in Settings or on reading pages. A top ad strip that was already shown and leaves the screen (for example when you switch to Settings or leave the app briefly) may be kept in the phone's memory; if you come back within 60 seconds, the app may show the same ad again without making a new request, and after 60 seconds this ad is not shown and is discarded. It is also dropped from memory when consent or privacy choices are opened or changed, when the device is low on memory, and when no ad may be shown (for example for Premium, previously granted access or the ad-free time earned with the rewarded video). This adds no new data category, no new recipient and no personalisation; the ad-free moments, such as during the adhan, in Worship mode and in the first 2 minutes after a prayer time begins, apply as before. An app-open ad may be shown when the app starts from scratch or comes to the front after at least 30 minutes in the background, only if an ad has already been loaded; it is not shown when you enter from a notification or a widget, nor on a return when the decision takes longer than a moment or you have already touched the screen, at most 2 times in 24 hours with at least 4 hours between them and at most once per session. An interstitial ad may be shown at natural transitions between screens, on every 2nd transition, at most 6 times in 24 hours and at most 2 times per session; it never interrupts a tab switch. App-open and interstitial ads together appear at most 8 times in 24 hours with at least 3 minutes between any two; no full-screen ad is shown until 24 hours have passed since first use and 2 sessions have been completed. Full-screen ads may be video and can be closed; none is forced by a timer. See also “Where and when no ad is ever shown”.
- Optional rewarded video: in Settings → Support us and in a small balloon below the prayer times on the Today screen you can start a short ad video, only by tapping it yourself; once it is completed, no ads at all are shown in the app for 2 hours. The hours add up, but the remaining ad-free time is capped at 8 hours (while at the cap no new video is offered). It can be used at most 10 times in any rolling 24 hours (after the tenth use it cannot be started again until 24 hours after the first), never opens by itself, the balloon can be hidden with × for 7 days, it is not offered to Premium users and cannot be started while the adhan plays, in Worship mode, on religious text pages or in the first 10 minutes after a prayer time begins. The rewarded video does not grant Premium. Its requests are the same as for the other ads: non-personalised, with a maximum rating of "PG" and no child or age-restricted treatment. The view times of the last 24 hours, the end time and total of the ad-free period and the time the balloon was hidden are kept only on your phone and are not sent to our server. These formats collect no data beyond what is described above.
- With Premium no ad requests are made, all ad placements disappear and the advertising data above is not collected.
- Premium status and ads: No ads are shown while your Premium status has not yet been confirmed by Google Play. If Google Play gives no definite answer, the app asks again after 30 seconds and after 2 minutes. If the app has already received a "not Premium" answer from Google Play, ads may stay visible for at most 10 seconds while that answer is refreshed when you return to the app; if you have Premium, ads disappear as soon as Google Play confirms it.
8. Premium purchases (Google Play)
Premium comes in two options: Monthly Supporter and Lifetime Supporter. It is sold through Google Play in Türkiye only; in other countries the app is used as the free, ad-supported version. If you do not buy, no purchase information is sent to our server and our server holds no purchase record of yours.
- Premium is sold through Google Play. Payment details are handled by Google Play; the app never sees card or payment data. See the Google Privacy Policy.
- Purchase history: to confirm that your purchase is valid, the purchase token and product information issued by Google Play are sent to our server and verified with Google Play. This data is used only to provide your Premium entitlement (app functionality); it is not used for advertising or analytics and is not shared with third parties. The token is stored encrypted and never written to logs.
- Retention: the purchase token is stored encrypted while your entitlement lasts and for at most 90 days after it ends. Access logs for the verification flow are kept in truncated form for at most 14 days; Google Play notification messages for at most 30 days. If a Google Play notification is moved to the Google Cloud Pub/Sub dead-letter queue after 20 failed delivery attempts, the raw notification message (which may contain the purchase token) is kept there for at most 7 days and then deleted. For a refunded or revoked lifetime purchase, a minimal encrypted token-derived record is kept indefinitely to prevent the same token from being reused.
- Refunds and cancellations are handled through Google Play. You can save your purchase record to a file, or have it deleted from our server, in the app under Settings → Support us → Purchase data (“Delete purchase data”); your Google Play purchase and Premium right stay with Google. You can also write to destek@namazinikacirma.com.
- Previously granted access (reviewer and complimentary access): from app version vc12 the app has no access-code entry and no new codes are issued. Access that was granted earlier keeps working (status, retry and removal), and its credential stays on the device as before. This credential is sent to our server only to verify that access and is stored there as a digest (SHA-256), not as plain text; verification issues a short-lived session. This access is not a purchase record, is not combined with paid purchases, and is not linked to your name, location or a device fingerprint. When access is removed, the code and session records are deleted; only a minimal removal record (the code digest and the access ID) is kept so that the same access cannot be reopened. If you have no previously granted access, no such data reaches our server.
- Premium only removes ads and unlocks two special icon sets (Palestine and East Turkistan); calendar, prayer times, qibla, religious content and notifications stay free.
9. Notifications and widgets
- All notifications are scheduled on your device; no push notifications are sent from a server.
- Notification permission is requested only when you tap a button such as "Turn on notifications", never on first launch.
- If you keep prayer-time notifications on, an ongoing notification showing the day's prayer times and the countdown to the next one is on by default; you can turn it off in Settings. It is computed on your phone and no data leaves the device.
- Verse, hadith and prayer texts and their sources are not written into notifications; the lock screen shows only a neutral reminder. You read the full text inside the app.
- Home-screen widgets make no network calls, use no location and carry no ads. Prayer-time details can be hidden in widget settings.
- Prayer-time alerts are scheduled through the system's alarm-clock mechanism so that they arrive on time; because of this, an alarm icon may appear in your phone's status bar and the "next alarm" time on the lock screen. The timing of other notifications was also strengthened to work while the phone sleeps. All of this is scheduled on the device; no data leaves it.
- If notifications are delayed, the app may show a battery-restriction or auto-start hint in its settings. For this it reads, on the device only, the app's own battery-restriction state and the phone maker's name (Android's public manufacturer/brand field); nothing else about you or your device's identity is read, and nothing is stored or sent. You turn on the relevant system setting yourself; the app does not change it on its own.
- The status code in Settings → About (e.g. its "BG", "WID" and "MISS" fields) shows, in short fixed words, the battery-restriction state, the last widget refresh state and the number of prayer alerts that arrived late in the last 7 days. The code is only shown on screen: it contains no name, place, prayer time or other personal data, is not written to any log and is not sent anywhere; the counter and widget state are kept in app-specific files on the device only. If you wish you can long-press to copy the code and send it to us for support; that is entirely your choice.
10. Android permissions
| Permission | Why |
|---|---|
| Internet | Ads in the free version; Premium and (previously granted) access verification |
| Notifications | Prayer, religious-day and content reminders (when you turn them on) |
| Exact alarms | So that prayer-time alerts arrive exactly on time. On Android 13 and newer it is granted at installation and not asked separately; without it, approximate scheduling is used |
| Location (approximate / precise) | Only when you tap "Use my location", once, to find your district and for qibla |
| Do Not Disturb access | Only if you set up Worship mode, to silence the phone for the period you choose |
| Run at start-up | Re-creating scheduled notifications after a reboot |
| Google Play billing | Buying and restoring Premium |
The Google Mobile Ads SDK also brings the Advertising ID permission (AD_ID) and the permission to read basic phone state such as network type (READ_BASIC_PHONE_STATE; it gives no access to your phone number or calls). The Android and Google libraries in use also add the network state (ACCESS_NETWORK_STATE) and keep-awake (WAKE_LOCK) permissions; these read no personal data. The app manifest also lists the foreground service permission (FOREGROUND_SERVICE); this version starts no long-running service with it, and it reads no personal data. No contacts, camera, microphone, file or background-location permission is requested.
11. Age limit, children and countries
The app is published on Google Play for users aged 13 and over and may be offered in all countries (Premium is sold in Türkiye only). The app does not target children under 13. You are not asked your age for advertising, and your profile date of birth is not used for ads. No child or age-restricted treatment is added to ad requests; ads are requested non-personalised and rated "PG" at most.
12. Your rights and deleting data
- Data on your device: you view, edit and delete your personal details and worship records inside the app: Settings → Personal details and Worship → My worship goals; you delete Ramadan marks and the make-up record with “Delete Ramadan records” and “Delete make-up record” on the make-up record page in the Worship tab.
- Uninstalling the app, or clearing its data in Android settings (Settings → Apps → Namazını Kaçırma! → Storage → Clear data; menu names vary by phone), removes all app data from the device.
- Google's advertising data: you can reset or delete your Advertising ID in Android settings. In the EEA, the UK and Switzerland you can change your ad consent under Settings → Privacy → Check privacy options. You exercise your rights over data Google processes with the tools described in the Google Privacy Policy. Premium stops the collection of advertising data entirely.
- Server side: because the app has no account, our server holds no account or profile of yours. If you bought Premium, you can save your purchase record to a file under Settings → Support us → Purchase data, or send a deletion request with “Delete purchase data”. The request is verified against the current Google Play purchase on this device. The raw purchase token is deleted from online systems within 24 hours and from backups within 35 days at the latest; the technical trace that could be matched to the token is removed after 90 days. The raw copy of a notification message in the dead-letter queue (if any; see section 8) is deleted automatically within 7 days at the latest, independently of any deletion request. For refunded or revoked one-time purchases, the minimal encrypted record described in section 8 is kept. After deletion the app does not recreate the record by itself; to link ad-free use again, you tap “Restore purchases”. Your Google Play purchase and right stay with Google. You can also send your deletion request by e-mail to destek@namazinikacirma.com.
- For questions and requests about your rights under Türkiye's Personal Data Protection Law No. 6698 (KVKK), the EU General Data Protection Regulation (GDPR) or the law of your country, write to destek@namazinikacirma.com; we will review your request and reply.
13. This website
namazinikacirma.com sets no cookies, runs no analysis or monitoring tools and loads no third-party fonts or scripts. Our hosting provider (Vercel) may keep standard server access logs to serve the pages; we do not use them for visitor analysis. If you close the “Stand against oppression!” box in the bottom corner, that choice is stored only in your browser's local storage (localStorage); it is not sent to us or anywhere else, and clearing your browser data removes it.
If you e-mail us (for example for support), we use your e-mail address and message only to reply to you. People who wrote with the “Notify me at launch” button before version 1.8 are written to only once, to say the app has been released. We do not add your address to a marketing list or share it with third parties. This correspondence is not app data; if you want our correspondence deleted, simply write to the same address.
14. Changes
When this policy changes, the new version is published on this page with its effective date. For significant changes to how the app processes data, we also inform you inside the app. When the way ads, Premium or server package downloads process data changes, this policy and the Google Play Data safety declaration are updated together.
- Version 1.15 (22 November 2026): Takes effect with app version 17 (1.0.17). With this version, when ads are requested changed, and it is now described in more detail; no new data category, no new recipient and no personalisation were added, and ads are still requested non-personalised. The statement "the consent form is shown before any ad loads" is replaced by this: where consent is required, no ad is requested before you make a choice in the form, except in one case. When you open or return to the app, Google refreshes your consent information; before that refresh finishes, the app may already request ads if the information kept on your phone from earlier use allows it. If the refreshed information does not allow ads, all ad areas close and no ad loaded earlier is shown. The one exception: if you moved from a country where consent is not required to one where it is, non-personalised ads may be requested and shown until the refresh succeeds and the consent form is shown. The moment ad data goes to Google is now written as "when an ad is requested or shown" instead of "when an ad is shown" (a request may return no ad, and full-screen ads and the rewarded video may be loaded in advance, before they are shown). Also, a top ad strip that was already shown and leaves the screen (for example when you switch to Settings or leave the app briefly) may be kept in the phone's memory; if you come back within 60 seconds, the app may show the same ad again without making a new request, and after 60 seconds this ad is not shown and is discarded. The promises of no ads during the adhan, in Worship mode, in the first 2 minutes after a prayer time begins, in Settings and for supporters did not change.
- Version 1.14 (22 November 2026): Takes effect with app version 16 (1.0.16). Ad requests changed: the app no longer sends a child or age-restricted treatment (your age is still never asked and no age information is added to requests); ads are still requested non-personalised, and the maximum ad content rating is now "PG" instead of "G". As a result, in the free version the Advertising ID and Google's ad-measurement requests may be sent with an ad request (with Premium there are no ads and no ad data). Alcohol, gambling/betting, dating and similar sensitive categories, and ads with religious content, are blocked in our ad network settings. A fixed ad strip was added at the top of Today, Worship and Calendar (none in Settings or on reading pages). Interstitial ads may now appear on every 2nd natural transition, at most 6 times in 24 hours and 2 per session; app-open and interstitial ads together at most 8 times in 24 hours (before: every 3rd transition, at most 5, and 7 in total). In a session opened from the ongoing prayer-times notification or a widget no full-screen ad is shown but banners and the rewarded video are offered; a session opened from a prayer-time (adhan) alert notification has no ads. No new ad is started while the adhan plays or in the first minutes after a prayer time begins; a full-screen ad or rewarded video you are already watching is not interrupted by the app, so a full-screen ad that started just before a prayer time can still be on screen while the short adhan plays. No ads are shown while your Premium status is still unknown; if Google Play gives no definite answer, the app asks again after 30 seconds and after 2 minutes. When you return to the app, an app-open ad is not shown if the decision takes longer than a moment or you have already touched the screen. The on-device "adhan delivery log" was added: the record of the last 40 prayer-time alerts stays on your phone only, is not included in backups or device transfers, is never sent anywhere and is removed with the app's data. How location, personal details and purchases are processed did not change.
- Version 1.13 (19 November 2026): Takes effect with app version vc15. The optional rewarded video changed: each view gives 2 ad-free hours; hours add up, but the remaining ad-free time is capped at 8 hours, and the video can be watched at most 10 times in any rolling 24 hours (before: 3 hours per view and at most two views in 24 hours). The on-device rewarded-video record now holds the view times of the last 24 hours (at most ten) and the ad-free total after each view; it stays on your phone and is never sent. Battery-restriction and auto-start hints were added: to show the hint the app reads, on the device only, its own battery-restriction state and the phone maker's general name (Android's public manufacturer/brand field); this information never leaves the device. Three fields were added to the status code in Settings → About (battery-restriction state, widget refresh state and the number of prayer alerts that arrived late in the last 7 days); they are only shown on screen, not written to any log and not sent over the network; copying the code and sending it to us is entirely your choice. Prayer-time alerts are now scheduled through the system's alarm-clock mechanism, so an alarm icon and the "next alarm" time may show on the phone. The on-device scheduling of other notifications was also strengthened. No other data processing changed; the Google Play data safety declaration is not affected.
- Version 1.12 (17 November 2026): Takes effect with app version vc13. The optional rewarded video can now be watched at most twice in any rolling 24 hours (the 3 ad-free hours are unchanged); besides Settings → Support us, a small balloon below the prayer times on the Today screen offers it and can be hidden with × for 7 days (it is not shown to Premium users, while the adhan plays, in Worship mode or while reading religious texts). The on-device rewarded-video record now holds the last two view times, the end time of the ad-free period and the time the balloon was hidden (the old "tip" flag is gone); it stays on your phone and is never sent. For users who keep prayer-time notifications on, an ongoing notification showing the day's prayer times and the countdown to the next one is on by default and can be turned off in Settings; it is computed on the device. No other data processing changed; the Google Play data safety declaration is not affected.
- Version 1.11 (15 November 2026): Takes effect with app version vc12. The "Access code" entry was removed from the app and no new access codes are issued. Access granted earlier keeps working (status, retry, removal) and its credential stays on the device as before; the related wording (sections 8 and 10, international transfers) was corrected accordingly. No other way the app processes data changed; the Google Play Data safety declaration is not affected.
- Version 1.10 (12 November 2026): The optional rewarded video is described: 3 hours of ad-free use in return for a short video that only you start, at most once every 24 hours; its requests are non-personalised and in the all-ages mode, and the end time is kept only on the phone. Rows for this rewarded-video record and for the Ramadan marks and make-up record were added to the "Data stored on your device" table. The 7-day retention of notifications in the Google Pub/Sub dead-letter queue was written into the retention and deletion sections. The advertising rules were aligned with the current design: no ads while the adhan plays (for banners, including the first 2 minutes after a prayer time begins), in Worship mode and on religious text pages; none at all in Settings and notifications; no full-screen ad in the first 10 minutes after a prayer time begins; banner ads may appear around prayer times; the app-open and interstitial limits and the conditions of the rewarded video were written down, and it was stated that the app has no analytics tool of its own. The data collected and its purposes are unchanged; the Google Play Data safety declaration is re-checked against this version on the publishing day.
- Version 1.9 (11 November 2026): The ad rules were updated: the general ad-free window around prayer times was removed; ads remain excluded while the adhan plays, in Worship mode and on religious text pages, and full-screen ads never appear in the first 10 minutes after a prayer time begins. The ad formats that may be used (banner, app-open and interstitial, full-screen video, optional rewarded) are described. The data collected, its purposes and the Google Play Data safety declaration are unchanged.
- Version 1.8 (11 November 2026): The policy is written for the first public release (1.0.0); the closed-test wording was removed. It now states that ads are shown in the free version, that Premium (Monthly Supporter / Lifetime Supporter) is sold through Google Play in Türkiye only, and that purchases are verified on our server. The data involved in the reviewer/complimentary access code was added. In-app purchase-data export and deletion requests (Settings → Support us → Purchase data) and the deletion periods (24 hours, 35 days in backups, 90 days) are described; the “no server-side deletion-request flow” wording was removed. The full adhan playback service and the media foreground service are not in this version, so they were removed from the permissions table; the general foreground service permission that stays in the manifest is explained. Server package downloads are not in this version, so the quota ID, Play Integrity and 32-day retention descriptions were removed.
- Version 1.7 (9 November 2026): added a data table that matches the Google Play Data safety declaration one-to-one (approximate location, app interactions, diagnostics, device IDs; purchase history). The data collected by the ads SDK and its purposes (advertising, analytics/ad measurement, fraud prevention, security and compliance) are now described in the present tense; IP-derived approximate location, diagnostics and encryption in transit were added. The all-ages ad mode and the EEA/UK consent form are explained. The closed-test status (ads, Premium sales and server package downloads switched off) is stated. The quota ID, Play Integrity token and 32-day retention for server package downloads are explained. Scope updated to "all countries, ages 13 and over". The deletion section was rewritten to state clearly that there is no server-side account or deletion-request flow.
- Version 1.6 (8 October 2026): previous version.