IQRA has no account and never asks who you are. Your reading and your hatim live on your device. Anonymous statistics tell us which parts of the app help people read; nothing in them can be traced back to you. This page sets out exactly what is handled and by whom.
IQRA (“the App”) is a Quran reading app. It presents all 6,236 ayahs one screen at a time, in Uthmani Arabic with translation and optional transliteration, plays recitation with word-by-word highlighting, and tracks your progress towards a complete hatim.
The App has no account and no sign-in, and never asks for your name, your email or any other detail that identifies you. It does collect anonymous usage statistics so we can tell which parts of the App are helping people read. These are attached to a random identifier, never to you. Your reading progress, your saved ayahs and your hatim plan are kept on your device. The App plays audio; it never records any. If you subscribe to Premium, Apple handles the payment and we never see your card details.
This policy explains what the App stores, what it sends, why, and who else is involved. It also covers this website. By using the App or the site, you agree to the practices described here.
The App needs to remember what you have read in order to keep your hatim at all. All of the following is written to storage on your iPhone, and the copy on your device is the one the App actually runs on:
Which ayahs you have read, your current bookmark in the mushaf, and your progress through each of the 30 juz. This is the record your hatim percentage and your widgets are drawn from.
Your chosen pace, your daily goal, and the day-by-day ledger the App uses to show how each day of your plan went.
The ayahs you save, your chosen translation, which reading lines are visible, type size and tone, language, sound settings and reminder preferences.
Verse audio you have listened to is kept in the App’s cache so it can play again without downloading. You can clear this cache at any time from the App’s settings.
If you enable the daily ayah notification, it is scheduled locally by iOS on your device at the time you choose. It is not a push notification, and no server is involved in sending it.
Because the App has no sign-in, your progress cannot be moved between devices by us and cannot be restored if you delete the App. A new phone starts from zero unless you restore an iPhone backup. The anonymous statistics described below are not progress and cannot be turned back into it.
We collect usage statistics so we can tell which features actually help people build a daily reading habit, and which parts of the App confuse them.
The App generates a random identifier for each installation: a string with no meaning, created on your device. It is stored in your device’s Keychain, which means it can survive deleting and reinstalling the App; that continuity keeps our statistics honest, and it still says nothing about you. Every statistic described below is attached to that identifier and to nothing else.
It is not your Apple ID, not an advertising identifier, and not derived from your device’s serial number, phone number or any hardware detail. It is not linked to a name or an email address, because the App never collects either. We cannot use it to work out who you are, to contact you, or to recognise you in any other app or website.
These records describe what happened in a session, not who did it. In practice we look at them in aggregate: how many readers finish their first juz, or whether a hatim plan makes people read more.
Statistics are handled by Firebase Analytics (Google Analytics for apps) and stored in Cloud Firestore, both operated by Google on our behalf. Firestore holds the anonymous records described above and nothing else. There are no user profiles in it, because there are no users to profile.
When you play an ayah for the first time, the App downloads that verse’s recitation from a public Quran audio service, along with the word-timing data that drives the word-by-word highlighting. Like any internet request, these downloads carry standard connection data such as your IP address to the server that answers them. They carry no identifier from the App: not the anonymous identifier from section 3, and nothing about your progress.
Downloaded audio is cached on your device, so a verse you have listened to plays again without any network request at all.
The App does not use your microphone. It plays recitation and optional ambient sound; it does not record anything. There is no microphone permission request, no voice capture and no recording of any kind.
We also do not collect:
We do not sell personal data, we do not share it with data brokers, and we do not use your reading data to train machine-learning models.
IQRA Premium is sold through the App Store as an auto-renewing monthly or yearly subscription. The entire transaction is processed by Apple. We never see, collect or store your card details, billing address or Apple ID credentials.
We use RevenueCat to check the receipt Apple issues and to tell the App whether Premium is active. RevenueCat receives the anonymous identifier described in 3.1, the product you bought and the state of the purchase: active, expired or cancelled. Nothing that identifies you. When you tap “Restore purchases”, this is the check being repeated.
Apple also provides aggregate sales reporting through App Store Connect: how many purchases were made in which country. Those reports are anonymous.
The App relies on the following services. Each receives only the data described above, and our processors are not permitted to use it for their own purposes.
| Service | Purpose | Policy |
|---|---|---|
| Apple App Store Apple Inc. | App distribution, payment processing, subscription billing and renewals | Apple |
| RevenueCat RevenueCat, Inc. | Receipt validation and entitlement state; receives the anonymous identifier and purchase status | RevenueCat |
| Firebase Analytics Google LLC | Anonymous in-app usage statistics | |
| Cloud Firestore Google LLC | Storage of the anonymous statistics described in section 3 | |
| Quran audio services Public recitation CDNs | Serving verse recitation audio and word-timing data on request; receive standard connection data only, no App identifier | Various |
This website is a set of static pages. It sets no cookies, runs no analytics and loads no trackers. The only third party involved is Google Fonts, which serves the typefaces.
No system is perfectly secure. If a breach affecting your data ever occurs, we will notify affected users and the relevant authority as required by law.
IQRA contains no user-generated content visible to others, no chat, no advertising and no external links inside the reading experience, so it is suitable for a general audience. It is not directed at children under 13, and we do not knowingly collect personal information from them. Because the App requires no account and collects no personal identifiers by default, a child can use it without providing any personal data at all. If you believe a child has given us personal information, contact us and we will delete it promptly.
Depending on where you live, you may have rights under the Turkish Personal Data Protection Law (KVKK), the EU and UK GDPR, or comparable legislation: to know what is held about you, to have it corrected or erased, to object to processing, to restrict it, and to receive a copy in a portable format.
Most of this is directly in your hands:
One honest limitation: the statistics described in section 3 are anonymous by design, and we hold nothing that connects them to you. That means we cannot look up “your” records to show you or delete them individually, because we have no way to tell which are yours. Sending stops when you delete the App.
For anything else, email the address on our contact page with “Privacy” in the subject line. We respond within 30 days. You also have the right to complain to your local data protection authority.
Our processors, Google, Apple and RevenueCat, operate infrastructure in several countries, including the United States. Where data is transferred out of Turkey, the EEA or the UK, those transfers rely on the safeguards those companies provide, including the European Commission’s Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework.
We may update this policy as the App changes. In particular, if a future version adds an optional account or progress sync, this page will be updated before that version ships and the change will be described plainly. The date at the top always reflects the current version. If a change materially affects how your data is handled, we will tell you inside the App before it takes effect. Continuing to use the App after a change means you accept the updated policy.
Questions about this policy, or a request about your data, can go to the address on our contact page. A person reads it, usually within two working days.