Permission Disclosures
This page applies to the Android version of sudo ego only. The permissions described below (AccessibilityService and App Usage Access) exist only on Android. The iOS version uses Apple's Screen Time / Family Controls and does not request or use any of these permissions.
Accessibility Service Disclosure
This disclosure is displayed in-app (as a modal or full screen) when requesting the AccessibilityService permission on Android devices.
1. Why We Use This Permission
sudo ego uses Android's AccessibilityService to detect in real time when you open one of the apps you have chosen to block.
When a Ritual lock is active and you launch a blocked app, sudo ego immediately displays the Ritual lock screen. This feature is a self-control tool that operates exclusively under your explicit consent and configuration.
2. What Data the Accessibility Service Accesses
The Accessibility Service detects only one thing:
- App launch events — the package name (app identifier) of the app that moved to the foreground
sudo ego does not access the following:
| Data not accessed | Details |
|---|---|
| On-screen text content | We do not read text displayed in any app, notifications, or messages |
| User input | We do not log keyboard input, search queries, or notes |
| Passwords and credentials | We do not access login information, PINs, or financial data |
| Personal messages and conversations | We do not read SMS, messaging apps, or email content |
| Photos and files | We do not access your gallery, downloads, or documents |
Technical basis: sudo ego's AccessibilityService is implemented with canRetrieveWindowContent=false. This setting technically prevents the service from reading any screen content. The service receives only app-switch events — which app came to the foreground.
3. How the Detected Information Is Used
App launch events detected by the Accessibility Service are handled as follows:
- Processed on-device only. Detected app launch events never leave your device.
- Not transmitted to sudo ego servers. We do not store information about which apps you open.
- Not shared with any third party. App launch events are never used for advertising, analytics, or any other purpose.
- Used solely to display the Ritual lock screen. The only action taken is showing the Ritual lock screen when a blocked app is opened.
4. How to Revoke This Permission
You can revoke the Accessibility Service permission at any time.
Android settings path: Settings → Accessibility → Installed Services → sudo ego → Disable
Revoking this permission stops app-launch detection. If a Ritual lock is active, blocked apps may no longer be intercepted immediately upon launch.
5. Your Consent
I have read and understood the above. I agree to allow sudo ego to use the Accessibility Service to detect when I open apps that I have configured as blocked.
This consent is voluntary. If you decline, you can continue using the app without granting this permission; however, the real-time app-launch blocking feature will not function.
App Usage Stats Permission Disclosure
This disclosure is displayed in-app (as a modal or full screen) when requesting the PACKAGE_USAGE_STATS permission on Android devices.
1. Why We Use This Permission
sudo ego uses Android's PACKAGE_USAGE_STATS permission (App Usage Access) to detect which app is currently in the foreground.
This permission works alongside the Accessibility Service to detect when a blocked app is launched. While the Accessibility Service handles real-time switch events, app usage stats provide a complementary detection mechanism. Together, they ensure the Ritual lock feature works reliably as you have configured it.
2. What Data This Permission Accesses
Using PACKAGE_USAGE_STATS, sudo ego reads only:
- Current foreground app — the package name (app identifier) of the app currently displayed on screen
sudo ego does not access the following:
| Data not accessed | Details |
|---|---|
| Time spent in each app | We do not collect how many minutes or hours you use any app |
| App launch frequency | We do not record how many times per day you open an app |
| Total screen-on time | We do not aggregate your overall screen time |
| In-app activity | We do not access information about what you do inside any app |
| Battery and network usage | We do not read per-app resource consumption data |
Beyond confirming which app is currently in the foreground, sudo ego does not read or store any usage statistics data.
3. How the Information Is Used
Foreground app information obtained via PACKAGE_USAGE_STATS is handled as follows:
- Processed on-device only. Information about which app is running never leaves your device.
- Not transmitted to sudo ego servers. We do not record which apps you open or when.
- Not shared with any third party. App usage information is never used for advertising, analytics, or any other purpose.
- Used solely to display the Ritual lock screen. The only action taken is showing the Ritual lock screen when you open an app you have designated as blocked.
4. How to Grant and Revoke This Permission
This permission must be granted manually in Android system settings — it cannot be requested through a standard runtime dialog.
To grant: Settings → Digital Wellbeing & Parental Controls (or App Management) → Usage Data Access → sudo ego → Permit Usage Access
To revoke: Follow the same path, select sudo ego, and disable Usage Access.
Revoking this permission stops app-launch detection. If a Ritual lock is active, blocked apps may no longer be intercepted immediately upon launch.
5. Your Consent
I have read and understood the above. I agree to allow sudo ego to use App Usage Access to check whether any app I have configured as blocked is currently running. I understand that usage statistics accessed through this permission are not transmitted to any server and are not shared with any third party.
This consent is voluntary. If you decline, you can continue using the app without granting this permission; however, the reliability of the app-blocking feature may be reduced.