← Back to Home

Privacy Policy

Last updated: November 5, 2026

1. Introduction

This Privacy Policy explains how we ("we," "our," or "us," the developer of the Quran AI (AI Quran Reader) mobile application, the "App") collect, use, and share information when you use the App. The App is available on the Apple App Store (iOS). The Android version (package com.skiestech.aiquran) is distributed through Google Play. This policy describes what each version does, and says "iOS" or "Android" where they differ. The consent controls described in §4 and §5 apply to iOS version 1.0.15 and later and Android version code 8 and later. iOS versions before 1.0.15 and Android test builds with version code 7 and earlier behave as described under "Earlier versions" in §4. By downloading, installing, or using the App, you acknowledge that you have read this Privacy Policy. If you do not agree, please do not use the App.

Who we are: Appskies is the developer and data controller responsible for your personal data. You can contact us at Salih Kanat Sk., Özlem Apt. D:2, Girne/KKTC, Mersin 10, Türkiye, or by email at appskiesltd@gmail.com.

2. Information We Collect

2.1 Information You Provide

The App does not require you to create an account. You can use it with an automatically generated anonymous identifier, and we do not collect a username or password. You may optionally provide:

Anonymous sign-in and Firebase services that run from launch: When the App starts, it signs in to Firebase Authentication anonymously, which assigns a pseudonymous identifier (a Firebase UID) rather than creating a named account, and it reads its remote configuration from Firebase. Firebase also creates a Firebase Installations identifier for the App on your device. On Android, Firebase App Check (Google Play Integrity) attests requests from the App, and Firebase Cloud Messaging registers the device with Google to obtain a push token, which the App stores on your device only. These services are needed to run the App, they run from launch, and they are not switched off by any analytics or consent choice.

2.2 Information Collected Automatically

2.3 Information We Do NOT Collect

2.4 Information About Religious Beliefs

Questions you type and your worship and reading records may reveal your religious beliefs, which many laws treat as special-category (sensitive) data. Your worship and reading records are kept on your device. The AI assistant is optional and is used only when you choose to send a message: AI questions are sent only when you ask a question in the assistant, including when you select a suggested question, and sending is your explicit action (see §9). Before your first AI message the App shows a notice that your message goes to OpenAI (on iOS through AIProxy, on Android through our server) and asks you to accept it; nothing is sent until you accept, declining keeps your draft and sends nothing, and your acceptance is stored on your device. Please do not include sensitive personal information in your questions that you do not want shared.

3. How We Use Your Information

4. Advertising, Attribution and Analytics (ATT on iOS)

Platform note: The App Tracking Transparency (ATT) prompt and the IDFA are iOS-only. The paragraphs in this box describe the iOS version of the App. The Android version also shows ads and uses attribution and analytics SDKs; it is described in the separate box below. The consent form, "Privacy choices" and "Do not sell or share" controls that apply to both platforms are described in the third box.

The free version of the App shows advertisements through Unity LevelPlay (ironSource), which includes Unity's Ad Quality SDK (see §9). The App also uses AppsFlyer to measure installs and sessions, and Firebase Analytics and Crashlytics for product analytics and crash diagnostics. These providers may process device identifiers, ad interactions, usage data, IP-derived approximate location, and related technical information to deliver and measure advertising and attribution. When the IDFA or cross-company data is used, Apple treats this as "tracking."

iOS version 1.0.15 and later: consent first. In the EEA, UK and Switzerland the App shows a consent form from Google's User Messaging Platform (UMP) with the options Consent, Do not consent and Manage options. It appears on the home screen before any ads, attribution, analytics or crash reporting start, and before the ATT prompt. Nothing starts until you answer. If the form cannot be shown, or you close it without a choice, nothing starts and the App asks again on a later launch (it fails closed). Outside those regions the App shows no consent form. What may run follows your answers, using the standard TCF purposes: storing and accessing information on your device (purpose 1) is needed before ads or any SDK can start; Firebase Analytics and Crashlytics also need audience statistics (purpose 9); sharing ad user data needs purpose 7; personalized ads need purposes 3 and 4. LevelPlay's GDPR consent is set to granted only with purposes 1, 3 and 4 (and only while "Do not sell or share" is off; outside those regions, only if you allowed ATT and the switch is off), AppsFlyer receives the DMA consent flags and starts only with ad storage and user data consent, Firebase receives Google consent mode signals (analytics storage, ad storage, ad user data, ad personalization), and Crashlytics collection follows the consent for analytics. RevenueCat's collection of the AdServices attribution token, and the AppsFlyer ID it receives, need attribution consent in those regions; outside them they run unless "Do not sell or share" is on. After the consent form, the App shows the ATT prompt only if you consented to at least one ad-related purpose; if you declined everything it skips ATT. ATT still separately controls IDFA access.

Earlier versions (iOS versions before 1.0.15). These versions have no consent form, no "Privacy choices" and no "Do not sell or share" switch. On iOS, we show Apple's App Tracking Transparency (ATT) prompt on the home screen the first time. Until you have answered it, the App does not start LevelPlay, AppsFlyer's network start, Firebase Analytics collection or Crashlytics collection. After you answer, whatever your answer, they start; on later launches they start when the App opens. We pass your choice to the advertising system:

What runs before the ATT prompt (iOS versions before 1.0.15). Some SDKs run at launch, before you answer the ATT prompt. RevenueCat is configured at launch. The App also asks RevenueCat to collect Apple's AdServices attribution token at launch, so that Apple Ads installs can be attributed; Apple does not require ATT for this token and it does not use the IDFA. The App also passes the AppsFlyer ID to RevenueCat at launch, and RevenueCat can then collect device identifiers such as the IDFV and your IP address (and the IDFA only if iOS gives access).

Apple privacy manifest and tracking domains. In all iOS versions, the App's Apple privacy manifest declares that the App tracks (NSPrivacyTracking) and lists Firebase and Google domains used for analytics, crash reporting and ads as tracking domains. We therefore do not say that Firebase is free of tracking. Apple's system may block connections to declared tracking domains while ATT permission is not granted, so Firebase analytics or crash data may not be delivered if you decline. Before 1.0.15 the App itself does not turn them off when you decline ATT; from 1.0.15 the consent form and the "Do not sell or share" switch control them as described above.

You can change ATT permission in iOS Settings › Privacy & Security › Tracking. Users with an active premium (ad-free) subscription are not shown ads.

Android version: The free version of the Android app shows banner, interstitial and rewarded ads through Unity LevelPlay (ironSource) and its demand partners. LevelPlay includes Unity's Ad Quality SDK, which monitors the ad creatives shown in the App and may process technical and device data, such as your IP address and device identifiers, for that purpose. The App uses AppsFlyer to measure installs and sessions, and Firebase Analytics and Firebase Crashlytics for product analytics and crash diagnostics. Users with an active premium (ad-free) subscription are not shown ads, but the SDKs may still start and collect identifiers for them (the App starts them whether or not you are subscribed).

Advertising ID and other data: These SDKs can read the Android advertising ID (a resettable identifier managed by Google Play services). The merged release manifest of the Android app declares the com.google.android.gms.permission.AD_ID permission (and Android's ad-services ID and attribution permissions), because the bundled SDKs declare them. These SDKs also use other device identifiers, the Google Play install referrer, IP-derived approximate location, ad interactions, and install and in-app event data. This data is used to deliver and measure ads, attribute installs, prevent fraud, and understand how the App is used, and it is shared with LevelPlay, its demand partners and AppsFlyer. The Android app also links the AppsFlyer ID to your RevenueCat subscriber record once attribution is running.

Android version code 8 and later: consent first. In the EEA, UK and Switzerland the app shows a consent form from Google's User Messaging Platform (UMP) with the options Consent, Do not consent and Manage options when it opens, before any ads, attribution, analytics or crash reporting start. Nothing starts until you answer. Each time the app opens it asks UMP again, and if that fails it uses your last stored choice; with no stored choice, nothing starts (it fails closed). Outside those regions the app shows no consent form. What may run follows your answers, using the standard TCF purposes, and Google must also be among the vendors you consented to: analytics and ad storage need purpose 1, sharing ad user data needs purposes 1 and 7, and personalized ads need purposes 1, 3 and 4. LevelPlay starts only with ad storage consent (purpose 1), and LevelPlay's GDPR consent is set to granted only with purposes 1, 3, 4 and 7; AppsFlyer receives the DMA consent flags and starts only with ad user data consent; Firebase Analytics receives Google consent mode signals (all denied by default in the app manifest until you decide); Crashlytics collection follows the analytics consent, and unsent crash reports are deleted if you withdraw it. The app links the AppsFlyer ID to RevenueCat only after AppsFlyer has started with consent. Android has no ATT prompt; ATT is an Apple feature.

Earlier Android test builds (Android version code 7 and earlier): no ATT and no consent prompt. These builds do not show their own consent prompt for advertising, attribution or analytics, and they do not use Google's User Messaging Platform. When the SDKs start: on the very first launch, the App starts Firebase Analytics, Crashlytics and AppsFlyer, and starts LevelPlay with personalized-ads consent set to "not granted," when the home screen opens. On all later launches the App applies its saved start-up decision as the app process starts, so these SDKs run from launch, without waiting for a screen. LevelPlay and its partners may still use the advertising ID for ad delivery, measurement and fraud prevention under their own policies.

Your choices on Android: In version code 8 and later, use Settings › Privacy choices (shown where the consent form applies) and Settings › Do not sell or share my personal information (see the box below). On every version you can delete your advertising ID in your device settings, usually under Settings › Privacy › Ads › Delete advertising ID or Settings › Google › Ads, depending on your device and Android version. Older Android versions offer "Opt out of Ads Personalization" in the same place. On current Android versions, apps receive a string of zeros instead of an ID after you delete it. Version code 7 and earlier have no in-app switch to turn off analytics, crash reporting or attribution. To stop all collection by these SDKs on those builds, leave the test programme and uninstall the App. To ask about or request deletion of data we hold, see §6, §10 and §13.

5. Legal Basis for Processing (EEA/UK Users)

6. Data Retention

7. Data Storage and Security

We use reputable cloud infrastructure (Google Firebase) and apply industry-standard safeguards, including encryption of data in transit using TLS. No method of transmission or storage is completely secure, but we work to protect your information with appropriate measures.

8. Sharing and Disclosure

We do not sell your personal information for money. The advertising and attribution providers described in §4 (LevelPlay, its demand partners and AppsFlyer) receive device identifiers and related device and usage data: on Android, the Android advertising ID; on iOS, the IDFA only if you allow tracking; and on both, other identifiers and your IP address. Some laws, including the CCPA/CPRA, may treat this as a "sale" or "sharing" of personal information. We share information only as follows: with the service providers listed in §9 to operate the App; when required by law or legal process; to protect our rights, users, or the public; in connection with a business transfer; or with your consent.

In iOS version 1.0.15 and later and Android version code 8 and later, you can opt out of this sharing with Settings › Do not sell or share my personal information. It is on by default outside the EEA, UK and Switzerland (see §4 for what it does). Earlier versions have no such switch.

9. Third-Party Services

The App uses the following third-party services, each governed by its own privacy policy:

AI Assistant Data

On Android, your current message is sent to our Firebase HTTPS callable aiChat in the us-central1 region, which calls OpenAI on the server with your message and a server-side instruction. On iOS, your current message is sent through AIProxy to OpenAI. We do not attach your email, location, purchase data, past chat history, or Firebase UID to the request sent to OpenAI; anything you include in the current message itself is sent as part of that message. The AI assistant is shown only to premium subscribers.

On Android, questions are sent only when you ask a question in the assistant. This includes selecting a suggested question. On Android, our server records a daily usage counter linked to your pseudonymous Firebase UID and operational metadata (request outcome, model, input character count, token counts, and latency), but does not record the message or reply text, except for an AI reply you choose to report in Android version code 9 and later (next paragraph).

Reporting an AI response (Android version code 9 and later). If you tap Report on an AI assistant reply and confirm, the app sends that reply's text, the reason you chose (offensive or inappropriate, inaccurate or misleading, or something else), your app language, the app version and the platform ("android") to a Firebase Cloud Function so we can review the response and improve the assistant. The report does not include your question, your email address, your Firebase user ID or any device identifier, although the reply text may itself repeat words from your question. It is stored in Firestore under a random document ID, without your Firebase user ID, and it is deleted automatically about 90 days after it is created (Firestore's automatic deletion can lag the exact expiry time). To limit abuse, a separate counter keyed to your pseudonymous Firebase user ID records how many reports that identity submitted per UTC day, is capped at 20 per day and expires one day after the end of that UTC day (Firestore's automatic deletion can lag). The counter is not used to look up reports, but because it and the report are written together, someone with administrative access to our database could, while the counter still exists, match your most recent report to your pseudonymous ID by its write time. After the counter has been deleted the report cannot be traced to you, so we generally cannot find or delete a particular person's report on request. If the report cannot reach our servers, the app instead prepares an email to appskiesltd@gmail.com that you review and send yourself.

OpenAI states that data submitted through its API is not used to train its models unless you opt in, and that limited abuse-monitoring logs may be retained, normally for up to 30 days, with exceptions described in its API data-usage policy. These logs may include message and reply content. On Android, our OpenAI requests set store: false to limit application-state retention; this does not disable OpenAI's abuse-monitoring logs.

Server Logs

Our Cloud Functions write operational logs to Google Cloud Logging. These logs include your Firebase UID and request metadata (outcome, model, input character count, token counts and latency for AI requests), and standard platform request information. Message and reply text is not written to these logs by our code. When you report an AI response (Android version code 9 and later), our code logs only the outcome and the reason code, not the reply text and not your Firebase UID. Retention is described in §6.

International Data Transfers

We are based in the Turkish Republic of Northern Cyprus. Our providers, including Google (Firebase, Google Cloud), OpenAI, RevenueCat, AppsFlyer, Unity and Apple, process data in the United States and other countries, which may be outside your country and may not offer the same level of data protection as the EEA, UK or Switzerland. For transfers of personal data from the EEA, UK or Switzerland, we rely on the safeguards each provider offers, such as the EU-US Data Privacy Framework (where the provider participates) or Standard Contractual Clauses. We have not independently verified each provider's participation or certification. Contact us at the address in §13 if you would like more information.

10. Your Privacy Rights

Depending on your location, you may have the right to access, correct, or delete your personal data, to object to or restrict certain processing, to data portability, and to withdraw consent. Because the App does not use traditional accounts, most of your data is either stored on your device or associated with an anonymous identifier.

EEA/UK Users (GDPR)

Where the GDPR applies, your rights include:

California Residents (CCPA/CPRA)

Where the CCPA/CPRA applies, your rights include:

You can exercise these rights by emailing appskiesltd@gmail.com. We will not discriminate against you for exercising your privacy rights.

Deletion and Other Requests

In-app deletion (iOS): On iOS, if your installed version includes Settings › Delete My Data, use it to delete your optional app-owned cloud email, referral credits and used promo-code history, your Firebase Authentication guest account, and the locally cached email. The authenticated App deletes its own Firestore records, queues and attempts to sync a best-effort RevenueCat request to remove any legacy email attribute, deletes the current anonymous Firebase account, and creates a new guest session so the App remains usable. RevenueCat's SDK does not expose provider-side confirmation of that attribute request; contact us at the address in §13 if you require confirmed removal by the provider. If interrupted, the App retains an on-device recovery phase until the operation finishes. If Firebase removes the local credential without confirming server-side account deletion, the App does not claim success: it retains the old anonymous identifier on the device as the support reference shown to you and restores a separate guest session.

In-app deletion (Android): On Android, use Settings › Delete My Data to delete your optional email record, your referral record and your Firebase Authentication guest account, and to clear the email saved on your device. The App then creates a new guest session. If the App shows a deletion reference, keep it. Email the reference to appskiesltd@gmail.com to ask us to remove your referral redemption record, which the in-app flow does not delete, or if Firebase could not confirm deletion of the old guest account. See §6 for what this flow does not delete.

What deletion does not remove: Deleting app-held data or your Firebase guest account does not delete the pseudonymous RevenueCat subscriber identifier or purchase history held by your app store (Apple or Google Play) or RevenueCat, where used, for subscription access and restoration; it does not cancel a store subscription or erase preferences and reading progress stored only on your device; and it does not delete data already held by analytics, crash-reporting, attribution and advertising providers. Delete the App to remove on-device data, and manage or cancel subscriptions through the store where you purchased them.

Additional requests and earlier app versions: Contact us at the address in §13 if the in-app option is not present, if you want assistance, or if you need to request deletion from a service provider. Providers may retain limited transaction, security, fraud-prevention, or legal-compliance records under their own policies and applicable law. EEA/UK users (GDPR) and California residents (CCPA/CPRA) have the additional rights described by those laws, including the right to lodge a complaint with a supervisory authority (EEA/UK) and the right to opt out of "sale"/"sharing" (California); we honor opt-out signals the App supports: the "Do not sell or share my personal information" switch and your consent form choices (iOS 1.0.15 and later, Android version code 8 and later), on iOS your ATT choice, and on Android a deleted advertising ID (see §4). The App does not currently read other browser or device-level opt-out signals.

11. Children's Privacy

The App is not directed to children under 13 (or the minimum age required in your jurisdiction), and we do not knowingly collect personal information from them. If you believe a child has provided us information, contact us and we will delete it.

12. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above and, where appropriate, through an in-app notice.

13. Contact Us

If you have questions about this Privacy Policy or your data, contact us at: appskiesltd@gmail.com.