Tehfīz is used by children. This page explains what that means for the information we hold — and, more importantly, what we have deliberately arranged not to hold.
Last updated: 4 October 2026
We do not know your students' names. There is no name field in our
database. A student is identified by a code we generate, like HUDHUD-S6PX.
The name attached to that code is stored in the teacher's own browser and is never sent
to us. A teacher who turns on name sync also keeps a copy in a private folder in their
own Google Drive; that copy goes from their browser to their Drive, not through us.
This is a deliberate design decision, not an oversight, and it shapes everything below. Because we never receive a child's name, we cannot disclose it, lose it in a breach, or be compelled to hand it over. We accepted a real cost for this: a teacher who clears their browser data loses their name list and has to rebuild it from their exported backup — or, if they have turned on name sync, from their own Google Drive.
We also do not run advertising, do not sell or share data with anyone, and do not use analytics or tracking of any kind. There are no third-party scripts on the apps beyond Google's sign-in for teachers and the Quran text and fonts described below.
Teachers sign in with Google. We never see or store a password.
| What | Why |
|---|---|
| Email address | Identifies your account and is how we contact you |
| Name from your Google profile | Shown so you can recognise your own account |
| Account status and dates | Whether your account is approved, and when it was last used |
| Name sync setting | Whether you have turned name sync on, and when that last changed. A yes/no only — never any names |
We email you when your account is approved, and we email ourselves when someone new signs up. Those are the only automatic emails we send, and they contain nothing but the teacher's own name and email address.
To sign you in, we request only your email address and basic profile from Google. We do not request access to your Gmail, contacts, calendar or files.
If you turn on name sync in the Students panel, Tehfīz asks Google for one
more permission: to store its own data in a private, hidden app folder in your Google
Drive (Google calls this permission drive.appdata). Tehfīz keeps one small file
there — your students' codes and the names you gave them — so they appear on every device
you sign in on.
Tehfīz's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data from your Drive is used only to show your own students' names back to you in Tehfīz; it is not used for advertising, not sold, not transferred to anyone, and not read by people.
Students never create an account and never give us an email address. They are given a code by their teacher and choose a 4-digit PIN.
| What | Notes |
|---|---|
| A generated code | e.g. HUDHUD-S6PX. Not derived from anything about the student |
| The PIN, hashed | Stored so it cannot be reversed, and additionally protected by a key held outside the database. We cannot read a student's PIN, and neither could anyone who obtained a copy of the database alone |
| Recitation sessions | Which verses were recited, which words were mistaken, the type of mistake, how much help the teacher gave, and any notes the teacher wrote |
| Devices signed in | Stored as a one-way fingerprint, so that resetting a student's PIN signs out every device they use. The actual sign-in token is never stored |
What is deliberately absent: no name, no age, no school, no email address, no phone number, no photograph, no location, and no IP address logging by us.
Teachers: the notes you attach to a mistake are free text, and they are stored on our servers along with the session. Please do not write a student's name, their school, or anything else that identifies them in a note. Everything else in the design keeps children unidentifiable; a name typed into a note undoes that.
We cannot detect or prevent this, which is why we ask. Notes are intended for teaching observations — "watch the madd", "rushed the ending" — not for identification.
A teacher can permanently delete any session from within the app. When they do, the recitation record is erased from our storage immediately.
What is erased: the recitation itself, the notes, the record of which passage was covered, when, how many mistakes there were and how much help was given, and the index described under Statistics.
A small marker is kept — an identifier and a timestamp, with no recitation content. It is what stops the same session being re-created by a device that had not yet synced, and it holds nothing about what was recited.
To delete an entire account, or a specific student's records, email contact@tehfiz.com. Quote the student's code rather than their name — we have no names to match against, so a request naming a child is one we cannot act on. We aim to complete deletion requests within 30 days.
Parents and guardians may make this request as well as teachers.
Separately from the apps, we run a few short forms — for people looking for a teacher, for teachers looking for students, and for arranging sessions directly. These are Google Forms, and what you send through them goes to us by email — it is not stored in the database that holds recitation sessions, and it is never published anywhere.
One of those forms, on the dhor page, is for booking a session directly with Qazi Emaduddin, who runs Tehfīz and also teaches. It asks for your name, your age, where you are, and how to reach you, so that a suitable time can be arranged. It is for adults booking for themselves.
It is handled exactly like the enquiry forms above: it comes to us by email, it is not stored in the database that holds recitation sessions, it is never published, and you can ask us to delete it at any time.
Worth stating plainly: Tehfīz is run by someone who also teaches. If you send an enquiry through the forms above, you may be introduced to him, and he will say so. You are under no obligation, and enquiries he is not suited to are passed on.
We do not verify anyone's qualifications and we do not vouch for teachers or families. An introduction is not a recommendation. Please make your own checks before arranging lessons.
Alongside each session we keep a short index of it: which pages of the mushaf were covered, and how many mistakes fell on each, by type and by how much help was given. It is derived from the session itself and tells us nothing the session did not already contain — it exists so we can see which passages are hardest across everyone using Tehfīz, which is what lets the tools improve.
Three companies process data on our behalf, and no one else:
The apps also load Quran text and fonts from quran.com and the King Fahd
Complex, which involves your browser requesting those files. No information about you or
your students is sent with those requests.
We do not sell data, do not share it with advertisers, and will not transfer it to anyone else without telling you.
Tehfīz costs nothing to use and comes with no guarantee of availability, accuracy or fitness for any particular purpose. It is a teaching aid, not a system of record. Keep your own copies of anything you would be sorry to lose — both apps can export sessions as files at any time, and we recommend using that.
If you use Tehfīz with students, you decide what is recorded about them and you are responsible for having the appropriate permission from them or their guardians. We provide the tool; the teaching relationship is yours. You are also responsible for keeping student codes and your own account secure.
New teacher accounts are reviewed before they can send sessions to students. We may decline or suspend an account, particularly where we believe a child may be at risk. Suspension keeps your records intact.
If we change this page in a way that affects what we store or who can see it, we will say so on the site before the change takes effect.
Questions, deletion requests, or concerns about a child's safety: contact@tehfiz.com.
We read everything sent to that address and aim to reply within a few days.