How Hafidz handles your data

Last updated: May 25, 2026

Hafidz is built to be useful even with the network off, so by default it stores everything on your device and sends nothing back to us. This page describes exactly what that means.

What stays on your device

Which verses you have marked as memorised, and their strength (Fresh / Firm / Mutqin).
Your review history — every Again / Hard / Good / Easy rating and the timestamp.
Your reading position, daily streak, daily target, and the verses you have flagged as "stumbles".
App preferences: reciter, translation language, reader mode, active-recall mode, tasbih count.
Cached mushaf pages and tafsir text fetched for offline use.

All of this lives in a local SQLite database inside the app's sandboxed storage. It never leaves your device through any code we wrote, and there is no Hafidz account or user identifier.

What ships inside the app

A lot of the reading experience needs no network at all, because the static parts are bundled into the app you install from the store:

Mushaf page images — all 604 printed pages of the Madinah Mushaf 1441 AH, sourced from Quran.com's public page-image dataset and packaged with the app at build time. Rendering a page does not contact the network.
Word coordinates — the bundled ayahinfo_1024.db from Quran.com's ayahinfo dataset, which tells the reader where each word sits on the page. Used locally for tap targets and highlights; never sent anywhere.
Static section data for the Memory Map and the mutashabihat ("similar verses") cards.

What we send over the network

Some content still travels over the network so the app can stay small and the per-language data can update without an app release:

Per-word translations and transliteration from the Quran.com API, fetched the first time you open a page and cached locally afterwards.
Tafsir text from equran.id (Indonesian / Kemenag) and Quran.com (English / Arabic), fetched per surah and cached locally.
Recitation audio streamed from the reciter's public audio CDN at playback time.

These requests carry the standard network metadata your device attaches to any HTTP call (IP address, user-agent, the verse or page identifier being requested). We do not add any custom tracking headers, and we do not log these requests on our side. You can pre-fetch all of the above with Settings → Offline → Download for offline, after which the app can run with the network off.

Analytics & advertising

Hafidz contains no analytics SDK, no crash-reporting service, and no ads. We do not know how many people use the app or which features they use.

Children

Hafidz is suitable for all ages and does not collect personal information from anyone, including children under 13.

Data retention & deletion

Because all your data lives on your device, you control it completely. Deleting the app from your device removes everything: memorisation records, review history, cached content, and preferences. There is no server-side copy to request.

Third-party services

The third parties Hafidz contacts are listed above (Quran.com for translations and audio metadata, equran.id for Indonesian tafsir, the reciter's audio CDN for recitation streams). Their own privacy policies apply when your device connects to them — please consult those services directly if you need detail on their practices. The bundled page-image and ayahinfo datasets from Quran.com ship with the app and do not involve any runtime network connection.

Changes to this policy

We will update this page when our practices change and bump the "Last updated" date at the top. Material changes will be noted in the app's release notes as well.

Contact

Questions about privacy? Reach us at hafidzquran.com.official@gmail.com.