App privacy
What leaves your phone, what never does, and which switch controls each one.
The short version. No ads, and nothing in the app tracks you across other apps or websites. Prayer times are calculated on your phone, and your exact position is never sent to our server. Backup runs only when you tap it. Your qadaa — the prayers and fasts you owe — never leaves the device, and that is enforced in the code, not just promised here. A few things do leave the phone; every one of them is in the table below, with the switch that controls it, or a plain statement that there is none.
Who is responsible
Sakeena is published by meshmesh Labs, an independent software studio in Jordan. meshmesh Labs is not a registered company, so the controller of your data is the individual who operates it, as set out in the studio privacy policy. That page also lists your rights under Jordan's Personal Data Protection Law and the GDPR, and how to use them. This page is the part that is specific to the app.
Everything that leaves the phone
| What | When | Where it goes | Your control |
|---|---|---|---|
| Your prayer record, your settings and your chosen mosque | Only when you tap Back up now | Our server (Google Firestore), where we can read it | Back up my record; Delete my data |
| The next prayer times (up to six) and two Apple push tokens | While Update while Sakeena is closed is on — on by default | Our server, then Apple's push service, to update the Lock Screen countdown | That switch, in Settings → Adhan & alarms → Live Activities |
| Your country | When you open the mosques screen | Our server, to send you that country's mosque list | Not opening the screen |
| Mosques found near you: each mosque's name and coordinates | In the background, after launch | Our public mosque directory | None — see Mosques below |
| A nickname, your tasbeeh days, the juz you read, and your country | Only if you join the Rank board | Our server, and shown publicly to other users | Leaving the board; Delete account |
| Your email address and name | Only if you sign in with Apple or Google | Our sign-in service (Firebase Authentication) | Not signing in; Delete account |
| Crash reports, performance data and usage events | Always | Firebase (Google) | None — see Diagnostics below |
| The area shown on the mosque map | When the map is drawn | Google Maps, to fetch the map tiles | Not opening the map |
| A request for a tafsir file | When you download one of the five optional tafsirs | jsDelivr and GitHub, which host the files | Not downloading |
Nothing else is sent by Sakeena. Apple's own services are covered under Location below.
The prayer record and backup
Sakeena keeps a record of which prayers you marked as prayed. It stays on your phone unless you back it up. Backing up to our server is a one-time purchase; restoring is free. Once backup is unlocked and Back up my record is on, a backup runs only when you tap Back up now. Nothing is sent automatically.
A backed-up day holds only the prayers you affirmatively marked as prayed, the date and a timestamp. There is no field for what you missed anywhere in the format, and a prayer absent from that list is not a record that you missed it. A backup also holds your settings (such as calculation method, madhab, reminders and muezzins) and the mosque you chose as yours.
What never leaves the device
- Your prayer qadaa — the prayers you owe.
- Your fasting log and fasting qadaa counter.
- Your tasbeeh counts, lifetime totals and custom dhikr. (If you join the Rank board, only the number of days you met your own target is published, never a count.)
- Your Quran bookmarks and khatma plan.
- Your exact position, as far as our server is concerned. See below.
This is a mechanism, not a policy. Every write to our
server passes through a check that refuses any payload carrying a fenced field — the fasting keys
by name, and any field named missed, qadaa, owed,
fasting or fast. A document that carries one is not written at all: it is
dropped and logged. A future version of Sakeena that tried to sync your qadaa would fail on the
first attempt rather than succeed quietly.
We wrote it that way because a rule that lives only in a document cannot stop a future mistake, and this is the most private thing the app holds.
Location
Sakeena needs your location to calculate prayer times and the qibla direction. That calculation happens on your device, and your coordinates are never sent to our server. Some things derived from where you are do leave the phone, and we would rather list them than describe the app as sending no location data at all:
- Prayer times for the Live Activity. Up to six upcoming prayer times (in Ramadan, also the next imsak and maghrib) go to our server with two Apple push tokens and no account or name, so the Lock Screen countdown can move on while the app is closed. Prayer times place a phone to roughly a city. Turning Update while Sakeena is closed off stops this and deletes the record.
- Your country, when the mosques screen asks for that country's mosques, and on the Rank board if you join it.
- Apple's services. To name your city and to search the map for mosques, Sakeena uses Apple's own geocoder and MapKit search. Those send your location to Apple, under Apple's privacy policy; they never reach us.
Mosques
The mosque list comes from our own directory, one country at a time. To keep that directory growing, Sakeena searches Apple Maps for mosques within about 10 km of you after launch and adds any it does not already know. What is written is the mosque's name and coordinates — never yours, and with no account attached. There is no switch for this. It does show that someone using Sakeena was near those mosques, which is why it is in this table.
The mosque map is drawn by the Google Maps SDK, which receives the area on screen and your IP address to fetch the map, under Google's privacy policy. Directions open Apple Maps or Google Maps, whichever you choose.
Your account
Sakeena works with no account at all. An anonymous identifier is created the first time you back up, so your device can find its own data again; it is not tied to your name, email or phone number.
You may optionally sign in with Apple or with Google, so your backup survives losing the phone and follows you to a new one. If you do, we hold the email address and name that sign-in gives us. Sign in with Apple lets you hide your email, and Sakeena works exactly the same if you do.
The Rank board
The Rank board is opt-in. If you join, a nickname you choose, the number of days you met your own tasbeeh target, the number of juz you read, and your country are published to other Sakeena users on that country's board. Nothing else about you is on it. Leaving the board, or deleting your account, removes your entries.
Diagnostics
Sakeena sends crash reports, performance data and basic usage events to Firebase (Crashlytics, Performance Monitoring and Analytics), from every install. There is no switch for this; we say so here rather than offer a switch that does not exist.
What they carry: which screens and tabs were opened, when the app was opened, when the calculation method changed, when a reminder permission was asked for, and the size of a tip if one was bought. Crash reports carry the app version and build, the build type and your device's language. Firebase also creates installation identifiers for its own services (In-App Messaging and Cloud Messaging). What they do not carry: no account, no name, no user identifier and no user properties — the app has no code that sets either — and nothing about your prayers, fasts or qadaa.
Advertising and tracking
There are no ads in Sakeena, and no advertising SDK. The app never asks for permission to track you, so iOS gives it no advertising identifier, and none of the data above is used to track you across other companies' apps or websites, or shared with data brokers.
Purchases
The optional backup unlock and the "cup of tea" tips are bought through Apple. Apple takes the payment; we never see your card or your Apple account. The app checks the purchase on the device, and stores only whether backup is unlocked. A tip unlocks nothing.
Getting your data, and deleting it
In Settings → About & support → Privacy:
- Export your record hands you your prayer, fasting and qadaa records, tasbeeh counts and corrections, in a file you keep.
- Delete my data removes your record from the phone and from our server. If the server part fails because you are offline, the app tells you so explicitly rather than claiming success.
Deletion runs against the server even if you had already switched backup off — turning the switch off does not delete what was sent while it was on, so the delete does.
Delete account, in Settings → Account, removes the account, its backup and your Rank board entries from our server. Data on the phone stays until you delete it.
A backup is kept until you delete it or your account. Crash and usage data are kept by Firebase under its standard retention, and are not linked to you.
Features that are switched off
Some features in development, including AI explanations, are switched off in this version. If we switch on one that sends anything new, this page changes before it does.
Children
Sakeena is not directed at children and does not knowingly collect data from them.
Changes
If we change what leaves the device, this page changes with it, and the date below moves.
Contact
Questions about any of this: [email protected]
Last updated 14 October 2026