SECDE VAKTİ · EMRE ŞAHİN
Privacy Policy
Last updated: September 24, 2026
1. Scope and controller
This policy covers the Secde Vakti iOS app (App Store), Android app (Google Play), their Apple Watch and Wear OS companions, and these support pages, provided by Emre Şahin. Contact: info@emresahin.app. Data flows depend on the platform, features and app version you use; platform-specific differences are marked “on iOS” and “on Android” in the relevant section. Worship records may reveal religious beliefs; consider this when sharing.
2. Personal records, cloud sync and backups
Prayer and missed-prayer records, fasting, dhikr, Khatm/reading progress, bookmarks, tasks, quiz achievements and preferences are stored on the device. On iOS, supported records sync through your own Apple account’s iCloud key-value storage when available. On Android, supported records are backed up to a private Firestore document linked to your Firebase user ID and readable only by that ID; depending on your device settings, Android Auto Backup may copy app settings to your Google account’s device backup. Delivery depends on device settings, connectivity and Apple/Google services; a prepared backup does not prove delivery to another device. Widgets, Apple Watch and Wear OS use copies of relevant records; the Wear OS app receives copies of your prayer times from the phone and sends watch dhikr counts back through Google’s Wearable Data Layer. Exported backup files may contain personal data; you choose where to store and share them.
3. Location, maps and content
Location permission supports place detection, prayer-time selection, Qibla calculations and nearby mosques. You can choose the prayer-time location manually. Qibla calculations run on the device; selected places/coordinates may be saved locally. On iOS, Apple geocoding and MapKit search process location or search-region information. On Android, place detection uses Android/Google location and geocoding services; the nearby-mosques search sends the search region to public OpenStreetMap Overpass servers (such as overpass-api.de and maps.mail.ru), and the map is displayed with Google Maps. Opening directions in another map app sends a request to that provider. Prayer data comes from ezanvakti.emushaf.net; Quran content/audio from Quran.com and associated content/audio servers; calendar updates from Diyanet sources. These services may receive IP addresses and request details. Not every feature works offline.
4. Firebase identity, groups and quiz
Firebase Authentication can create an app identity without email/password entry; this is not the same as unlinked data. Firebase/Google processes user IDs, chosen names/avatars, group memberships and shared records, quiz answers, scores and monthly/all-time rankings. Your name, avatar and ranking results may be visible to other participants. Group sharing varies between Full Details, Percentage Only, Completed Days Only and Hidden; Hidden does not hide membership or your profile. Changes and cleanup must reach the server; previously viewed or copied content cannot be recalled. Account recovery uses a random key and, on the server, a hash of that key linked to your user ID. On iOS the key is kept in iCloud Keychain; on Android it is kept in the app’s private storage on the device and, depending on your device settings, may be copied by Android Auto Backup to your Google account’s device backup. We do not receive your Apple or Google account password.
5. Purchases, ads and technical data
Apple processes payments on iOS and Google Play on Android; we do not receive card details. On iOS, StoreKit, server verification and RevenueCat, and on Android, Google Play Billing, process subscription/purchase status, product/transaction IDs and technical app identifiers. RevenueCat is not used on Android. AdMob ads may appear in the free version. Premium removes ads but does not automatically disable other necessary data flows. Google UMP manages advertising choices; on iOS, ATT permission may be requested separately for tracking, and on Android, AdMob may use the Android advertising ID according to your device settings and consent choices. Advertising services may process identifiers, IP addresses, device details and ad interactions according to permissions and choices. Firebase Analytics collects app/feature usage, purchase-flow and notification interactions; in the iOS app, Crashlytics collects crash and diagnostic data. App Check helps verify app requests, using App Attest on iOS and Google Play Integrity on Android. On Android, in-app update and review prompts are provided by Google Play. Technical identifiers may be included; we do not describe all these records as anonymous.
6. Purposes, providers and retention
Processing supports requested features, synchronization, purchase verification, service analysis and abuse prevention. Depending on applicable law, grounds may include service performance, legal obligations, necessary and proportionate security/operational interests, or consent where required. This policy is not itself a consent request. Apple, Google/Firebase/Google Play, RevenueCat, OpenStreetMap Overpass servers and content providers may process data outside your country, subject to applicable transfer requirements and provider agreements. Active account data is retained as needed for the feature; records on the device, in iCloud and in Android backups may remain until cleared. Provider logs and backups follow their retention periods. Minimum security or legally required records may remain after deletion; we do not promise immediate removal of every copy.
7. Choices, rights and deletion
Manage location, notifications and tracking/advertising-ID settings in your device settings (iOS Settings or Android Settings), and advertising choices through the app’s privacy options where available. Review group sharing and backup status in the app. Delete Account in app Settings initiates removal of linked server data and of personal device records and cloud backups (iCloud on iOS, the Firestore backup on Android). Offline devices may receive the change later. Deleting groups you created may affect other members. Retry or contact support if deletion reports an error. A minimal identity/deletion marker may remain to prevent a deleted account from being recreated through old credentials. Uninstalling the app does not delete cloud data; deleting an account does not cancel Apple or Google Play subscriptions, so manage them in the store where you subscribed. Where applicable, contact us to request access, correction, erasure, restriction, objection, portability or withdrawal of consent; you may also complain to the competent authority. Proportionate identity verification may be needed.
8. Children, support website and updates
Parents should supervise children’s profile/group sharing and purchases. Do not publish children’s identifying or contact details. Contact us about a child’s data for review or deletion. Information you email to support is used to address your request; do not send passwords or payment-card details. Netlify, the website host, may process IP/connection and security logs. Some marketing pages load Google Fonts; language preferences may be saved in your browser. We update this policy and date as data practices change, with additional notice or permission where required.
