Zikirmatik

1. Data We Collect

• Your dhikr data: your dhikr list, goals, counts and statistics. These are stored on your device and leave it only through the features you turn on yourself (iCloud sync, Dhikr Brotherhood, data transfer).
• Device and usage data: device model, iOS version, app version, language and region and similar anonymous technical data, plus a small number of app events.
• Advertising identifiers: IDFA / IDFV. Access is governed by your choice under Apple's App Tracking Transparency (ATT).
• Approximate location: the country/region the advertising and consent infrastructure infers from your IP address, used only for ad delivery and consent management. The app requests no location permission.
• Crash data: stack traces plus device/iOS/app version collected by Firebase Crashlytics.
• Purchase data: the Pro subscription is processed entirely through Apple App Store; we do not see or store your payment information.
• Advertising partners: AdMob and its mediation networks — Meta Audience Network, Vungle (Liftoff), Pangle (ByteDance) and InMobi — may process device/advertising identifier data for ad selection and measurement under their own privacy policies.

2. Device Permissions

• Tracking permission (NSUserTrackingUsageDescription / ATT): access to your advertising identifier for more relevant ads; granting it is entirely up to you. Pro users are not asked.
• Notifications: optional permission for announcements and, if you joined, shared dhikr events.
• Camera (NSCameraUsageDescription): used only on the "Transfer Data" screen to scan the QR code shown on another device. The camera image is never recorded and never leaves your device.
• Add to Photos (NSPhotoLibraryAddUsageDescription): requested only when you choose to save a share card to Photos. The app never reads your photos.

The app does not access location, microphone, contacts, calendar or health (HealthKit) data. You can revoke any permission at any time via iOS Settings.

3. Local Storage

Your dhikrs, counts, goals, statistics and app preferences are stored in a local database on your device. A small summary needed by the widgets and the Apple Watch app is kept in a shared area on the same device (an App Group). Deleting the app removes this data from the device.

4. iCloud Sync (Optional)

iCloud sync is off by default. Unless you turn it on during onboarding or in Settings, no iCloud container is created and nothing is sent to the cloud. When you enable it, your dhikrs and counts are kept in the private iCloud database of your own Apple Account so they stay in step across your devices; that data is held by Apple and Codeida cannot access it. Turning sync off only stops syncing — it touches neither the copy on your device nor the one in the cloud. You can manage or delete your iCloud data under iOS Settings > [your name] > iCloud.

5. Dhikr Brotherhood / Shared Dhikrs (Optional)

Dhikr Brotherhood is an optional feature that shows the combined total of everyone contributing to a shared dhikr, and it starts only when you press "Join" on the consent screen. Until you consent, not a single request is sent to our server for it.

Identity: joining creates no account. An anonymous installation identity is created for your device and proven with Apple's App Attest and short-lived access tokens; those values are kept in your device's Keychain. This identity is not the advertising identifier (IDFA) and is never given to any advertising or analytics SDK.

What is sent: only what is needed to count your contribution — which shared dhikr you contributed to and how much (a dhikr code and a number), the local day the contribution belongs to and your time zone, the first and last tap time of that batch, its source (app, widget or manual entry), the app version and the version of the consent text. Counts are written to your device first and sent in batches at natural pauses; the names of your dhikrs, your notes, your personal list and your statistics are never sent.

Deletion: Settings > Brotherhood > "Delete my Brotherhood data" removes your record, and the identity and queue on your device are cleared too. Your past contributions remain anonymous in the shared totals. Your personal counters and dhikr history are unaffected.

6. Transfer Data (QR and File)

There are two ways to move your data to another device, and both run only when you start them:

• Transfer by QR: your data is encrypted on your device and the encrypted package is placed on our server briefly. The decryption key exists only in the QR code on screen and never reaches the server (end-to-end). The package is deleted on the first successful download, or within 30 minutes at the latest.
• Transfer by file: your data is exported as an encrypted backup file, saved to the location you choose and never uploaded to Codeida servers.

7. Notifications

Notifications are delivered through Firebase Cloud Messaging (FCM) topic subscriptions: a "general" topic for announcements and, if you joined Brotherhood and opted in separately, a topic for shared dhikr events. Your device notification token is never sent to or stored on our server. Shared dhikr notifications are off by default, and leaving Brotherhood unsubscribes you. You can switch both off under Settings > Notifications and revoke the permission in iOS Settings.

8. Advertising & Consent Management

Ads are served through the Google Mobile Ads SDK (AdMob) (banner, MREC, interstitial, app-open and rewarded ads). A rewarded ad is shown only when you choose to watch one to unlock the weekly theme. Whether personalized advertising is used depends on your choices in the Google User Messaging Platform (UMP) consent dialog and the iOS ATT prompt: if GDPR applies to you, personalization requires consent; otherwise your ATT choice decides. Ads are still shown if you decline; without personalization consent, requests are sent as non-personalized (npa=1).

The following mediation adapters provide access to additional ad networks:

• Meta Audience Network — Privacy Policy
• Vungle (Liftoff) — Privacy Policy
• Pangle (ByteDance) — Privacy Policy
• InMobi — Privacy Policy

Your ATT and UMP choices are forwarded to each network individually and re-applied whenever your preference changes. Ad measurement uses Apple's SKAdNetwork framework, which attributes installs without identifying you. Users with a Pro subscription see no ads at all. None of your dhikr data is ever passed to advertising.

9. Analytics & Crash Reporting

Firebase Analytics collects anonymous usage statistics and Firebase Crashlytics collects crash and error records. Event parameters consist only of codes and numbers: the name, transliteration or meaning of a dhikr, or any text you typed, is never sent. The Brotherhood identity, its tokens and keys are likewise never written to analytics or crash records. Google's Consent Mode signals start as denied in the app and are updated only according to your consent and ATT decision.

10. In-App Purchases (Pro)

Pro, which removes ads and unlocks extra features, is sold as a monthly or yearly subscription through Apple StoreKit 2. The one-time "Remove Ads" purchase from the app's previous version is recognised and remains valid. Payment information is managed by Apple; our app never sees your card details. Manage subscriptions under Settings > Apple Account > Subscriptions.

11. Widgets & Apple Watch

The Home Screen widgets and the Apple Watch app (with its complications) show your latest dhikr and count. They read your data only through the on-device App Group; they make no network connections of their own and send nothing to external servers.

12. Sharing & Review

If you choose to share a dhikr card, the card is produced entirely on your device and handed through the iOS share sheet to only the app you pick; you can also save it to Photos. The in-app rating prompt uses Apple's StoreKit review API, and its counters stay on your device.

13. Children's Privacy

The app is not intended for users under 13. We do not knowingly collect personal data from children under 13.

14. Data Retention & Security

You have no account on our servers; they hold only the anonymous Brotherhood installation record and contribution counts if you joined, plus the encrypted package that rests there briefly during a data transfer. iCloud data follows Apple's terms, and analytics, crash and advertising data follow the retention policies of Google/Firebase and the respective ad networks. All network traffic is encrypted in transit using HTTPS.

15. Your Rights

You may have rights to access, correct, delete or object to the processing of your data under GDPR, CCPA, KVKK and similar regulations. You can delete your Brotherhood record from inside the app, manage iCloud data under Settings > [your name] > iCloud, tracking under Settings > Privacy & Security > Tracking and notifications under Settings > Notifications.

16. Contact

For privacy questions: [email protected].

1. İzinler ve Topladığımız Veriler

• INTERNET / ACCESS_NETWORK_STATE: reklam yüklemek, isteğe bağlı özellikleri (Kardeşlik, veri taşıma) çalıştırmak ve bağlantı durumunu izlemek için.
• POST_NOTIFICATIONS: Android 13+ üzerinde duyuru ve (katıldıysanız) ortak zikir bildirimlerini gösterebilmek için.
• VIBRATE: sayaç dokunuşlarında titreşimli geri bildirim için.
• com.google.android.gms.permission.AD_ID (Reklam Kimliği / AAID): AdMob ve aracılık ağları tarafından kullanılır; Ayarlar > Google > Reklamlar üzerinden sıfırlanabilir veya silinebilir.
• SDK'ların eklediği izinler: reklam ölçümü için AdServices (ACCESS_ADSERVICES_AD_ID / ATTRIBUTION / TOPICS), abonelik için com.android.vending.BILLING, bildirim altyapısı için com.google.android.c2dm.permission.RECEIVE, ayrıca WAKE_LOCK, FOREGROUND_SERVICE ve yükleme kaynağı servisi. Uygulamanın kendisi sürekli çalışan bir arka plan servisi başlatmaz.
• Zikir verileriniz: zikir listeniz, hedefleriniz, sayımlarınız ve istatistikleriniz; cihazınızda saklanır.
• Cihaz ve kullanım verileri: cihaz modeli, Android sürümü, uygulama sürümü, dil/bölge gibi anonim teknik veriler ile az sayıda uygulama olayı; ayrıca çökme kayıtları.
• Yaklaşık konum: reklam ve onay altyapısının IP adresinden türettiği ülke/bölge bilgisi; yalnızca reklam yayını ve onay yönetimi için. Uygulama konum izni istemez.
• Reklam ortakları: AdMob ve aracılık (mediation) ağları — Meta Audience Network, Vungle (Liftoff), Pangle (ByteDance) ve InMobi — reklam seçimi ve ölçümü için cihaz/reklam tanımlayıcısı verilerini kendi gizlilik politikaları kapsamında işleyebilir.

Uygulama kamera izni istemez: QR okutma, Google Play hizmetlerinin kendi tarayıcı bileşeniyle yapılır ve görüntü uygulamaya aktarılmaz. Konum, mikrofon, kişiler, takvim veya sağlık verilerine de erişilmez.

2. Yerel Veri Saklama

Zikirleriniz, sayımlarınız, hedefleriniz, istatistik kayıtlarınız ve uygulama tercihleriniz cihazınızdaki yerel veritabanında ve ayar deposunda (DataStore) saklanır. Ana ekran widget'larının gösterdiği özet de cihaz içinde kalır. Uygulamayı kaldırdığınızda bu veriler silinir.

Cihaz yedeklemesi: Android'in otomatik yedekleme özelliği açıktır, ancak yedeğe yalnızca uygulamanın oluşturduğu taşıma yedek dosyası ile ayar tercihleriniz dahil edilir; zikir veritabanı yedeğe alınmaz. Yedeklemeyi Android ayarlarından kapatabilirsiniz.

3. Zikir Kardeşliği / Ortak Zikirler (İsteğe Bağlı)

Zikir Kardeşliği, ortak bir zikre katkıda bulunan herkesin toplamını gösteren isteğe bağlı bir özelliktir ve yalnızca onay ekranında "Katıl"a bastığınızda açılır. Onay vermediğiniz sürece bu özellik için sunucumuza hiçbir istek gitmez.

Kimlik: katıldığınızda hesap açılmaz. Cihazınızda kurulum başına anonim bir anahtar çifti üretilir ve istekler bu anahtarla imzalanır; Google'a cihaz kanıtı gönderilmez (Play Integrity kullanılmaz). Bu kimlik reklam kimliği (AAID) değildir ve hiçbir reklam ya da analitik SDK'sına verilmez.

Gönderilen veriler: yalnızca katkınızı sayabilmek için gereken alanlar — hangi ortak zikre ne kadar katkı yaptığınız (zikir kodu ve sayı), katkının ait olduğu yerel gün ve saat diliminiz, katkının ilk/son dokunuş zamanı, kaynağı (uygulama, widget veya elle giriş), uygulama sürümü ve onay metninin sürümü. Sayımlar önce cihazınıza yazılır, doğal duraklarda toplu gönderilir; zikirlerinizin adları, notlarınız, kişisel listeniz veya istatistikleriniz gönderilmez.

Silme: Ayarlar > Kardeşlik > "Kardeşlik verilerimi sil" ile kaydınızı silebilirsiniz; cihazınızdaki kimlik ve bekleyen kuyruk da temizlenir. Geçmiş katkılarınız ortak toplamlarda isimsiz kalır; kişisel sayaçlarınız etkilenmez.

4. Verileri Taşı (QR ve Dosya)

Verilerinizi başka bir cihaza taşımak için iki yol vardır ve ikisi de yalnızca siz başlattığınızda çalışır:

• QR ile taşı: veriniz cihazınızda şifrelenir ve şifreli hâliyle kısa süreliğine sunucumuza konur. Çözme anahtarı yalnızca ekrandaki QR kodundadır, sunucuya hiç gitmez (uçtan uca). Paket, ilk başarılı indirmede ya da en geç 30 dakika içinde sunucudan silinir.
• Dosya ile taşı: veriniz şifreli bir yedek dosyası olarak dışa aktarılır; dosya sizin seçtiğiniz konuma kaydedilir ve Codeida sunucularına yüklenmez.

5. Bildirimler

Bildirimler Firebase Cloud Messaging (FCM) konu (topic) aboneliğiyle gönderilir: duyurular için "genel", Kardeşlik'e katıldıysanız ve ayrıca onay verdiyseniz ortak zikir etkinlikleri için ayrı bir konu. Cihaz bildirim belirteciniz sunucumuza gönderilmez ve sunucumuzda saklanmaz. Ortak zikir bildirimleri varsayılan olarak kapalıdır; Kardeşlik'ten ayrıldığınızda abonelik kaldırılır. Her iki anahtarı da Ayarlar > Bildirimler üzerinden kapatabilir, izni Android ayarlarından geri çekebilirsiniz.

6. Reklam ve Onay Yönetimi

Reklamlar Google Mobile Ads SDK (AdMob) üzerinden yayınlanır (banner, MREC, geçiş, uygulama açılış ve ödüllü reklamlar). Ödüllü reklam yalnızca siz haftalık temayı açmak için izlemeyi seçtiğinizde gösterilir. Kişiselleştirilmiş reklam tercihi, Google User Messaging Platform (UMP) onay ekranındaki seçiminize göre belirlenir. Onay vermediğinizde veya UMP'nin kapsamadığı bir bölgede de reklamlar gösterilir; kişiselleştirme onayı yoksa reklamlar kişiselleştirilmemiş olarak sunulur.

Aşağıdaki mediation adaptörleri ek reklam ağlarına erişim sağlar:

• Meta Audience Network — Gizlilik Politikası
• Vungle (Liftoff) — Gizlilik Politikası
• Pangle (ByteDance) — Gizlilik Politikası
• InMobi — Gizlilik Politikası

Onay tercihiniz ilgili ağlara iletilir ve tercihiniz değiştiğinde yeniden yayılır. Pro aboneliği olan kullanıcılara hiç reklam gösterilmez. Reklamlara zikir verileriniz hiçbir şekilde iletilmez.

7. Analitik ve Çökme Raporlama

Firebase Analytics anonim kullanım istatistiklerini, Firebase Crashlytics ise çökme ve hata kayıtlarını toplar. Olay parametreleri yalnızca kodlardan ve sayılardan oluşur: zikir adı, okunuşu, anlamı ya da yazdığınız herhangi bir metin asla gönderilmez. Kardeşlik kimliği, jetonları ve anahtarları analitiğe ve çökme kayıtlarına yazılmaz. Google'ın Rıza Kipi (Consent Mode) ayarları reddedilmiş olarak başlar ve yalnızca onay kararınıza göre güncellenir.

8. Uygulama İçi Satın Alma (Pro)

Reklamları kaldıran ve ek özellikler açan Pro, Google Play Billing üzerinden aylık veya yıllık abonelik olarak satılır. Uygulamanın eski sürümünde alınan tek seferlik satın alma tanınır ve geçerliliğini korur. Ödeme bilgileriniz Google Play tarafından yönetilir; uygulamamız kart bilgilerinizi görmez. Abonelikleri Google Play > Hesap > Abonelikler üzerinden yönetebilirsiniz.

9. Widget'lar ve Uygulama Değerlendirme

Ana ekran widget'ları son zikrinizi ve sayımınızı cihaz içindeki verilerden okur; dış sunuculara veri göndermez. Uygulama içi değerlendirme akışı için Google Play In-App Review API'si kullanılır; bu API kişisel veri toplamaz.

10. Paylaşım

Zikir kartınızı paylaşmayı seçerseniz kart tamamen cihazınızda oluşturulur ve sistem paylaşım sayfası üzerinden yalnızca sizin seçtiğiniz uygulamaya gönderilir. Paylaşım içeriği Codeida sunucularına gönderilmez.

11. Çocukların Gizliliği

Uygulama 13 yaşın altındaki kullanıcılar için tasarlanmamıştır. Bu yaş grubundan bilerek kişisel veri toplamayız.

12. Veri Saklama ve Güvenlik

Sunucularımızda hesabınız yoktur; yalnızca katıldıysanız Kardeşlik'in anonim kurulum kaydı ve katkı sayıları ile veri taşırken kısa süreliğine duran şifreli paket bulunur. Analitik, çökme ve reklam verileri Google/Firebase'in ve ilgili reklam ağlarının saklama sürelerine tabidir. Tüm ağ trafiği aktarım sırasında HTTPS ile şifrelenir.

13. Haklarınız

KVKK, GDPR ve CCPA kapsamında verilerinize erişim, düzeltme, silme ve işlemeye itiraz hakkınız olabilir. Kardeşlik kaydınızı uygulama içinden silebilir, reklam tercihlerinizi Ayarlar > Google > Reklamlar, bildirimleri Android ayarlarından, aboneliğinizi Google Play hesabınızdan yönetebilirsiniz.

14. İletişim

Sorularınız için [email protected].

1. Permissions & Data We Collect

• INTERNET / ACCESS_NETWORK_STATE: to load ads, run the optional features (Brotherhood, data transfer) and watch connectivity.
• POST_NOTIFICATIONS: to show announcements and, if you joined, shared dhikr notifications on Android 13+.
• VIBRATE: for haptic feedback on counter taps.
• com.google.android.gms.permission.AD_ID (Advertising ID / AAID): used by AdMob and its mediation networks; you can reset or delete it under Settings > Google > Ads.
• Permissions added by SDKs: AdServices for ad measurement (ACCESS_ADSERVICES_AD_ID / ATTRIBUTION / TOPICS), com.android.vending.BILLING for subscriptions, com.google.android.c2dm.permission.RECEIVE for the notification infrastructure, plus WAKE_LOCK, FOREGROUND_SERVICE and the install-referrer service. The app itself starts no long-running background service.
• Your dhikr data: your dhikr list, goals, counts and statistics, stored on your device.
• Device and usage data: device model, Android version, app version, language/region and similar anonymous technical data, a small number of app events, and crash records.
• Approximate location: the country/region the advertising and consent infrastructure infers from your IP address, used only for ad delivery and consent management. The app requests no location permission.
• Advertising partners: AdMob and its mediation networks — Meta Audience Network, Vungle (Liftoff), Pangle (ByteDance) and InMobi — may process device/advertising identifier data for ad selection and measurement under their own privacy policies.

The app requests no camera permission: QR scanning is handled by Google Play services' own scanner component and the image is never passed to the app. It also does not access location, microphone, contacts, calendar or health data.

2. Local Storage

Your dhikrs, counts, goals, statistics and app preferences are stored in a local database and a settings store (DataStore) on your device. The summary the Home Screen widgets display also stays on the device. Uninstalling the app removes this data.

Device backup: Android's auto-backup is enabled, but the backup includes only the transfer backup file the app creates and your settings preferences — the dhikr database is excluded from backup. You can disable backup in Android settings.

3. Dhikr Brotherhood / Shared Dhikrs (Optional)

Dhikr Brotherhood is an optional feature that shows the combined total of everyone contributing to a shared dhikr, and it starts only when you press "Join" on the consent screen. Until you consent, not a single request is sent to our server for it.

Identity: joining creates no account. An anonymous key pair is generated on your device per installation and requests are signed with it; no device attestation is sent to Google (Play Integrity is not used). This identity is not the advertising identifier (AAID) and is never given to any advertising or analytics SDK.

What is sent: only what is needed to count your contribution — which shared dhikr you contributed to and how much (a dhikr code and a number), the local day the contribution belongs to and your time zone, the first and last tap time of that batch, its source (app, widget or manual entry), the app version and the version of the consent text. Counts are written to your device first and sent in batches at natural pauses; the names of your dhikrs, your notes, your personal list and your statistics are never sent.

Deletion: Settings > Brotherhood > "Delete my Brotherhood data" removes your record, and the identity and pending queue on your device are cleared too. Your past contributions remain anonymous in the shared totals; your personal counters are unaffected.

4. Transfer Data (QR and File)

There are two ways to move your data to another device, and both run only when you start them:

• Transfer by QR: your data is encrypted on your device and the encrypted package is placed on our server briefly. The decryption key exists only in the QR code on screen and never reaches the server (end-to-end). The package is deleted on the first successful download, or within 30 minutes at the latest.
• Transfer by file: your data is exported as an encrypted backup file, saved to the location you choose and never uploaded to Codeida servers.

5. Notifications

Notifications are delivered through Firebase Cloud Messaging (FCM) topic subscriptions: a "general" topic for announcements and, if you joined Brotherhood and opted in separately, a topic for shared dhikr events. Your device notification token is never sent to or stored on our server. Shared dhikr notifications are off by default, and leaving Brotherhood unsubscribes you. You can switch both off under Settings > Notifications and revoke the permission in Android settings.

6. Advertising & Consent Management

Ads are served through the Google Mobile Ads SDK (AdMob) (banner, MREC, interstitial, app-open and rewarded ads). A rewarded ad is shown only when you choose to watch one to unlock the weekly theme. Personalization depends on your choice in the Google User Messaging Platform (UMP) consent dialog. Ads are still shown if you decline or are outside UMP's scope; without personalization consent they are served as non-personalized.

The following mediation adapters provide access to additional ad networks:

• Meta Audience Network — Privacy Policy
• Vungle (Liftoff) — Privacy Policy
• Pangle (ByteDance) — Privacy Policy
• InMobi — Privacy Policy

Your consent choice is forwarded to the relevant networks and re-applied whenever it changes. Users with a Pro subscription see no ads at all. None of your dhikr data is ever passed to advertising.

7. Analytics & Crash Reporting

Firebase Analytics collects anonymous usage statistics and Firebase Crashlytics collects crash and error records. Event parameters consist only of codes and numbers: the name, transliteration or meaning of a dhikr, or any text you typed, is never sent. The Brotherhood identity, its tokens and keys are never written to analytics or crash records. Google's Consent Mode signals start as denied and are updated only according to your consent decision.

8. In-App Purchases (Pro)

Pro, which removes ads and unlocks extra features, is sold as a monthly or yearly subscription through Google Play Billing. The one-time purchase from the app's previous version is recognised and remains valid. Payment information is handled by Google Play; our app never sees your card details. Manage subscriptions in Google Play > Account > Subscriptions.

9. Widgets & In-App Review

The Home Screen widgets read your latest dhikr and count from on-device data and send nothing to external servers. The in-app rating flow uses the Google Play In-App Review API, which collects no personal data.

10. Sharing

If you choose to share a dhikr card, it is produced entirely on your device and handed through the system share sheet to only the app you pick. Shared content is never sent to Codeida servers.

11. Children's Privacy

The app is not intended for users under 13. We do not knowingly collect personal data from children under 13.

12. Data Retention & Security

You have no account on our servers; they hold only the anonymous Brotherhood installation record and contribution counts if you joined, plus the encrypted package that rests there briefly during a data transfer. Analytics, crash and advertising data follow the retention policies of Google/Firebase and the respective ad networks. All network traffic is encrypted in transit using HTTPS.

13. Your Rights

You may have rights to access, correct, delete or object to the processing of your data under GDPR, CCPA, KVKK and similar regulations. You can delete your Brotherhood record from inside the app, manage ad preferences under Settings > Google > Ads, notifications in Android settings, and your subscription through your Google Play account.

14. Contact

For privacy questions: [email protected].