AuraLock Android Permissions: What They Do
Understand why AuraLock needs certain Android permissions, exactly how to grant each one on your device, and how they protect your focus.
AuraLock depends on several Android permissions to create and hold your focus boundaries. Each one serves a clear purpose, and each is explained on its own page — with the exact tap path for your phone.
Permissions are essential
Not sure where a setting lives on your phone?
Required permissions
Accessibility
AuraLock uses this to detect when you open an app and to enforce your Aura boundaries.
Display over other apps
Lets AuraLock draw the Aura overlay and the boundary screen on top of other apps.
Usage access
Shows AuraLock which apps are running so it can enforce your boundaries and power Analytics.
Recommended settings
Battery optimization
Exempt AuraLock from battery optimization so a long Aura is never cut short in the background.
Auto-start and background activity
On MIUI, ColorOS, Funtouch, EMUI, and HiOS, allow AuraLock to auto-start and run in the background — otherwise the system may close it mid-session.
Alarms and reminders
Keeps session timers, schedules, and AuraWake alarms firing at the right time, even in the background.
Privacy
AuraLock does not collect or transmit your usage data. These permissions are used only on your device, and only to enforce the boundaries you set.
Check everything at once
Run Guardian inside AuraLock. It checks every permission and battery setting on your exact device and flags anything that would silently break your boundary — with a one-tap fix.