Privacy

Privacy Policy

Last updated: October 14, 2026

About the app

Ummahti is a Quran reader that works entirely on your device. It does not require an account. It does not collect usage analytics or send crash reports unless you explicitly turn optional diagnostics on, and everything the app is for keeps working if you say no.

Your bookmarks, reading position, reading/search history, Hifz practice, private Hifz Revision queue, and Ayah-on-Unlock progress never leave your device as Ummahti telemetry or an account profile.

1. What we collect by default

There is no account, no profile, no advertising identifier, and no usage tracking unless you choose to enable it.

Firebase Remote Config makes a background request for feature flags when the app starts. Google receives technical app/device identifiers needed to answer that request. It does not receive your reading activity, bookmarks, reading position, Hifz practice or private Revision history, and the reader never waits for the request. This connection is separate from the optional diagnostics choice below.

The app also makes small background HTTPS requests to Ummahti's public static host for independently signed featured-video state and version-support policy. That host can observe ordinary connection metadata such as an IP address. The request contains no reading activity, bookmark, reflection, history or account data. A still-valid verified response may be cached on the device.

2. What stays on your device

The app stores the following locally. Ummahti does not upload this local store as a profile. When you request a network feature, the relevant edition, reciter or verse number can form part of that request as listed in section 4:

  • Your reading position — the last surah, ayah and page you were on
  • Your bookmarks
  • Your private reflections, if you write any — the text you wrote, which ayah you attached it to, any personal labels you chose, and when you first wrote it and last edited it
  • Your reading and search history, if you leave history recording on
  • Your Hifz practice history — which ayahs you practised and the last local calendar day you completed each guided session
  • Your private Hifz Revision queue — exact ayahs, ratings, deterministic due schedule, review timestamps, lapse count, event history and daily target
  • Your My Hifz record: the surahs, passages and ayahs you have recorded, and whether each is learning, memorised or needs revision
  • Your Ayah on Unlock progress, if you use that feature — which ayah comes next, how many you have been shown, how many times you have completed the Qur'an, the time the last verse was shown to you, and whether you chose a Separate or Shared reading position
  • Which Ummahti Guide topics you have opened, most recent first, up to the last 12. Only the topic's own identifier is kept, never what you typed into Guide's search, and it is read only to reorder Guide's own suggestions on this device. Guide's disclaimer sheet has a Reset suggestions action that clears it at once.
  • Your settings — theme, font size, Arabic script, reading mode, Home card order and sizes, chosen reciter, chosen translation and transliteration
  • Your reminder choices, active Guided Sets, timing/cadence, selected reflection themes, quiet hours, temporary pause and delivery/progress counters, plus your local Hijri date adjustment
  • Quran text, and any translations, transliterations, tafsir or hadith you have loaded
  • Small flags recording whether you have seen certain one-time hints

The History screen lets you stop recording future reading/search history, remove one history entry, clear one trail, or use Clear everything to remove both history trails, bookmarks, and your last-read position. That last action does not clear Hifz practice, Hifz Revision, Ayah-on-Unlock progress, reminders, settings, cached content, diagnostics consent, or saved gallery images. Ayah on Unlock has its own confirmed Start Over action. It affects only the Unlock journey; if its position was Shared, the journeys become Separate first so Main Last Read is not silently moved. Reminders has a clear-all action that turns all reminders off. Hifz Revision ayahs can be removed from Hifz → Revise, with exact-count confirmation and Undo, without changing Quran text or other private data.

Android Settings → Apps → Ummahti → Clear data, or uninstalling the app, normally removes app-private data. Images you explicitly saved to your gallery are public device files and must be deleted from Gallery or your files app.

We treat your reading position, bookmarks, private reflections, Hifz practice, private Hifz Revision history, reminder configuration and Ayah on Unlock progress as sensitive. In a Quran app these reveal religious practice, which is a protected category of personal data under the GDPR and similar laws. That is why they are never transmitted, never attached to analytics, and never included in crash reports.

Your private reflections

You can attach one private written reflection to any ayah. It is yours, it stays on your device, and nothing else in the app or outside it reads it.

  • It is never uploaded, never shared automatically, and never sent anywhere.
  • It is never used to generate, rewrite, interpret or categorise anything, and no AI is involved at any point.
  • The fact that you wrote one, which verse it is on, and what it says are all absent from analytics, from crash reports, and from the app's logs entirely.
  • It is never shown in a notification.
  • It is excluded from Android's own automatic device backup and device-to-device transfer. It travels only inside a backup you deliberately create, and the manual backup file is encrypted with a password only you hold.
  • Clearing app data or uninstalling removes it, in the ordinary Android way.

The optional labels (Remember, Reflect, Memorise, Dua, Return to this) are a way for you to organise your own writing. They are not a statement about the verse and Ummahti never presents them as one.

Ayah on Unlock, and the permission it asks for

If you switch on Ayah on Unlock, the app asks for Android's Display over other apps permission and runs a background service so it can notice when you unlock your phone and show you the next verse.

We want to be direct about this, because it is the most powerful permission Ummahti asks for and you are right to be careful with it:

  • It is off unless you turn it on. A fresh install never asks.
  • It is used for this one feature and nothing else in the app.
  • Its reading position stays separate from Main Last Read unless you explicitly choose Shared or confirm a one-time transfer. Looking, peeking, scrolling and swiping do not commit either position.
  • The app does not read your other apps, your notifications, your screen, or anything you type. The permission lets Ummahti draw, not observe.
  • The verse never appears over your lock screen — only after you have unlocked — and it never asks you to type anything.
  • It does not appear while you are on a call, and it disappears when your screen turns off.
  • Nothing about it leaves your device. No network request is made to show you a verse.
  • You can revoke the permission at any time in Android Settings, or switch the feature off in Ummahti, and everything else in the app carries on unchanged.

The permanent notification you see while it is on is required by Android. It is there so you always know the feature is running.

Recite to add, Say a reference, and the microphone

In My Hifz, Add what you know can use your voice in two ways. Recite to add lets you recite a passage you remember so Ummahti can find where it is in the Qur'an. Say a reference lets you say where a passage is, such as Surah Yusuf, ayahs 1 to 10. To hear you, both ask for the microphone.

  • Android asks only when you first tap the microphone on one of those steps. Nothing else in the app uses the microphone, and you can always type a reference or choose the passage yourself instead.
  • Recite to add listens only while its step is on screen, and keeps the screen on while it listens. It stops when you tap stop, when you pause for a few seconds, after 10 minutes at most, or as soon as you leave the app.
  • Your recitation is recognised on your phone. The sound and the words recognised stay in memory while the sheet is open and are then forgotten. They are never saved, never sent anywhere, and never included in analytics, crash reports, logs or backups.
  • Say a reference listens once, until you stop speaking or tap Stop, and stops as soon as you leave the step or the app. It uses your phone's own speech recognition, and Ummahti asks Android to recognise on the phone itself, never through a server. If your phone cannot do that for your language, Ummahti says so and you type the reference instead; it never switches to online recognition. That speech recognition is part of your phone, provided by its maker or Google under their terms, not by Ummahti.
  • If your phone can add offline speech for your language, Ummahti offers a button that asks your phone to add it. Your phone makes that download, only when you tap it, and Ummahti sends nothing with it.
  • Ummahti keeps what you said only on screen, to show what it understood, until you speak again or close the sheet. It is never saved, sent anywhere, or included in analytics, crash reports, logs or backups. Only the passage you choose is kept while the sheet is open, so it survives the app being closed by Android.
  • Nothing is added to My Hifz until you choose the ayahs and tap Save.
  • Recite to add needs a single download of about 107 MB from Ummahti's release page on GitHub, made only when you tap Set up. GitHub can observe ordinary connection metadata such as your IP address; nothing about you or your reading is sent. You can remove the download from the same step, and your My Hifz record stays as it is.
  • You can turn the microphone off for Ummahti at any time in Android Settings, and everything else carries on unchanged.

If you have Android's system backup enabled, Ummahti selectively allows cloud backup and device-to-device transfer of benign app preferences such as theme, reader display and layout settings, selected content editions, and reciter. Personal Quran-reading, religious-practice, behavioral-history, reminder, device-local diagnostics-consent, onboarding, operational, Version Policy and update state are excluded by the app's current rules. The Room content database and app cache are also excluded. The backup transport is provided and controlled by Android and Google; Ummahti does not operate it or have access to your backup.

Older versions allowed broader DataStore backup. This version cannot retroactively guarantee deletion of every historical backup held by the platform. After this version migrates local state and a subsequent backup runs, the app-owned eligibility follows the selective policy above. You can manage Android backup in your device settings.

Backup & Restore

Settings → Backup & Restore adds two optional, user-controlled ways to recover your bookmarks, private reflections, last-read position, Hifz practice or Revision progress, reminders, and reading preferences after reinstalling Ummahti or moving to a new device. Neither is on by default, and neither involves an Ummahti server — Ummahti has none.

Reminder backup includes your sets, individual choices, timing/cadence, reflection-theme selection and quiet hours. It excludes temporary Pause All, daily delivery counters and seasonal completion tallies because those may be stale or misleading on another device.

  • Automatic backup is off until you switch it on. When you do, Ummahti prepares a small copy of the data listed above and makes it eligible for Android's own backup system, exactly like the benign preferences already described above — Android decides if and when that backup actually uploads, and Ummahti cannot see or control that. Turning the toggle back off deletes the prepared copy immediately; it never touches your live data. Restoring it after a reinstall always asks you first — nothing is restored silently, and the same device/reinstall is never asked twice.
  • Manual backup creates a single encrypted file, on your explicit request, that you save wherever you choose using Android's own file picker — your device, or a cloud storage app you already use. The file is protected with a password only you know; Ummahti never stores, logs, or has access to that password, and cannot open the file itself. Restoring from a manual backup shows you what it contains before anything is changed, and always requires your confirmation.

Restoring either kind of backup never re-enables diagnostics consent on its own, and never turns on a permission-gated feature like Ayah on Unlock without the underlying Android permission still being granted.

3. What we collect only if you agree

When you first open Ummahti you are asked whether to share optional usage and crash diagnostics. The default is no. If you decline, nothing in this section happens, and no feature of the app is withheld or degraded.

If you agree, we use Google Firebase to collect:

  • Crash reports (Firebase Crashlytics) — the error, the stack trace, and device information such as model and Android version, so we can fix crashes.
  • Usage analytics (Firebase Analytics) — automatically collected app activity such as first open, sessions, time in the app and screen class, together with app version, device information, approximate location and a Firebase app-instance identifier. Ummahti does not set a user ID.

This data travels to Google Firebase over an encrypted network connection. It is stored in the Ummahti Firebase project. Authorised project members view Analytics reports and grouped crash reports in the Firebase Console; reports are not delivered directly to a personal inbox.

We do not include which verses or surahs you read, your bookmarks, your private reflections, reading position, Hifz practice or private Revision history in Analytics or Crashlytics, under either setting. Section 4 separately explains the verse number sent only when you explicitly open tafsir.

You can change your mind at any time in Settings. Crash information cached on the device while reporting is off is queued for deletion before a consent change is saved, so pre-consent reports are not deliberately submitted later.

The Android Advertising ID is explicitly disabled. Ummahti contains no advertising and does no ad tracking.

4. Connections the app makes

Even with analytics off, the app contacts these services when you use the relevant feature. The app does not send an Ummahti account profile because it has no accounts, but Firebase SDKs and every ordinary network connection can involve the technical identifiers or connection metadata described below.

| Service | When | What is sent | |---|---|---| | alquran.cloud | You choose a different translation or transliteration | The edition you chose | | quranenc.com | You choose the Rowwad English or Rachid Maach French translation, which that service publishes and alquran.cloud does not | The edition you chose and a surah number, once per surah | | Quran.com | You open commentary for a verse | The verse number | | HadeethEnc | Authentic hadith content is synced | Requested language, content categories and content IDs | | cdn.islamic.network (AlQuran Cloud audio) | You play, or choose to download, a verse-by-verse recitation that is not already on your device | The reciter edition, bitrate and global verse number in the audio file URL | | MP3Quran audio file servers (numbered serverN.mp3quran.net hosts) | You play, or choose to download, a whole-surah recitation that is not already on your device | The reciter's audio folder and the surah number in the audio file URL | | MP3Quran timing service (mp3quran.net) | A whole-surah recitation that highlights verses plays or is downloaded, and its timings are not already stored on your device | The surah number and MP3Quran's recitation ID | | Firebase Remote Config | On app start | SDK/app-device technical metadata needed by Firebase | | Ummahti public YouTube-state host | Background featured-video state check | A plain HTTPS request; the host can observe normal connection metadata such as IP address. No reading or personal Quran data is sent | | YouTube thumbnail CDN (i.ytimg.com) | When you open the Ummahti Hub while a verified featured video is shown | The validated public video ID in a fixed preview URL and ordinary connection metadata. The app may cache the image; no reading/profile data is attached | | YouTube | Only after you tap the fixed channel or a featured video | The fixed channel URL or validated video ID and ordinary connection metadata; Ummahti attaches no reading/profile data | | Official Ummahti website | Only after you tap the website row in the Ummahti ecosystem | The fixed ummahtiofficial.com root URL and ordinary connection metadata; Ummahti attaches no reading/profile data | | Ummahti public operations/update host | Background operational or update-manifest check | A plain HTTPS request; the host can observe normal connection metadata such as IP address | | Ummahti public version-policy host | Background version-support check after the local cache is resolved | A plain HTTPS request; the host can observe normal connection metadata such as IP address. No reading or personal Quran data is sent | | Release download host | Only after you choose to download a Direct-build update | A plain HTTPS download request; the host can observe normal connection metadata such as IP address | | Ummahti's release page on GitHub (github.com) | Only after you tap Set up for Recite to add | A plain HTTPS request for a fixed file; the host can observe ordinary connection metadata such as IP address. Nothing about you or your reading is sent |

One thing worth being clear about: when you open commentary, or play or download a recitation, the relevant verse or surah reference is part of the request to the selected third-party service. A recitation request fetches audio or timings; it does not upload your listening or reading history. It is not sent by Ummahti as an account profile, and the app does not attach your bookmarks, reflections, history, Hifz practice, Hifz Revision, or Ayah-on-Unlock progress. It is nevertheless a detail of what you chose to read or play.

Your use of these services is also subject to their own privacy policies.

5. What we never do

  • Sell or share your data with advertisers or data brokers
  • Show advertisements
  • Require an account to read the Quran
  • Track you across other apps or websites
  • Read your notifications, contacts, messages, call logs, or browsing history
  • Access your location
  • Collect an advertising identifier
  • Keep or send recordings of your voice

6. Children

Ummahti is suitable for all ages and does not knowingly collect personal information from anyone, including children. There is no account, no user profile, and no social feature.

7. Your rights

Because your data is stored on your own device, you control it directly:

  • See it — history is visible in the History screen; bookmarks, position, Hifz practice, Hifz Revision, reminders and settings are visible in their relevant screens
  • Delete it — use the scoped controls described in section 2, uninstall the app, or Android Settings → Apps → Ummahti → Clear data. These controls do not delete public gallery images, a third-party share target's copy, or backup/ Firebase-side data governed by those services.
  • Stop analytics — turn it off in Settings at any time

If you are in the UK, EU or another region with data protection legislation, you retain your statutory rights of access, rectification, erasure and objection. Since we hold no data that identifies you, in most cases there is nothing for us to retrieve or erase on your behalf — but contact us and we will help.

8. Data retention

Local data is kept until you delete it. Opt-in analytics and crash data are retained according to Firebase's retention settings, currently the Firebase default; crash reports are kept no longer than needed to diagnose the issue.

9. Changes to this policy

If this policy changes materially — particularly if we ever begin collecting something new — we will update the date at the top and inform you in the app before the change takes effect.

10. Contact

Email: contact@ummahtiofficial.com

Publisher: Ummahti Quran