Privacy
Privacy policy
Hasanah needs no account (one is optional, for those who want it) and sells no one's data. This is what the website and the app collect, and why.
The Hasanah app (Android and Android TV)
The app collects no personal data and has no analytics or advertising. Your settings (language, font, theme and so on) and the surahs and pages you have read are kept on your device only.
It connects to Hasanah’s server to learn which ayah is being recited and to fetch the Quran text and translations, to Aloula’s streaming servers for the video, and to the Quran Foundation for the mushaf’s page fonts. Those servers receive what any website receives from a visitor, such as an IP address, in order to serve it.
The site’s own visit counter
The website counts its visits itself, without cookies: the browser keeps a random id, and the server stores only a salted hash of it that is joined with nothing else, except your account if you sign in to one. IP addresses are not stored. It records the page and how long it was on screen, the kind of device and browser, the country inferred from the time zone, and the name of the referring site. Records are deleted after 400 days. A browser that asks not to be tracked (Do Not Track or Global Privacy Control) is not counted at all.
In the live reader your settings are kept in your browser, and a summary of them (font, theme and the like) is sent under the same hashed id, so we can see what readers use.
Google’s statistics
The website also uses Google Analytics, which sets cookies and processes visit data under Google’s privacy policy. The app does not use it.
A Hasanah account (optional)
If you create an account, Hasanah keeps your email address, a name if you give one, your language, when the account was made, whether the email is confirmed, and your Hasanah Plus subscription, if any. Signing in (with email and password, or with Google) is handled by Google’s Firebase Authentication, which stores the password hashed and sends the emails that confirm an address or reset a password, under Google’s privacy policy. The site keeps you signed in with one strictly necessary cookie. While you are signed in, your visits and use of the tools (what the visit counter below records) are linked to your account, so the people who run Hasanah can see how it is used and help you with your account and subscription; nothing is linked if your browser asks not to be tracked. This is never used for advertising or shared with anyone. If you use the Hifz trainer while signed in, its review schedule, recitation history and profile are kept with your account so they follow you to other devices. You can delete your account at any time from the account page; it is then removed from Hasanah and from Firebase.
The Hasanah Plus subscription
Payments go through Stripe’s checkout page. Hasanah Plus is sold by Amiro, the business behind Hasanah (see the legal notice); plans bought before 29 October 2026 were sold through Link, Stripe’s service, which keeps their payment details. Card and PayPal details are entered on Stripe’s page and never reach Hasanah’s server. Stripe processes the payment under its privacy policy. A “Plus key” (the subscription’s id and its expiry, signed) is kept in your browser so the site knows you subscribe. After checkout, and when you ask to manage your subscription by email, Hasanah emails the address you paid with; for that request it keeps the address with a one-time link for an hour (only a hash of the link), and Stripe tells the server when a subscription is cancelled, renewed, refunded or disputed so Plus stays correct.
Reciting aloud in the Hifz trainer
When you press “Recite aloud” in the Hifz trainer, or “Follow my recitation” in the Quran reader, the microphone is opened and your voice is analysed inside your browser, on your own device. Hasanah does not record the sound, keep it, or send it to its server, and the microphone is closed when you finish or leave the page.
The listener itself (a speech model of about 68 MB, or 25 MB on a small phone) is downloaded once from tilawa.dev, the open-source project that makes it, and then kept by your browser. That site sees your IP address, as it would for any file on the web; nothing about you or your recitation is sent to it. The result of a recitation (the passage, the grade and the words you slipped on) stays in your browser, or with your account if you are signed in. Only a summary in numbers reaches the visit counter, under the same hashed id: the passage, how many words were recited and heard right, how many slips of each kind, the grade and score, and how long it took. The words themselves and the sound are never sent. The people who run Hasanah see these numbers, and the progress of learners who are signed in, to learn how the memoriser is used and improve it.
While “Check tajweed” is on (it is, unless you turn it off in the Session tab), a lesson’s sound is also heard by a second listener inside your browser: TajweedFormer, made by Quran Lab. Its model (about 56 MB) is downloaded once from Quran Lab, which sees your IP address as any site would. Its software checks Hasanah’s key with Quran Lab and sends it anonymous counts of use (such as how many recitations and minutes in a day: no sound, no text, nothing that identifies you). Quran Lab may also ask you, on a sheet of its own, whether you want to share recordings of your recitation to improve the model. Recordings are sent to Quran Lab only if you agree there; you can turn that off, and delete what you shared, under You in the Memorise panel. With the tajweed check off, none of this is loaded. So that reciting starts without a wait, both listeners are fetched and started when you open Memorise mode. On a mobile-data or data-saving connection, and on a phone whose browser does not say what it is connected to, they are fetched only when you go to press “Recite aloud” (as you touch it, hover over it or reach it with the keyboard). The microphone is not opened until you press it.
Follow a recitation and Studio
When you choose an audio file or a link in Follow a recitation or Studio, the audio is sent to our server to be recognised and then discarded; neither the audio nor the result is kept on the server, and the result stays in your browser.
If you report a mistake in Studio, the sound of that part (up to ten minutes; the sound only, never the picture or your file’s name) and the ayat Studio showed over it go with the report, unless you untick it before sending. It is kept on Hasanah’s server to improve how the ayat are found and timed, heard only by the Hasanah team, and deleted after a year.
When you listen to one of the famous reciters on a surah page, or take their ayat into Studio, the audio is fetched straight from the site that publishes it (sources), which sees your IP address as it would for any audio on the web. Nothing else is sent to it.
Rendering in the cloud
When you choose “Render in the cloud” in Studio, your project is uploaded: the recordings and pictures in it, the ayat and their timings, and how the video looks. It goes straight from your browser to a storage bucket of ours on Google Cloud in Belgium (europe-west1), over an encrypted connection and a link that works only for that upload.
The video is made there by our own program on Google Cloud Run, in the same region, which opens Studio with your project and saves the result back to the bucket. Recordings that need it are first converted to a common format. No one at Hasanah watches or listens to your project or your video. They are used to make the video you asked for and, only when you explicitly request it, share that finished video through a connected account.
The project and the video are deleted from the bucket automatically two days after they were uploaded. Until then the video can be downloaded only through a signed link given to you, which stops working after six hours (a new one is given each time you open Studio or your profile).
On Hasanah’s server we keep a short record of each render for 90 days: the name you gave the video, its length and settings, its size, when it was made and how long it took, whether it worked, and the Hasanah Plus subscription it counted against (to count the month’s minutes). It holds none of the recordings, pictures or video. Google processes the files for us as our cloud provider, under its data processing terms.
Questions
For any question about privacy, or to ask for something to be deleted: [email protected]. Last updated 22 October 2026.
Sharing a Studio video
Connecting TikTok is optional. After you authorize it, Hasanah keeps your TikTok account identifier and encrypted access and refresh tokens on its server, linked to your Hasanah account. The account name and current privacy choices, interaction permissions and video duration limit are requested to display the posting page. Hasanah never asks for your TikTok password and never returns these tokens to your browser.
After you preview a completed Studio cloud video, choose its caption, privacy, disclosures and interactions, and explicitly authorize the post, Hasanah reads that video and sends it with those choices to TikTok. A temporary copy passes through the server and is removed when the transfer attempt ends. TikTok handles the video under its privacy policy.
Hasanah keeps a posting record for up to 90 days: your Hasanah account, TikTok account identifier, Studio render identifier, submission times, posting identifiers and success or error status. This prevents accidental duplicate submissions. Disconnecting on the sharing page removes the local connection tokens and requests revocation at TikTok; the posting record remains until it expires. You can also revoke Hasanah in TikTok's app permissions. Deleting your Hasanah account removes its local connection and sharing records; it does not delete posts from TikTok.