Sunnah Lock is a blocking app, so it needs more Android permissions than a regular app. Here is every permission it requests, what the app does with it, and what happens if you deny it.
Every permission on this page is used only to enforce blocks. None are used for analytics, advertising, tracking, or sending data off your device.
Core blocking permissions
Detect the foreground app and browser URL
Manifest: BIND_ACCESSIBILITY_SERVICE
Why: This is the blocking engine. It reads the package name of whichever app you just opened (and the URL if that app is a browser) so it can decide whether to show a block screen.
If denied: The app cannot block anything. See the full Accessibility Service Disclosure for detail.
Show the block screen on top of blocked apps
Manifest: SYSTEM_ALERT_WINDOW
Why: When a block triggers, the block screen (showing a Qur'an ayah or Hadith as a reminder) is drawn on top of the blocked app. Android requires this permission to draw over other apps.
If denied: Block screen won't appear; user can see and use blocked apps normally.
Enforce daily usage limits
Manifest: PACKAGE_USAGE_STATS
Why: Required only for the usage-limit feature ("block Instagram after 30 minutes per day"). The app reads per-app foreground time totals from Android's Usage Stats API.
If denied: Usage-limit blocks don't work. Time schedules, location blocks, and normal app/keyword blocks still work.
Anti-bypass permissions
Prevent uninstall and disabling
Manifest: BIND_DEVICE_ADMIN
Why: Device Admin is what prevents a child (or a lapse-of-will-power adult in Strict Mode) from uninstalling the app or disabling its services without the PIN. This is the whole reason the app can't be worked around.
If denied: App can be uninstalled or disabled freely — the core protection disappears.
Restart blocking after reboot
Manifest: RECEIVE_BOOT_COMPLETED
Why: Without this, turning the phone off and on again would disable the blocking engine until the user manually re-opened Sunnah Lock. This would be an easy bypass.
If denied: Blocking is off until the user opens the app after every reboot.
Keep the blocking engine alive
Manifest: FOREGROUND_SERVICE
Why: Android aggressively kills background processes. A foreground service keeps the blocking engine running reliably, with a persistent notification so you always know Sunnah Lock is on.
If denied: Android may kill the service, leaving gaps where blocks don't trigger.
Feature-specific permissions
Trigger location-based blocks
Manifest: ACCESS_FINE_LOCATION, ACCESS_BACKGROUND_LOCATION
Why: Used only for the location-trigger feature ("block Instagram when I arrive at the masjid"). The app checks whether you are inside a radius you defined.
What we do with it: Your location is read on-device and checked against your saved location triggers. It is never sent anywhere and not written to any log.
If denied: Location-based blocks don't work. Everything else works.
Show block confirmations and reminders
Manifest: POST_NOTIFICATIONS
Why: Displays the persistent "Sunnah Lock is active" notification, block triggered notifications, and Strict Mode status.
If denied: App still works; you won't see status notifications.
Firebase sign-in and subscription check
Manifest: INTERNET, ACCESS_NETWORK_STATE
Why: Used only for Firebase Authentication (sign-in), Firestore (subscription state), Google Play Billing, and the Play Integrity check. The blocking engine itself makes no network calls.
If denied: Sign-in and subscription features don't work. On-device blocking still works (offline).
What is not requested
Sunnah Lock does not request:
- Contacts, call logs, or SMS
- Camera or microphone
- Photos or files
- Calendar or email
- Bluetooth or nearby devices
If you ever see the app request one of these in the future, it is a bug and we want to hear about it.
Contact
Questions about a specific permission: admin@sunnahlock.com