Android app blocker permissions
Answer: On Android, Lauds needs Accessibility Service and Usage Access so it can tell when an app you chose is opened and place the Lauds shield over it. Those permissions are used for blocking behavior only. Lauds says it does not read screen content, capture keystrokes, or upload foreground app names.
Why Android asks for these permissions
Accessibility Service
Lauds uses Android Accessibility Service to notice when a selected app moves to the foreground during your lock window. That lets the app show its shield before the feed becomes the first thing you see.
Usage Access
Usage Access helps Lauds understand foreground app state reliably enough to enforce a user-chosen lock. Without it, the blocker may not know when Instagram, TikTok, YouTube, or another selected app opens.
Installed app list
Android may show permission language for the installed app list. Lauds uses this so you can pick which apps to lock. The privacy policy says the list stays on your device.
Local unlock state
Lauds keeps the morning rule, unlock window, selected apps, and completion state as local app behavior. The lock can then work without treating your morning as a server-side profile.
Privacy boundaries
- Lauds says it does not read screen text, collect keystrokes, or record what you do inside other apps.
- Foreground app names are used in memory for blocking and are not sent to Lauds servers.
- Journal entries and optional photos are stored locally in the app's private storage.
- Limited anonymous mobile analytics may be used for onboarding, paywall, and referral health, but not with journal text, selected app lists, foreground app names, Screen Time tokens, email addresses, or raw referral codes.
Permission checklist
Android app blocking fails quietly when a required permission is missing, so the setup should be checked in plain language. A working install needs the app list chosen by the user, a lock window, Accessibility Service permission, Usage Access permission, and any manufacturer-specific background setting required by the device.
During setup
Confirm that the app explains each permission before sending the user into Android settings. The page should match the in-app language so users do not feel surprised.
After setup
Open one selected app during the lock window and confirm the Lauds shield appears. Then complete a Bible app, timer, or journal unlock and confirm the selected app opens normally.
When it stops working
Check whether Android disabled Accessibility Service, whether battery settings restricted background work, or whether the lock window has already ended.
When uninstalling
Revoking the permissions in Android settings or uninstalling Lauds removes the blocker. Lauds should never require hidden device-management steps to leave.
Honest limitations
Users can revoke Accessibility Service or Usage Access in Android settings. If those permissions are turned off, the lock feature will stop working or become unreliable. Some Android skins may require additional background, autostart, overlay, or battery settings controlled by the device maker.