Privacy Policy for Sabr
Last updated: 22 October 2026
Sabr ("the app") is an Android screen-time blocker published by Fares Ahmed ("we", "us"). This policy explains what the app accesses, what it does with it, and what leaves your device.
The short version: Sabr has no account, no analytics, no advertising, and no server of its own. Your app lists, your deed history, and your settings stay on your phone and are never sent to us. The one thing that leaves your device is ordinary DNS traffic, which must reach a DNS resolver for the internet to work. Sabr does not intercept it. You can optionally point Android's Private DNS at a third-party family filter yourself; if you do, that provider answers your lookups instead of your network's resolver (section 2).
1. What Sabr accesses on your device
| Data | How it is accessed | Why |
|---|---|---|
| App usage statistics — which app is in the foreground and for how long | Android's Usage Access permission (PACKAGE_USAGE_STATS) |
This is the core of the blocker: detecting when you open an app you asked Sabr to guard, and enforcing daily time limits. |
| Installed apps — the names and packages of apps with a launcher icon | Android package manager | So you can choose which apps to restrict. Icons are read per app, only to display them in that list. |
| Your blocklists and settings — chosen apps, schedule and limit settings | Created by you, stored on device | To enforce your settings. |
| Your activity in Sabr — deeds completed, breaks earned, streaks | Created by you, stored on device | To show your progress and calculate streaks. |
Sabr does not access your messages, contacts, photos, files, calendar, microphone, camera, the contents of your network traffic, or your DNS queries. It cannot read the pages you visit or the domains you look up. The one exception is approximate location, and only if you turn on prayer notifications — see below.
2. What leaves your device
Nothing is sent to us. Sabr has no backend, no account system, and no telemetry. We never receive your app lists, your usage history, your domains, or your deed history.
Two things do leave your device during normal operation:
1. DNS lookups, handled by your own resolver. To load a site, its domain must be resolved by a DNS resolver. Sabr does not run a VPN, does not intercept DNS, and does not see those lookups. Your device sends them straight to the resolver configured by your network (Wi-Fi/mobile). That resolver can see the domain names being looked up, exactly as it would without Sabr installed.
Optional Private DNS filter (Android 9 and later). Sabr's
Settings screen can open Android's Private DNS settings and shows
CleanBrowsing's free Family Filter hostname
(family-filter-dns.cleanbrowsing.org). This is entirely your
choice and happens in Android settings, not inside Sabr. If you enable it,
Android sends all DNS lookups on the device to CleanBrowsing, which
sees the domain names of every lookup and answers adult, malware, and
mixed-content domains with a block page. Sabr does not receive those
queries, cannot read them, and cannot switch the setting on or off for you.
You can change or remove the hostname in Android settings at any time.
Because this is a device-wide DNS setting, some apps that use their own
encrypted DNS or a VPN may bypass it.
2. Your approximate location, if you turn on prayer
notifications. Sabr needs to know roughly where you are to look up
prayer times. With your permission it reads the device's last known
approximate location (coarse, not GPS), rounds it to two decimal
places — about a kilometre — and sends those coordinates to
Aladhan (api.aladhan.com), a public prayer-time API, to fetch
the month's times. Aladhan sees the rounded coordinate, the month, and your
IP address, and nothing else: no identifier, no app list, no usage data.
The times are cached on your device, so the request is made about once a
month rather than on every launch. If you decline the permission, the app
falls back to a city you choose, and the same request is made with that
city's fixed coordinates. Prayer notifications are off by default; turning
them off stops both the request and the notifications.
3. Your in-app purchases, if any. Sabr is distributed free and charges nothing. If that ever changes, payment processing would be handled by Google Play, under Google's privacy policy, and this policy would be updated before release.
3. What is stored, and where
All of it is on your device:
- App-level storage (Android
AsyncStorage): your blocked apps, deeds, break sessions, daily stats, cached prayer times, and settings. - Service-level storage (Android
SharedPreferences): the same enforcement config, kept by the blocking service so it can keep working after the app is closed or the phone restarts. - A cache directory for app icons, which Android may reclaim at any time.
None of this is backed up or synced — Sabr sets
allowBackup=false, so your data is not copied to Google's cloud
backup either.
4. Permissions, and why each is needed
- Usage access — detect the foreground app and enforce limits (the blocker).
- Display over other apps — show the pause screen on top of a blocked app.
- Notifications — tell you when a break is ending, and show the ongoing "Sabr is active" notification required for the service.
- Run after restart — resume blocking after a reboot.
- Alarms — schedule break-expiry and break-warning notifications.
- Battery optimisation exemption (optional) — ask you to exempt Sabr so aggressive battery managers don't stop the blocker.
5. Sharing and disclosure
We do not sell, rent, share, or transfer your data to anyone. There is no ad network, no analytics provider, and no crash-reporting SDK in the app. The only third parties that see anything as a result of using Sabr are your DNS resolver — your network's resolver, or CleanBrowsing if you chose to enable its Private DNS filter in Android settings — because the DNS protocol requires a resolver to answer a lookup at all, and Aladhan if you have turned on prayer notifications, because the prayer times come from its API. We neither own nor operate CleanBrowsing or Aladhan and have no relationship with either.
We would only disclose data if legally compelled, and because we hold none, we would have nothing to disclose.
6. Diagnostics you choose to send
Sabr's Settings → Diagnostics screen can show a technical snapshot (device model, Android version, permission states, and whether the guard service is running) and offers a Share button so you can send it to us when reporting a problem. This only happens if you tap Share and pick a destination yourself.
That snapshot deliberately excludes the raw record of which apps you opened — package names are reduced to short non-reversible tags and timestamps are stripped before anything is shareable. The same rule applies to the system log: the app does not write the package name of the app you opened, or the domain you attempted to visit, to logcat. Nothing is ever sent automatically.
7. Children
Sabr is not directed at children under 13, and we do not knowingly collect personal information from children. Because the app collects nothing on our side, there is nothing for a child's data to be exposed to. Parents looking for a family screen-time tool should be aware that Sabr is designed for an individual managing their own device.
8. Your control and deletion
You are in control of everything Sabr stores:
- Reset all data — Settings → Reset All Data deletes your blocked apps, deeds, stats, settings, and resets the native enforcement config.
- Private DNS filter — if you enabled one, change or clear it in Android Settings → Network & internet → Private DNS. Sabr never controlled it.
- Uninstall — removing the app deletes all app storage, the service preferences, and the icon cache.
Since we hold no data about you, there is no server-side record to request or delete.
9. Security
Data stays in your device's private app storage, which other apps cannot read. Sabr declares no VPN service and does not intercept network traffic. Internal broadcast receivers are not exported. The app disables Android cloud backup. The optional Private DNS filter in section 2 is a system setting outside Sabr's control; if you enable it, DNS queries are sent to CleanBrowsing over Android's encrypted Private DNS (DNS-over-TLS).
10. Changes to this policy
If this policy changes materially, the "Last updated" date will change and the new version will be published at this same address before the app is updated. If Sabr ever adds a feature that sends data anywhere — analytics, sync, crash reporting — this policy will be updated and the change disclosed before that feature ships.
11. Contact
Questions about this policy or about Sabr's data handling:
Fares Ahmed —
eng.fares0ahmed@gmail.com