Kitaby

Privacy

Reading the Quran in Kitaby tells us nothing about you. An account is optional and only syncs your reading position and the places you pinned before, notes, playlists and settings between devices. No ads, no analytics, no trackers. Nothing is sold. Service providers receive only what is needed for the features described below.

Last updated: 10 November 2026.

Reading needs no account

The Quran text, its fonts and the tajweed colours are inside the app. Reading involves no network and no server.

Downloads (translations, tafsirs, recitations, mushaf fonts) come from our server. Each request carries an installation identifier: a random string created on first launch that names no person, account or device. It only serves to share the server fairly between installations. Uninstalling the app erases it.

Our web server keeps standard access logs (IP address, time, request) for fourteen days, to keep the service running and stop abuse.

The colours of the sky

To estimate dawn and sunset, our server first uses approximate location headers from Cloudflare when available. Otherwise it sends your public IP address to GeoJS, with ipwho.is and ip-api as fallbacks. The ip-api fallback uses HTTP. No GPS access or precise device location is requested. An IP estimate can describe your network provider or VPN rather than where you are.

Only the approximate latitude, longitude and country code are returned to the app. The country selects a regional calculation method locally. The server caches the estimate for a week under a keyed hash of the IP, without linking it to an account. The app keeps the last coordinates locally and calculates the sky offline; it normally refreshes weekly. Fixed hours remain available when no estimate can be obtained.

If you create an account

An account holds:

  • your name, used only to address you in emails;
  • your email address, to confirm the account and reset the password;
  • your password, stored hashed: nobody can read it, including us;
  • the six-digit codes we email you, also hashed, valid fifteen minutes;
  • your reading position, and the places you pinned before it, with the time of each, so that any device can take you back there;
  • your bookmarks, notes, saved words, memorised verses, playlists (each one's name, and the reciter and surah of each item) and settings;
  • one session token per signed-in device.

We keep this because syncing it is the service you signed up for (GDPR article 6(1)(b)). It is never used for profiling and never sent anywhere but your own devices.

Sharing a playlist

When you share a playlist, its name and its list of reciters and surahs are published at a public link that anyone who has it can open. The link never shows who shared it.

Shared while signed in, the link follows your playlist as you edit it. It stops working when you delete the playlist, and is erased with your account. Shared while signed out, the link is a copy tied to the app's installation identifier, not to you or to an account: only that installation can update it, and it stays online until you ask us to remove it.

Crash and performance reports

Unhandled errors and their stack trace go to Sentry, on European servers, with a count of failed playbacks by kind of failure. For one session in ten, anonymous performance measurements go too: how long the app takes to start and its calls take to answer. Every number is removed before they leave, so no surah, verse, page or reciter is ever named. No IP address, request headers, session replay, or record of which verse was open. Our server reports its own errors and response times the same way.

Identifying a recitation

When you tap the microphone on the home screen, and only then, the app records up to fifteen seconds of sound to identify a recitation playing nearby. The sound goes to our server alone, which answers with the reciter and the verse and discards it: it is not stored, not logged and not linked to you or to an account. A copy stays on your device, and is sent only if you agree to share your recordings, below. The microphone permission is asked for at that first tap, and can be withdrawn in your phone's settings.

When you recite from memory or read aloud, the app listens to follow you and uncover each word you say. That happens on your device, with a model downloaded once. The recording stays on your device, and nothing of it is sent unless you agree to share your recordings, below.

Recordings you choose to share

The app keeps the recordings of its microphone, when you recite or identify a recitation, on your device only: 500 MB at most, the oldest deleted first to make room. Nothing leaves your device unless you agree. They are deleted with the app, or with its data in your device's settings.

The first time you use the microphone, the app asks whether it may send them to improve recognition, including those already kept on your device. If you say no, it asks again a week later at the earliest, and never again if you choose Don't ask again.

If you agree, each recording is sent to our server: the sound as the app heard it, and what was recognised in it (for a recitation, the passage, the sounds and words recognised and where it lost track; for an identification, the reciter and verse found, or nothing), with the app's and the model's versions and the kind of device (Android, iPhone, Mac or browser). On a phone it waits for a connection that is not charged by the amount of data, such as Wi-Fi. It is linked to no account, name or installation identifier, serves only to train and test the recognition models, and is kept three years at most.

A recitation of the Quran can reveal your religion, so we ask for your explicit consent (GDPR article 9(2)(a)). You can withdraw it at any time in Settings → Help improve recognition: nothing more is sent, and your recordings stay on your device only, as before you agreed. Recordings already sent are linked to no one, so they cannot be found again to be removed.

Reporting a mistake

When you report a problem, we receive your message and what the app was showing, so that we can find it: the verse and the way you were reading (page, surah, printed mushaf…), the reading, script and colours chosen, the translations, tafsir and word-by-word in use and installed, the reciter, the app's language and version, and your device's model, system version and screen size. With it comes the technical state of the device, since a display fault often depends on it: its processor and graphics chip, memory and storage (total and free), battery level, the kind of network (Wi-Fi, mobile, none), the screens and the app window, accessibility settings such as bold text, how the app draws and how long it has been open. Nothing in it names you. A picture of the app's screen, as it was when you opened the report form, goes too. The same report is also filed with Sentry (below), so that it sits beside the errors of the minutes before; Sentry receives your message, not the screenshot. If you are signed in, the report is linked to your account so that we can answer; otherwise no account is attached. Reports are kept until the problem is handled, and the screenshot is deleted then.

What the app never does

No advertising, advertising identifier, analytics kit, tracker or social network button. Recitations, timings, page images and fonts are served by us: the app only contacts kitaby.cc and the crash reporter above. No other company knows which surah you opened, in which voice, or when.

Who else handles it

  • our server in Germany, where the database lives;
  • Cloudflare, which carries the traffic;
  • Resend, which delivers account emails and therefore sees the name and address in them;
  • GeoJS, ipwho.is and ip-api, for approximate network location;
  • Sentry, European region, for crash reports.

Database backups are kept on our own hardware.

How long it is kept

  • account data: until you delete the account;
  • backups: nightly, the last fourteen kept;
  • server access logs: fourteen days;
  • crash reports: ninety days;
  • recordings you chose to share: three years at most;
  • mistake reports: until the correction is made;
  • a playlist shared while signed out: until you ask us to remove it.

Deleting your account

In the app: My space → Account → Delete account (Settings → Account in versions up to 1.0.4). Without the app: https://kitaby.cc/account/delete.

Deletion is immediate and irreversible. The account, reading position and the places pinned before it, notes, saved words, memorised verses, playlists and the links that follow them, settings and device tokens are erased, not flagged. Backups roll off within fourteen days.

A playlist shared while signed out, and not shared again once signed in, belongs to no account and is not erased with one: write to us and we remove it.

What is stored on the device itself (downloads and your reading position) is removed by uninstalling the app.

Your rights

You may ask for a copy of your data, have it corrected or erased, or object to our holding it. Write to [email protected]; you will have an answer within a month. In the European Union you may also complain to your data protection authority.

Children

The app is not directed at children and asks nobody's age. Without an account, it uses only the technical data described above and what a reader chooses to send: a mistake report, a shared playlist.

Changes and contact

If any of this changes, this page and its date change with it. Questions go to [email protected].