Privacy
Updated: 4 November 2026. NurVakti is operated by Mehmet Kaan Ulu. Support and data requests: support.NurVakti@gmail.com.
Information on your device
You do not need an account. Worship records, notes, favorites and reading preferences stay on your device by default; they are not sent to the ad system or to RevenueCat. You can export and delete them from the Privacy screen. Records stay on the device until you delete them or remove the app’s data; operating-system backups follow your own settings.
Your privacy choices
Measurement, the installation record and announcements are optional and do not start without your permission. Prayer times, Quran and your chosen reminders still work if you decline. Ads and purchases do not depend on these choices. Change your choices anytime in Settings → Privacy.
This screen does not grant location or operating-system notification permission. Manual city selection remains available. Your own city, language and theme choices are unaffected.
Notifications are delivered through Apple or Google services. Withdrawal stops optional processing on your device immediately; cleanup of related server records is retried when connected. Required purchase records and your content are not deleted.
Acceptance and refusal are remembered. Normal launches do not ask again for the same account and purposes. An account or purpose change may require a new decision. Collection and queued uploads do not start without the relevant permission.
Support number
The app creates a random NV number. Even if you decline measurement, this number is stored at RevenueCat with your random app account so that we can find your support request. It contains only this number, with no usage, location or worship information. You can ask for it to be deleted through the support address.
Location and external services
Location is taken only with your permission and only during the action that needs it; you can use a manual city, and no background location is collected. Prayer times are calculated on your device.
Time zone: When you use your current location, your coordinates are sent over HTTPS to our own server to find the time zone. The server only works out the time zone and replies; it does not write the coordinates to a database. If the server cannot be reached, the time zone is estimated on your device.
Routes: When a route to a mosque is calculated, your current location and the mosque’s location are sent to our own server and from there to the route provider openrouteservice (HeiGIT). The result is kept in the server’s temporary memory for 5 minutes so the same route can be reused; it is not written to a database.
Nearby mosques: The search point is sent to our own server, which rounds it to about 100 meters and queries OpenStreetMap (Overpass) data. If the server cannot be reached, the search point is sent directly to Overpass servers.
When you open external directions, the map service you choose receives this information. Our server, our hosting infrastructure and audio listening/download providers can see connection details such as your IP address in network requests; our server uses them to limit abuse.
Live Activity (iPhone)
When you start a Live Activity on iPhone yourself, the session token issued by Apple and the activity’s content are sent to our own server so the screen can update when prayer times change. The content consists of prayer names and times, time zone, the prayer-time source label, theme and display preferences, language and screen texts and, if shown, the nearby mosque’s name and walking time; it contains no coordinates. Updates reach your device through Apple Push Notification service (APNs). A session lasts at most 8 hours. When it ends or you stop it, the token and content are deleted; only a one-way token digest that prevents the session from reopening is kept for 8 more hours. The live notification on Android runs on the device and does not use this service.
App updates
While on Wi-Fi, the app checks our own server for updates that do not need a new store version. This request sends the platform, app runtime version, update channel, the ID of the installed update and a random update ID unique to your installation (EAS-Client-ID). This ID is used to roll out updates in stages and to select test devices; it does not depend on your measurement choice. Your name, location and worship content are not sent. The ID is normally not recorded; only during limited test recording periods are the ID, platform, runtime version and request time written to a file on the server.
Problem reports and suggestions
When you send the app’s problem report or mosque suggestion form, the category or suggestion type, record or mosque ID, your description and any source link are sent to our own server. The app does not add an account, location or device ID to these submissions. Submissions are kept as unchangeable records for review and audit, with no automatic deletion period. For this reason, do not write your name, exact location, access keys, card details or personal worship history in these forms.
If you email us, your address and message are used to reply and are processed by Google’s email service.
Ads
Everyone who does not have NurVakti Pro sees non-personalized ads. Ads are part of the free version; there is no separate ad permission, and ads do not depend on your measurement choice. The Apple ATT permission is not requested, and there is no cross-app tracking.
Google AdMob is the primary ad provider and Unity LevelPlay / ironSource is the backup. The app does not send precise location, verse notes or worship history to the ad system. These SDKs may process IP address (approximate region), device identifiers, ad interactions and diagnostic/performance information to show and measure ads. Non-personalized ads do not mean that no data is processed.
In regions where Google requires it, Google shows its own choice form (Google UMP); this form affects Google ads only. Pro is available for ad-free use; verified Pro users do not see ads.
Purchases
Apple and Google handle payments in their own stores; NurVakti does not receive your card details. RevenueCat processes a random app ID and store purchase/validity information for entitlement checks, restoring purchases and subscription status. Worship history is not added to purchase information. Deleting device data does not cancel a store subscription; subscriptions are managed from your store account.
Optional diagnostics
Measurement is off by default and starts only with explicit consent. NurVakti uses a random measurement ID for analytics and troubleshooting; if you join referrals, it may be linked to your verified purchase account. Our referral service and RevenueCat process the inviter link, purchases, cancellations, refunds and Pro entitlements to operate rewards and prevent abuse. Inviters do not see names or payment details. Entitlement and security records are retained as needed; hashes of revoked access are kept to prevent reuse. Data requests: support.NurVakti@gmail.com.
Only foreground time and notification scheduled, received, opened or error events are sent. No content, worship history or location is sent. No account is required. Device platform (iOS/Android), app and build version, and first and latest foreground visits are also sent.
Events are kept for 30 days. Turning this off stops collection and requests deletion; offline requests are retried.
Scheduling is not proof of delivery. Not all background deliveries can be measured. Past usage and unsent records are not added to reports.
Installation and activity record
Help improve NurVakti by sending device type, version, app visits, active time and notification diagnostics to our server under a random ID. Your platform, app version and last open time are sent to our service. Your name, location and worship content are not sent. If you arrived through an ad link, only the source and campaign labels in that link are recorded; no advertising ID (IDFA/AAID) is used and there is no cross-app tracking. The record is kept until you turn this permission off or delete your data. Turning this off stops sending data and requests deletion when connected. If you have an existing RevenueCat purchase account, these records may be linked to it. The usage goals you choose at first launch (e.g. Quran, dhikr) are also sent with this permission. All NurVakti features work without this permission.
Invite & earn
Joining creates a private purchase identity on this device. Your invitation code is public; your recovery key is private.
Each friend must keep their first paid purchase for 30 days without cancellation or refund. This applies to monthly, yearly and lifetime plans. Below five valid contributions, the temporary reward is removed. After five contributions complete 30 days, your reward becomes permanent.
Trials, free offers, sandbox purchases and family sharing do not count. Store refund rights are unchanged. Joining is optional; the free app remains available.
Your recovery key gives full access to your invitation identity. Keep it in a private password manager. Never send it to friends, administrators or support.
NurVakti announcements
Optional notifications about new features and app news. Your notification address, language, time zone, sound and quiet-hour preferences are stored securely and removed after 90 days without renewal. Turning this off deletes the registration when connected. Prayer reminders work separately.
Retention and requests
Retention of records held by providers, along with security and legal obligations, is subject to each provider’s policy; deleting data on your device does not automatically delete those records. You can send access, correction or deletion requests to the support address. Do not send unnecessary location or worship records. Service providers may process data on systems outside your country.
This website
This site uses no cookies, analytics, ads or forms. The language you choose is stored only in your browser; when the language is chosen automatically, only your browser’s language setting is read and your location is not taken. Share links may contain a verse reference, a public OSM ID or a public invitation code; they do not contain the secret recovery key. GitHub Pages may process technical access information.