Privacy Policy

This Privacy Policy explains how Thabat - Quran Memorization Review ("Thabat", "we", "us", or "our") collects, uses, and shares personal data when you use the Thabat mobile application, our website and their related services (the "Service"). It should be read together with our Terms & Conditions.

In short: we use your data to run your memorisation practice. We do not sell it. We keep recitation audio only when you choose to send it with a report. You can turn off usage analytics and delete your account from the app.

1. Who We Are

We operate Thabat, a Qur'an-memorization ("Hifz") practice app. For the purposes of applicable data-protection law, we are the controller of the personal data described here. You can reach us about privacy and your data at support@thabat.net or through the in-app support form.

2. Data We Collect

2.1 Data you provide

• Account and identity: your email address and, if you sign in with Google or Apple, the name and profile picture (if any) that the provider shares. If you use Apple's "Hide My Email", we receive the relay address Apple gives us. These are managed by our authentication provider (see Section 4).
• Date of birth and age category:
  • Older app versions asked for your date of birth during onboarding.
  • Newer registrations do not collect or verify a birth date. They store a fixed placeholder date and a default adult category instead.
  • Birth dates already supplied stay private and are not shown to other users.
  • The recorded category is used for account settings. It is not reliable proof of a person's age.
• Profile: a display name and an optional short bio that you choose.
• Country: a country code from your device's region settings or that you provide during onboarding.
• Memorization and study data:
  • which portions of the Qur'an you mark as memorized;
  • your quiz sessions and individual answers, including what you type or select, timing, confidence, hints used and correctness;
  • your spaced-repetition review history, saved quiz settings, streaks and daily-practice records;
  • experience points, levels, quests, rewards and similar progress data.
• Recitation data: see Section 2.5.
• Streak-pause reasons and notes: if you pause your streak, we store:
  • the reason you select, which can include health-related reasons (such as illness or menstruation) or a religious-observance reason (such as i'tikaf);
  • any free-text note you add.
• Support, reports and feedback:
  • support requests: the subject, message and category you choose;
  • content reports (for example, a question you think is wrong);
  • recitation-grade reports;
  • ideas, votes and comments you post on the in-app ideas board;
  • reactions you give to in-app announcements;
  • answers to optional surveys or feedback prompts.
• How you found us: if you answer "How did you hear about us?" or enter a friend's referral code, we store your answer and the code used.
• Preferences: language (Arabic, English or Urdu), theme, font and text size, reminder and notification settings, email preferences, and similar choices.

2.2 Data collected automatically

• Usage data: timestamps of your activity, such as:

  • when you were last active;
  • daily logins and streak dates;
  • the notifications and emails we send you.

  We use these to run features like streaks, reminders and your activity view, and in aggregate to understand overall app usage.

• Device and app information:

  • Support snapshot. When you contact support, the app attaches a technical snapshot to help us troubleshoot: app version, platform (iOS/Android/web), operating-system version, locale, theme and timezone. It also attaches a diagnostic log of recent app events. The log records technical events (screens opened, network errors, sign-in steps). It is designed to leave out passwords, tokens, the contents of your answers and the text of your recitations, and to mask email addresses.
  • Timezone. Your device's timezone is also used to schedule reminders and to calculate day boundaries.
  • Analytics. The separate analytics collection described in Section 2.4 may include device models and identifiers.

• Device sessions: we record a technical identifier for each signed-in session and when it was first and last seen. This lets us keep your account secure and, where enabled, keep it signed in on one device at a time (see the Terms).

• Push notification token and device identifier: if you enable notifications, we store a push token and a randomly generated device identifier so we can deliver notifications to your device.

• Diagnostics: if the app or server encounters an error, we collect crash and error reports through our diagnostics provider (see Section 4). We do not deliberately attach your identity to these reports.

• Product experiments: we sometimes show different versions of a screen or message to different groups of users to learn which works better. We record which version you were shown.

• On your device: the app stores data locally on your device, including:

  • your progress, settings, sync queue and cached content;
  • your sign-in token and a device identifier, kept in the device's secure storage;
  • your kept page recitals (see Section 2.5).

We use third-party product analytics and, on eligible Android accounts, advertising measurement, as described in Section 2.4. We do not store your IP address in our own logs. Our servers do not log request contents, and authentication tokens and cookies are removed from our logs.

2.3 Data from third parties

• Authentication provider: your verified email address, and your name and profile picture where the sign-in provider shares them.
• Subscriptions provider and app stores: if you subscribe, we receive your subscription status and related purchase events so we can unlock paid features. These include the product, store, trial status, renewal, cancellation, expiry and refund events and dates. We do not receive your payment card details.
• Email delivery provider: whether an email we sent you was delivered, bounced, marked as spam, opened or clicked (see Section 2.6).

2.4 Google Analytics for Firebase (from version 1.0.8)

Starting with native app version 1.0.8, we use Google Analytics for Firebase to understand app usage and measure the effectiveness of our marketing. Older app builds without this SDK do not collect this analytics data.

• What Google may receive. When usage sharing is enabled, Google may receive:

  • app launches, sessions, screen names and engagement;
  • app-instance and device identifiers;
  • app version, operating system, device model and language;
  • approximate location derived from IP addresses.

  We do not request GPS or precise location for analytics.

• How events are linked to you. While you are signed in, events are linked to an opaque internal account identifier, not your name or email address. This is pseudonymous data, not anonymous data. We may analyse it alongside our own account records. Our server also stores your app installation's analytics identifier so it can report subscription changes to the right installation. That record is deleted when you turn usage sharing off or delete your account.

• Properties we send. We send limited categorical properties, such as:

  • subscription tier, interface language and experiment assignment;
  • a broad range for the amount marked as memorized;
  • whether notifications and recitation are turned on;
  • how you found the app;
  • device accessibility settings (font-size range and whether a screen reader is enabled).

• Purchases and subscriptions.

  • Starting a trial or subscription. When you start a free trial or a subscription in the app, we report it to Google Analytics with the plan, its price and currency, and the screen or feature that led you to it.
  • iPhone. The app also passes the store's purchase record to Firebase, so the purchase is measured the way Google Play reports Android purchases.
  • Later changes. Our servers report later changes to your subscription: a trial becoming paid, a renewal, a cancellation or turning renewal back on, an expiry, a failed payment or a refund. Each report includes the plan, any amount charged or refunded, whether you were still in your free trial, and the store's reason for a cancellation or expiry. It is linked to the app installation that was registered while usage sharing was on.
  • Android. Google Play may also report store purchase and subscription events, including product identifiers and amounts, where its integration is enabled.
  • None of this includes your payment-card details.

• What we never deliberately send to Google Analytics:

  • your name, email address or exact birth date;
  • support messages, ideas or reports;
  • quiz answers;
  • recitation audio or transcripts;
  • Qur'anic text, or identifiers of individual surahs, ayahs, juz or pages.

• Staff "view as". Nothing is sent while a staff member is viewing an account in read-only support mode (see Section 4.2).

Turning analytics off

• The default. Usage analytics is enabled by default in supported release builds.
• How to turn it off. You can stop future collection on a device in Settings → Account & data → Data & privacy → "Share usage analytics".
• What the setting covers. It applies to that device across accounts. It does not carry over automatically to your other devices, and a fresh installation may use the default again.
• What turning it off does not do. It does not disable the core app or delete data already collected.

Android advertising measurement

• When it can be used. On Android, advertising identifiers and advertising-measurement signals may be used only for accounts that meet all of these conditions:
  • recorded as adults;
  • known not to be staff;
  • the device region and timezone indicate a location outside the European Economic Area, the United Kingdom and Switzerland.
• Unknowns count as no. An unknown age category, staff status or location does not enable these signals.
• Under-18 accounts. Accounts registered as under 18 are excluded. Newer registrations use a default adult category rather than a verified age (see Sections 2.1 and 9).
• Google Ads. Where Google Ads integration is enabled, eligible signals, including the start of a free trial or subscription with its price, may be used to measure campaign effectiveness.
• Off for everyone. Ad personalization and remarketing signals are disabled.

iOS

On iOS, this integration is for product analytics only. We build it without advertising-ID support and disable advertising-measurement and personalization signals. We do not use these analytics events for cross-app advertising tracking, and we do not ask for App Tracking Transparency permission.

Network data and retention

• Google receives network information when the SDK communicates with its services, and derives approximate location from IP addresses. Our own server logs do not store your IP address.
• Google's processing is also described in Google's Privacy Policy and Google's partner-site and app information.
• We keep event-level analytics in Google Analytics for up to 14 months, and raw exported events for up to 60 days. Aggregated reports may be kept longer.

2.5 Microphone, recitation and recordings

Some features let you recite aloud and have the app check your recitation: the "recite" question in quizzes, and "Recite the page" (Tasmīʿ). They use your microphone only after you start a recitation, and only with your permission.

• Speech-recognition services.
  • What we send. While you recite, the audio is sent from your device to our servers, and from there to one or more speech-recognition services (listed in Section 4.1). They turn it into text so we can compare it, word by word, with the Qur'anic text on our side.
  • What the services do not receive. They receive the audio only. They do not receive your name, your email address or the āyah you were asked to recite.
  • Who checks the result. We compare the text with the Qur'anic text ourselves. No AI language model is used to grade your recitation.
• Audio is graded and discarded.
  • Our servers do not save the audio of your recitations.
  • During "Recite the page", a short piece of audio where a possible mistake was heard may be held in server memory, never on disk, while your result is open. This lets you send it with a report if you choose. It is normally released within minutes of closing the result, and never kept longer than 4 hours.
  • Where a speech-recognition service stores files for processing, we instruct it to delete them, or delete them ourselves after the call.
• What we store about a recitation.
  • Recite questions. For a recite question, we store your grade together with your quiz session. The grade includes the score, the word-by-word result, and the text that the speech-recognition services heard. It is used to show your results, to review a grade you question, and to improve accuracy. It is deleted with your account.
  • Recite the page. For "Recite the page", we store word-level results: which words were recited correctly or missed, and where you slipped, so the app can show you where to focus. We do not store the text the services heard.
  • Usage records. We keep records of how many minutes and checks you used, so we can apply plan limits.
  • Cost records. We keep technical records of each call to a speech-recognition service: engine, duration, cost and the length of the text. They are not linked to your name or email, and are deleted after 90 days.
• When you report a grade. If you tap to report a recitation grade, we attach your recording of that āyah or piece so a scholar on our team can listen to it. We also attach what each service heard, the word-by-word result, your note and technical details. The app tells you this before the report is sent.
  • The recording is kept for 30 days, then deleted.
  • The rest of the report is kept for 90 days, then deleted.
  • These limits apply even if you delete your account earlier. Your account link is removed at deletion, and the report is deleted when its period ends.
  • Report recordings are heard only by authorised scholars and administrators, and can be sent again to our speech-recognition services to re-check the grade.
• Recordings kept on your phone ("My recitations"). When the "Keep my recitations" setting is on, page recitals are saved on your phone so you can listen back.
  • We do not upload them.
  • The phone keeps up to 50 recitals or 750 MB, and the oldest are removed first.
  • Sound effects such as the masjid sound and noise cleanup are applied on your phone only.
  • You can delete one recital, older recitals, or all of them in Settings, and turn the setting off.
  • On iPhone, files in the app may be included in your own iCloud or device backups, under your Apple account settings. On Android they are excluded from backup.
  • If you share or save a recording, it goes where you send it, and that is outside our control.
• No training, no voice identification.
  • We do not use your recordings or transcripts to train AI models. Where a speech-recognition service offers a setting that lets it use our data to improve its models, we keep that use turned off.
  • We do not use your voice to identify you.
• Improving the grader. Scholars may use reported grades to approve corrections to how specific words are checked. A correction stores only the word's position in the Qur'an and the spelling the services heard, never your audio or your identity.

2.6 Emails

• What we send. We send email through our email delivery provider (see Section 4.1):

  • Service emails: for example a failed payment, a trial that is about to become paid, a renewal reminder, a scheduled account deletion, and our replies to your support requests.
  • Practice and news emails: for example a welcome, a weekly progress summary, reminders to come back, and announcements.

  Practice and news emails use your own progress figures, such as āyāt memorized and your streak.

• How to stop them.

  • You can turn practice and news emails off, or choose fewer, in the app's Settings.
  • You can also use the unsubscribe link in any such email.
  • If you never changed the setting, these emails may be sent to you.
  • Service emails cannot be turned off while you have an account, because they concern your account or payments.

• Email tracking.

  • Links in our emails go through our own short links, so we can count clicks.
  • We may also record whether an email was delivered, bounced, opened or marked as spam.

• Our "do not email" list.

  • If you unsubscribe, an email bounces, or you mark our email as spam, we keep the address on a "do not email" list so we respect that choice.
  • We keep this list even after an account is deleted, so we never email you again by mistake.

• Apple "Hide My Email". We do not send practice and news emails to Apple relay addresses.

3. Why We Use It

We use personal data to:

• create and secure your Account and authenticate you;
• provide the core Service, including:
  • syncing your memorization progress across devices;
  • generating and grading quizzes and recitations;
  • scheduling spaced repetition;
  • showing your streaks, progress and analytics;
• send you the notifications and emails you receive under Sections 2.6 and 10;
• apply account age-category settings;
• provide customer support and respond to your reports, ideas and feedback;
• operate subscriptions, apply plan limits and unlock paid features;
• understand app usage, run product experiments and measure marketing effectiveness, under the controls in Section 2.4;
• keep the Service secure, prevent abuse, diagnose problems and improve reliability and grading accuracy;
• comply with legal obligations.

Depending on where you live, our legal bases for processing may include:

• performing our contract with you;
• your consent, for example for notifications, the microphone, and sensitive data such as health-related streak reasons;
• our legitimate interests in operating, securing, measuring and improving the Service;
• compliance with legal obligations.

Some of the data described above may be treated as sensitive under some laws. This includes your date of birth, health-related streak reasons, religious-observance reasons, your voice recordings, and the fact that you use a Qur'an-memorization app. We rely on your consent to collect and use it for the features you choose to use. You can withdraw consent by stopping the feature, changing the setting or deleting the data.

4. Who We Share It With

We do not sell your personal data. We share it only with the providers below, who process it on our behalf to operate the Service, and in the other cases described in this section.

4.1 Service providers

• Google (Google Analytics for Firebase, Firebase Cloud Messaging and, for eligible Android advertising measurement, Google Ads) — receives:
  • the usage data, pseudonymous identifiers and device data described in Section 2.4, to provide analytics and measure marketing effectiveness;
  • the information needed to deliver push notifications to Android devices.
• Clerk — our authentication and identity provider.
  • It stores your sign-in credentials and identity (email, name, profile picture).
  • It processes your sign-in, including Google and Apple sign-in, and sends sign-in and verification codes by email.
  • Your IP address is sent to Clerk as part of authentication.
• RevenueCat, with the Apple App Store and Google Play — our subscriptions provider. It processes purchases and sends us subscription-status events. Your account identifier and store purchase data are shared to manage your entitlement.
• Resend — our email delivery provider. It receives your email address, the content of the emails we send you, and delivery events.
• Speech-recognition providers — receive recitation audio only, as described in Section 2.5. Which provider handles a recitation depends on the feature and on which engines are active. They can include:
  • Mistral AI;
  • ElevenLabs;
  • Soniox;
  • OpenRouter, and the providers it routes to that host open Whisper models;
  • Groq;
  • Speechmatics;
  • AssemblyAI;
  • Modal, which hosts an open speech model that we operate.
• Sentry — our crash- and error-reporting provider.
  • It receives crash and error reports to help us keep the Service stable: error details, stack traces, device and app metadata, and limited performance data.
  • In some error cases an identifier may appear in an error message.
• Expo (push notification service and app updates) — receives:
  • your push token and the content of the notifications we send, so it can deliver them to your device;
  • technical requests when the app checks for updates.
• Anthropic — an artificial-intelligence provider, used in two ways:
  • Drafting study material. It helps our reviewers draft quiz questions, distractors, word hints and study notes from Qur'anic corpus text. No personal data or quiz answers are sent for this, and the app is designed to block personal data from these requests. AI never writes or changes the Qur'anic text itself.
  • Helping our team with support. It helps our team review support requests, content reports and recitation-grade reports, and draft suggested replies and actions. For this it may process the text of those requests and reports, including what the speech-recognition services heard. It is instructed not to read names or email addresses, and a member of our team approves each suggestion before anything is sent to you or changed.
• Replit (cloud hosting, running on Google Cloud) and Neon (database) — where the Service runs and your data is stored.

4.2 Our team

Authorised staff can access account data when it is needed to provide support, review reports or keep the Service safe.

• Scholars. Scholars on our team review content reports and recitation reports, including report recordings.
• "View as" for support. To investigate a problem, an authorised administrator can view the app as you see it.
  • The access is read-only and time-limited (at most 60 minutes).
  • Each use is logged.
  • The administrator cannot change your data or act as you.
• Second factor and audit log. Administrative access needs a second sign-in factor, and administrative actions are recorded in an audit log.

4.3 Other users

Your memorization data, answers and recordings are not shown to other users. If you post an idea or comment on the in-app ideas board, its text, votes and comments can be seen by other users once published. Your name is not shown with it.

4.4 Other disclosures

We may also disclose personal data:

• if required by law;
• to enforce our Terms;
• to protect the rights, safety and security of our users, the public or the Service;
• in connection with a corporate transaction such as a merger or acquisition, subject to this policy.

5. International Transfers

Our providers may process and store data in countries other than Jordan, including the United States and countries of the European Union, where several of them are based. Where data is transferred internationally, we rely on appropriate safeguards required by applicable law, such as standard contractual clauses or equivalent measures.

6. Data Retention

We keep personal data for as long as your Account is active and as needed to provide the Service. After that, we keep it only as required for the purposes described in this policy or by law, and then delete it.

• Account deletion. You can delete your Account in the app (Settings → Account).
  • Scheduled deletion. Deletion is scheduled for 30 days later, so you can change your mind. We may email you a reminder during that time. After 30 days, your Account and the data linked to it are permanently deleted. This includes your profile, marks, progress, quiz history, recitation results, preferences, subscription records, analytics identifier and device sessions.
  • Immediate deletion. In some cases, such as a suspended account, the app offers immediate deletion.
  • Deleting without the app. You can also email support@thabat.net to ask us to delete your Account or your data.
• What may remain after deletion, with your Account link removed:
  • support requests you sent, which keep the email address you wrote from, the message and the attached diagnostic log, where we have a legitimate or legal reason to keep them;
  • recitation-grade reports, until their 90-day period ends (recordings 30 days);
  • ideas and comments you posted on the ideas board;
  • your email address on our "do not email" list, if it is there (Section 2.6);
  • records that someone joined using your referral code;
  • administrative records of moderation actions;
  • backups, until they are overwritten in the normal cycle.
• Recordings on your phone stay on your phone until you delete them or the app.
• Subscriptions. If you cancel a store Subscription, remember that you must do so in the App Store or Google Play. Deleting the app or your Account does not cancel it.
• Analytics data.
  • It is kept under the Google Analytics property's retention settings (Section 2.4) and Google's retention policies, and aggregate reports may be kept longer.
  • Turning off sharing, signing out or deleting the app does not automatically erase historical analytics.
  • Contact us using Section 12 about analytics data associated with your account.

7. Security

We take reasonable technical and organizational measures to protect your data, including:

• sending data over encrypted connections (HTTPS);
• storing your sign-in token in your device's secure storage;
• limiting administrative access to authorized staff through role-based controls and a second sign-in factor;
• keeping an audit log of administrative actions;
• removing authentication tokens from server logs;
• designing our AI features so that personal data is not sent to the AI provider when drafting study material.

Your password is handled by our authentication provider, and we do not store it.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

8. Your Rights and How to Exercise Them

Depending on where you live, you may have the right to:

• access, correct or delete your personal data;
• restrict or object to its processing;
• withdraw consent;
• data portability.

You can exercise several of these directly in the app:

• View and edit: view and update your display name, bio and preferences in the app's Settings.
• Notifications and emails: turn study reminders, streak warnings, announcements and practice emails on or off in Settings, or unsubscribe from any practice or news email.
• Usage analytics: turn off "Share usage analytics" in Settings → Account & data → Data & privacy, on each device, to stop future collection on that device. The switch does not delete existing analytics, but you may contact us about access or deletion.
• Microphone: you can withdraw microphone permission in your device settings at any time. The recitation features then stop working, but the rest of the app does not.
• Recordings on your phone: delete them in Settings.
• Delete your Account: in Settings, or by contacting us.
• Other requests (including a copy of your data, correction of other data, portability or objection): contact us using Section 12, and we will respond as required by applicable law.

Selling and sharing

• We do not sell your personal data.
• Some laws treat advertising measurement as "sharing", including the Android campaign measurement described in Section 2.4. You can stop it by turning off "Share usage analytics", or by asking us.

We will not discriminate against you for exercising your rights.

9. Children's Data

The Service is intended for users aged 13 and over, and registration by anyone under 13 is not permitted. Older app versions asked for birth dates. Newer registrations rely on a statement that the user is 13 or older, and do not verify age. A default adult account category must not be treated as proof that a person is an adult.

Users between 13 and 17 (or under the age of majority in their jurisdiction) should use the Service only with the consent and involvement of a parent or legal guardian. Parental involvement matters because the Service may process data that can be sensitive for a minor, including:

• date of birth;
• voice recordings;
• health-related and religious-observance streak reasons;
• the fact of practising Qur'an memorization.

If you believe a child under 13 has given us personal data, contact us at support@thabat.net and we will delete it.

10. Push Notifications and Your Choices

If you enable notifications, we send you study reminders, streak warnings, reward and event notices, and occasional announcements.

• Limits. We limit how many you receive each day, and avoid night hours unless you chose the time yourself.
• In-app inbox. Notifications also appear in the app's inbox.
• Controls. You can control each category in the app's Settings and in your device's system settings. Announcements (marketing-style messages) can be turned off separately from functional reminders.
• Your push token. Turning off notifications does not delete the push token already stored. It is removed when you sign out on the device, or when the delivery service reports the token is no longer valid.

11. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the effective date and give notice through the Service or by other reasonable means. Please review it periodically.

12. Contact and Complaints

If you have questions or requests about this policy or your personal data, contact us at support@thabat.net or through the in-app support form. You also have the right to lodge a complaint with the competent personal-data-protection authority in Jordan or in your country of residence.