Barakah — Privacy Policy

Effective date: 14 August 2026

Barakah is built to be private by design. We have no account system, no analytics and no tracking SDKs, and we do not collect, store or sell your personal data. Barakah sends nothing to any server we operate. A small number of features you explicitly invoke do contact third-party services; each one is listed under “When something does leave your device” below and in the app under More → Privacy Report.

What we collect

Nothing. Barakah has no account system and no analytics or tracking SDKs. Everything you enter (calculator inputs, tasbih counts, preferences) is stored only on your device.

To make product quality measurable without remote analytics, Barakah keeps coarse aggregate counters on your device: the UTC day, an allow-listed event kind (such as onboarding completed, share hand-off, review prompt requested, an app open — counted at most once per day, with its source: a reminder tap or a deep link — or your notification-permission decision), and a count. These counters contain no identifier, location, worship content, search history, or free text; only a rolling 90-calendar-day window is retained; and they are excluded from portable backup. No app code sends them off-device. They leave only when you explicitly export them under More → Privacy Report, where you can also erase them — the Privacy Report also shows you the same usage summary the counters support (active days, consecutive days), computed on your device.

Location

If you choose to share your location, it is used only on your device to calculate prayer times and the Qibla direction, and it is never transmitted to us — we operate no server and receive nothing. The city you choose is saved on your device (in local storage) so the app can remember it next time.

One exception, and only when you ask for it: if you tap to search for nearby mosques, your approximate area — rounded to about one kilometre, never your precise position — is sent to the open mapping service Overpass (overpass-api.de) to answer that one query. Nothing about you is attached to it and we never receive it. Similarly, tapping “directions” hands the mosque’s coordinates to your own maps app (Apple or Google Maps), after which their privacy policy applies rather than ours. You can clear your saved location and every other locally stored value at any time from More → Clear all local data.

Calculations

All prayer-time, Qibla, Hijri, Zakat, inheritance, and tasbih calculations run entirely on your device, offline. No data leaves your phone to perform them.

When something does leave your device

These are the only cases, and each happens solely because you chose it:

• Nearby mosque search — your approximate area (~1 km) is sent to overpass-api.de when you tap to search.
• Directions, licence and attribution links — opening one hands the request to your maps app or browser (Apple/Google Maps, Wikimedia Commons).
• Qur’an, dua and adhan audio — streamed or downloaded on request from everyayah.com and Wikimedia Commons.
• Word-by-word Qur’an data — fetched from quran.com’s open API only if you switch that feature on.
• Recitation self-check — if you turn it on and accept the separate consent prompt, your voice is sent to the platform’s speech-recognition service while you recite.
• Sharing, exporting and the clipboard — when you tap share or export — for example an ayah or prayer-timetable card, a quest achievement, a calendar file, an encrypted backup or a diagnostics file — exactly the content you chose is handed to your OS share sheet and then to the app you pick, governed by that app’s policy. If no share channel exists, the caption text is copied to the clipboard, where any app you paste into can read it.
• Android System WebView — Android itself may contact Google’s autofill servers from inside the app’s process. This is not Barakah’s code and we cannot switch it off; setting Android Settings → Autofill service to “None” stops it.

None of these send anything to us — we operate no server — and none of them carries an account, identifier or profile, because we have none to attach. They are still ordinary internet requests, though, so the service on the other end necessarily sees your IP address and what you asked for (which surah, which audio file, which area). An IP address can be an online identifier under GDPR, so we say so plainly rather than describing these calls as carrying “nothing about you”. Each one happens only when you choose the feature that makes it.

Your control over stored data

Everything Barakah saves — your location, calculation settings, Zakat and inheritance inputs, journal entries, bookmarks, tasbih counts, streaks, diagnostics, and coarse local measurement counters — lives only in your device's local storage. You can permanently delete all of it at any time using "Clear all local data" in the More tab; this does not require contacting us, since we never had a copy to begin with.

Optional app lock

More → "Require a passcode to open Barakah" lets you add a numeric passcode gate on top of your device's own screen lock, so a menstruation-tracking or journal entry left on-screen isn't readable by anyone who briefly picks up an unlocked phone. Only a salted hash of the passcode is stored on your device (the passcode itself is never written to storage or sent anywhere); there is no cloud recovery, so forgetting the passcode requires erasing local app data via the same "forgot passcode" screen. Because the underlying data itself is never encrypted at rest — only gated behind this in-app screen — this is a UX-level deterrent against casual/shoulder-surf access, not a substitute for your device's own encryption and screen lock.

Children

Barakah does not collect data from anyone, including children, and is suitable for all ages.

Changes

If this policy changes, the updated version will be posted on this page with a new effective date.

Contact

Questions? Email suasion.78.hymn@icloud.com.