NoorHaven

Privacy Policy

Effective and last updated: 1 October 2026
The short version: your worship is between you and Allah. NoorHaven keeps your prayer tracking, Quran progress, and settings on your device. There are no ads and no data sale, and nothing about your worship leaves your phone unless you explicitly turn it on. An account is optional and is only needed if you want your data on more than one device — and when you do, it is encrypted on your phone before it is sent, with a key we do not have.

NoorHaven is an independent product and is not an official app of Quran Foundation, Quran.com, or QuranReflect. It uses Quran Foundation’s Content APIs in accordance with the Quran Foundation Developer Terms. Quran.com and QuranReflect are part of the wider Quran Foundation ecosystem; NoorHaven currently uses content endpoints only and does not access your Quran.com or QuranReflect account, bookmarks, notes, or posts.

Sensitive religious information

Prayer history, Qur’an reading progress, adhkar activity, and related records can reveal religious beliefs and practice. NoorHaven treats this as sensitive data. It remains on your device by default. It is included in encrypted sync only after you make a separate, explicit choice on the Sync screen. Family-group information is shared only when you separately create or join a group.

What stays on your device

Everything the app knows about your worship is stored locally on your phone. Unless you turn on Sync, it is stored nowhere else:

Prayer times are calculated on your device — your location is never sent to us. Unless you turn on Sync (below), none of the data in this list leaves your phone at all.

Sync across devices — optional, and end-to-end encrypted

NoorHaven works completely without an account. If you want the same prayer history, bookmarks and settings on a second device, you can create one with an email address and a password. Nothing about worship requires it.

Signing in with Google. Where the app offers it, you can use your Google account instead of typing an email address. Google confirms who you are to our sign-in provider (Firebase Authentication, which is also Google), and passes along the name, email address and profile-picture link on your Google account; the sign-in provider keeps them on your account record. The app itself uses only the email address, and never shows or uploads a picture. You still choose a separate sync password, and it is used exactly as described below — Google never receives it, and your Google login cannot decrypt your synced data.

Signing in with Apple. On iPhone and iPad you can use your Apple ID instead of typing an email address. The app asks Apple for exactly two things — your name and your email address — and for nothing else. Apple confirms who you are to the same sign-in provider as above (Firebase Authentication, which is Google), and that provider keeps what Apple returns on your account record. The app itself uses only the email address. You still choose a separate sync password, used exactly as described below: Apple never receives it, so your Apple ID cannot decrypt your synced data. If you signed in with Apple and never set a sync password, Settings → Sync → Delete account asks Apple to confirm it is you before anything is deleted — with no password on the account, that confirmation is the only proof there is.

If you use Hide My Email. Apple lets you keep your real address to yourself. Do that and the address we hold is not your real one: it is a relay address Apple minted for NoorHaven alone, ending @privaterelay.appleid.com, which Apple forwards to the inbox you kept private. We never learn the address behind it, and we cannot ask Apple who it belongs to. A relay address is a complete account, not a limited one: it identifies your account, it salts your sync password (below), and everything in the app works the same way. Your sync password is still yours alone either way — Apple cannot decrypt your synced data whether the address is a relay or your own.

Two things are worth saying plainly rather than leaving you to discover them. If you ask to manage a mosque, the address we hold is the one that goes on the request — so with Hide My Email that is the relay address, and a reviewer replying to you reaches you through Apple's forwarding rather than directly. That is the same address used for everything else on your account; we do not ask for a different one. And your Apple ID's email must be one Apple has confirmed, which it is for both a relay address and a real one; if your account ever arrives without that confirmation the app will tell you at the sign-in button rather than letting you in and then refusing everything afterwards.

The email address on an Apple or Google account cannot be changed from inside the app. Settings → Sync refuses it, and the refusal is deliberate rather than missing. The address belongs to the provider, which goes on asserting it whatever we did at our end; it is also what your password is stretched with, so moving it means re-sealing your encrypted data under a new key derived from the new address. With Hide My Email there is not even an inbox to move it to. A Google address is changed with Google. A relay address is managed in Apple’s own settings for NoorHaven, on your Apple ID, not here — and because the key is derived from the address, data saved under the old address is not readable under a new one.

How your password is used. Your password is never sent to us. On your device it is stretched with scrypt and split into two independent keys:

What we can see. On our servers your synced data is a block of ciphertext. We can see that a document exists, which account it belongs to, when it was last written, and a random opaque id for the device that wrote it — that id is generated on your phone and describes nothing about it. We cannot read what is in the block itself. This also means that if you forget your password we cannot recover your synced data — there is no back door for us to use on your behalf.

What is synced. Prayer history, Quran progress and bookmarks, adhkar and tasbih counts, Ramadan and checklist progress, zakat records, and your settings — all inside the encrypted block.

What is never synced. The private notes in the women’s circle never leave the device under any circumstances — the app promises that where they are written, and sync does not change it. Your city, its coordinates and your timezone; downloaded audio files; and supporter status also stay on the device they belong to. Location is deliberately per-device — prayer times should describe where that device actually is, not where another one was.

Who processes it. Sync runs on Firebase, which is Google. Two Firebase services are involved, and they are deliberately described separately, because they are not in the same place:

Turning it off. Sign out on a device and the encryption key is erased from memory and from the keystore immediately; your data stays on that device. Settings → Sync → Delete account deletes the account and the encrypted block belonging to it, from inside the app, without contacting us — see “Deleting your account” below for exactly what that removes and the small records it deliberately leaves behind. If you have joined a family group, read the note on leaving below too: a shared khatm is the one thing that does not simply vanish with your account.

Family groups — shared with people, not with us

A family group lets a household read a Qur’an together: the thirty juz are laid out, everyone takes the parts they want, and a parent can ask someone to read a particular surah. It is off unless you create or join a group, and it needs a sync account because it moves data between people.

This is the one place NoorHaven shares anything. Everywhere else in the app, “private” means nobody but you. Here it means nobody but your group — which is a real difference, and worth reading the rest of this section for.

Group contents are stored readably, unlike your own synced data. Your personal synced data is encrypted on your device and we cannot read it. A family group is different: so that the group can have an owner, remove members and change its invite code with the server enforcing it, a group’s contents are stored as ordinary data that the service can read. That means the group’s name, its members’ display names, which juz (or half juz) each member has claimed and finished, any requests to read a surah or memorise some of its ayat, a finish date and intention if the owner sets them, and a record of the khatms the group has finished. Please choose a display name you are comfortable with — it need not be your real name.

The invite code admits people. Anyone holding a group’s code can join it, so give it only to people you mean to let in. The person who created the group owns it and can change the code at any time — the old one then stops working for good and is never given to another group, and nobody already in the group has to do anything — and can remove a member, after which that account can no longer see the group or rejoin it. Removing a member also changes the code, because the person removed knew the old one; share the new one with anyone who still has to join. The owner can hand the group to another member, and cannot leave without doing so: when the owner leaves, the group passes to the longest-standing member automatically. Only the owner starts the next khatm, and only the owner can clear every request in the group (“Clear all requests”) if it fills up. The owner can also mark a juz unread again, or start the current khatm over, for the whole group — the way to undo reading marked that nobody did. If the owner has not opened the group for more than 60 days, any member can take it over, so that a household is not stuck with an owner who has stopped using the app; the previous owner stays a member, and the new owner can remove them like anyone else.

What the group can see. The display name each member typed, which juz each has claimed and finished, any reading or memorisation requests, the khatm’s finish date and intention, past khatms and who read in them, and who is currently in the group. Membership is tied to your account, so the group appears on every device where you sign in.

Sharing a finished khatm. The picture of a finished khatm is drawn on your device and goes only where you send it from your phone’s share sheet. It is not uploaded to us.

What we store. For each group: its owner, when the owner’s app last wrote to it (the 60 days above are counted from this), its current invite code, which accounts are in it and which were removed, which khatm it is on, how many times its owner has cleared the requests, and the shared khatm described above, and when the owner last marked each juz unread or cleared the khatm’s plan (a time for each, naming nobody). Each member’s display name is also kept on their own entry in the group’s member list, which only they can change. That entry also records which juz they marked read in the current khatm and which intention they last wrote, so that nobody else can mark reading or write an intention in their name: reading marked in the name of someone in the group counts only when their own entry says so. The intention is recorded there by its khatm, its version and a short fingerprint of its words, never the words themselves, so that nobody can change the words under their name either. Only what the member did on their own phone goes on their entry: until it has, that phone keeps a note of the juz they marked read and the intention they wrote there, on the phone only, and the note is removed once it is sent or when the phone leaves the group. It goes with the entry when they leave. When the owner removes someone, the display name that person had given themselves is kept beside the removal, so the owner can still see whom undoing it would let back in; it is erased when the removal is undone, when the group is closed, or when the removed person deletes their NoorHaven account. A code the group no longer uses is kept only as a pointer to the group’s random id, so that it can never lead anyone to a different group. Under your own account: which groups it belongs to and when it joined each one. We use this only to run the feature; we do not analyse it or share it with anyone.

The counter that caps group creation, and what it honestly is. One small record per account holds two numbers: how many groups this account has created, and how many it belongs to right now. It exists only to cap both, so that one account cannot make groups without limit. Firebase gives us no server of our own to keep it on, so the account keeps its own: the security rules refuse any change to those numbers that is not tied to a genuine join or leave, and refuse ever to lower the creation count. That makes it hard to forge, not impossible to forge, and we would rather write that down.

Leaving, and deleting your account. Leaving a group takes your account off it immediately, on every device. The shared khatm is a document the other members are still using, so the display name and progress you contributed stay in it; your entry in the member list, with the display name on it, is removed. Deleting your NoorHaven account leaves every group you are in, then removes your own synced data and your account. When the last member of a group leaves, the group is closed: its name, member list, removals (and the names kept with them) and shared khatm are erased, and all that remains is a marker that the group’s random id was used, naming nobody, so that the id can never be taken over. Its old invite codes likewise point only at that closed id. An owner can also close a group while others are still in it. Their entries in the member list, each with its display name, then cannot be read by anyone else, and are erased the next time each of those members opens the family screen, or when they delete their account.

Mosques — following one, and representing one

Following a mosque needs no account and tells us nothing. The mosque directory and each mosque’s published timetable are public, so the app reads them without signing in. Which mosque you follow is stored on your device (and in your encrypted sync block, if you use sync). No list of a mosque’s followers exists anywhere. A mosque you enter by hand stays on your devices and is never added to the directory.

Asking to manage a mosque does share details with us. A mosque representative who sends a management request gives the mosque’s name and address, their own name and role, and contact details for the mosque, together with their account’s email address. These are readable only by NoorHaven reviewers and by the account that sent the request. Reviewers use them to confirm the request, usually by contacting the mosque through its publicly listed phone number or email, and record a decision with a short note, which the account that sent the request can also read. They are stored in Google Cloud Firestore, as described above, and are not published. A request and its decision are kept until the account that sent it is deleted, as the record of that decision; an account can send up to ten requests over its life. If a request is approved, the account is recorded as a manager of that one mosque; that record is visible only to the manager and to reviewers. A timetable a manager publishes is public and carries no name.

Deleting your account — what goes, and the minimal records that stay

There is no NoorHaven server behind your account, and no cascade running somewhere out of sight: the app itself does the deleting, in this order, and stops if a step fails so that you can try again rather than be left half deleted. A test version of the app from before 30 September 2026 does these steps in an order the service no longer accepts, and cannot finish; update the app, then delete your account from the updated version.

Two minimal records are left behind on purpose: the two-number counter described under “Family groups” above, and the deletion marker containing one server timestamp. The counter is left because an app that could delete it could reset its own limit on creating groups simply by deleting its account and carrying on. What survives is two integers filed under an account id Firebase never issues to anyone again. It names no group, no person, no email address and no device, and nothing can be read back out of it about you. The marker prevents a previously signed-in device from writing the data back after deletion. A mosque listing and a timetable you published stay, because they belong to the mosque and name no one. Your personal encrypted block, mosque requests and memberships are removed. A family group’s shared khatm—including contributions you made before leaving—stays with the members still using it, as explained above. We say these exceptions plainly rather than claim the deletion is total.

Location

You can pick your city from a built-in offline list, in which case no location request leaves your phone at all. If you choose “Use my location” or search for a city that is not in the offline list, your device’s operating system resolves it using the platform’s standard location and geocoding services (Google on Android, Apple on iOS), subject to their own policies. The resulting city, coordinates, and timezone are then stored only on your device.

Network requests the app does make

Security, retention, and international transfers

Network connections use HTTPS/TLS. Synced worship data is encrypted on your device before upload; family-group content is not (see “Family groups”) and is readable only by the group’s members and the service. Service access is restricted to the minimum required. Quran Foundation credentials remain on NoorHaven’s server and are never embedded in the app. We maintain an incident response process, including reporting an actual or suspected API-related unauthorised access, security breach, or data exposure to Quran Foundation within 24 hours.

Local data remains until you delete it or uninstall the app. Live sync account data is deleted when you use Delete account, as set out above. There is no NoorHaven backup of it to age out afterwards. Scheduled Firestore backups and point-in-time recovery are paid Firebase features and are not enabled on this project, so we keep no recoverable copy of a deleted document and could not restore one if we were asked to. What happens after that is Google’s own internal timeline for purging data deleted from its services — theirs, not ours, and described in their documentation rather than here. We are not going to quote you a number for it that we have no way to enforce. Purchase records may be retained by Apple, Google, and RevenueCat as required for receipts, fraud prevention, tax, and legal compliance under their own policies.

Some processors may handle technical or account data outside your country. Where required, transfers from the EEA, UK, or Switzerland use lawful safeguards such as adequacy decisions or Standard Contractual Clauses. The linked processor policies above describe their locations and safeguards.

Notifications

Adhan and reminder notifications are scheduled locally on your phone. There is no push-notification server and no notification token is sent anywhere.

Your controls

Because data lives on your device, uninstalling the app also deletes it. If you use Sync, delete your account first — uninstalling removes the local copy but not the encrypted one on the server.

What we never do

Children

NoorHaven’s local, account-free features are available to families, and collect no personal data by default. Sync accounts are not intended for children under 13, or under the higher minimum age required where they live. The account screen requires the person creating an account to confirm that they are old enough to consent. A parent or guardian should manage any use by a younger child.

Changes to this policy

If a future feature changes what data is handled (for example, optional encrypted backup), this policy will be updated first and the change will be opt-in. The “Last updated” date above always reflects the current version.

Contact

Questions or concerns: support.noorhaven@foteraa.com