Privacy
The short version: your recording and everything made from it are deleted 12 hours after the job finishes, there is no account, and the only addresses ever written down are the ones you hand over on purpose — a code on its way to you, or the one message you asked for — each kept until it has done that job and no longer.
यह पेज सिर्फ़ अंग्रेज़ी में उपलब्ध है।
What is stored, and for how long
- Your recording, and the subtitle files made from it. Deleted 12 hours after the job finishes, or the moment you press Delete everything now on the result page.
- The job record — its status, how long the audio was, how much GPU time it took, and the keys of the daily counters below that it was charged to — salted hashes, and the names of the shared counters, one of which names your country — so that what it reserved can be settled or given back, and so that, once it has finished, its page can tell whether the browser reading it is the one it was charged to, which is when the date goes into this browser's cookie. Deleted with the recording.
- A notification address, if you asked to be emailed. Held until that one message is sent, then removed from the record.
- A one-way hash of a verified email, if you chose to raise your daily limit. The address itself is never written down: the hash is enough to recognise the same mailbox again, and not enough to send anything to it.
- Extra time added to a confirmed email, on the rare occasions we give some — to make up for a fault, or as thanks. Beside that email's one-way hash we keep how much was given, how much of it has been used, and a short note of why. It is not deleted when it runs out, so that the record of what was given stays; and a job that draws on it names that hash until it finishes, so that what it held can be settled or given back.
- Daily usage counters, keyed by one-way hashes made with a fixed secret and the date, so that the keys are different every day, of: your network address, as a ceiling shared by everyone on that connection; the random number this browser keeps in a cookie; the one-way device codes described on the cookies page, combined with your network address and, for a browser with no finished transcription here from an earlier day and no confirmed email, also with the country and time zone of your connection; and your email, if you confirmed one. Beside them are shared counters that name no one: one per country for everyone without a confirmed email, one for everyone coming through a privacy relay, and one for everyone at all. Neither your IP address nor any device value is stored. The counters are deleted two days after the day they count. Different spellings of one mailbox — with dots or a
+tag— count as one. - Counts of refusals, by reason — which limit turned a submission away, whether an email had been confirmed, and whether the browser was new to the site — with nothing that identifies anyone. Kept for 30 days, to tune these limits.
- Whether your address belongs to a VPN, a data centre, the Tor network or a privacy relay such as iCloud Private Relay or Cloudflare WARP, checked against public lists kept on this site's own server — nothing is sent anywhere to find out. VPN, data-centre and Tor addresses are shared by strangers and change with a click, so they carry no free time of their own: through one, the site asks you to confirm an email instead. A relay's addresses are shared too, so through one nothing is counted against the address or a device at it: visitors without a confirmed email who come through relays share a daily allowance between them, besides what is counted against their browser and, for a browser new to the site, against its kind of device in its area. The answer is not stored, except that the record of a job made through a relay names the relays' shared counter it was charged to.
- Monthly totals — GPU seconds and money spent. These are about the service, not about you, and are not deleted.
What is not done with it
Nothing is used to train any model. Nothing is sold, shared or published. No one listens to submitted recordings. There is no advertising on this site and no advertising network is given anything.
Why, and on what basis
- The transcription, the code that confirms an email, and the one message you may ask for — to provide what you asked for (GDPR art. 6(1)(b)).
- The daily counters, the device codes, and the VPN and relay check — a legitimate interest (art. 6(1)(f), recital 47): that one person cannot take several free allowances by switching window, browser, network or VPN, without counting everyone who shares a connection as one person. The free time is paid for by donations, and this is how it is shared out fairly.
- Who else handles it, each only to do its part: the companies that host the site and count its page views, keep its database and its files, run the bot check when it is switched on, run the machine that transcribes, and send its email.
Objecting
You can object at any time (GDPR art. 21) to any of the processing above that rests on a legitimate interest — the daily counters, the device codes and the VPN and relay check — by writing to contact@quran-transcribe.com. Nothing the site keeps would let it switch the device check off for one person, so for that there is a switch, for this browser, on the cookies page. With it off, none of the device facts described there is read and no device code is sent; this browser's cookie is still used, and free time in that browser needs a confirmed email, whether or not it has been used here before — which gives you 2 h 30 min a day of your own. In Safari the switch lapses after seven days without a visit (see the cookies page).
Deleting things, and asking questions
Every result page has a button that deletes the recording, the subtitles and the record immediately — no waiting for the 12hours to pass, and no request to us.
The daily usage counters for your connection, your browser and your device are kept under keys made with a secret and the day, never under your address, your cookie or your device's facts, and nothing else is kept to look them up by. The site finds today's only from what your browser sends with a request — that is how the form shows the time you have left — and they delete themselves two days after the day they count, as does the counter of a confirmed email.
If you verified an email, you can sign this browser out from the home page, which discards the proof it was holding. The hash itself stays, as the key of a usage counter: it is one-way, it cannot be turned back into an address, and it is not something anyone could write to. It is kept so that proving the same mailbox again gives you back the same daily allowance rather than a fresh one.
This page describes what the code does. If something here does not match what you observe, that is a bug and worth reporting.