MindWarden Accessibility Declaration

Last updated: July 20, 2026

MindWarden uses Android Accessibility for user-configured digital wellbeing blocking. MindWarden is not a disability-support accessibility tool; it uses Accessibility because Android does not provide a narrower ordinary permission for the real-time app and supported-browser information needed by its blocker.

Why Accessibility Is Used

MindWarden uses Accessibility to:

• Detect the foreground app and show the Block Screen when a user-selected app rule matches.
• Read the visible address-bar value in supported browsers and compare it with local website, adult-content, Safe Search, and social-media rules.
• Identify unsupported browsers when you enable Block Unsupported Browsers.
• Enforce an active Phone Lock session by keeping the MindWarden lock experience visible.
• Add user-configured friction around attempts to disable protection during an active protected period.

What MindWarden Does Not Read

MindWarden does not use Accessibility to read or upload messages, passwords, private chats, page content, search text, or unrelated personal content. It does not use Accessibility for ads, attribution, user profiling, or general-purpose automation.

Local Processing

Accessibility events are processed on your device. When a block succeeds, MindWarden stores only the minimum fact needed for Progress: timestamp, block source, and either the app package or normalized domain. It does not keep the full URL, path, page content, or search query.

User Control

You choose whether to enable MindWarden's Accessibility service in Android settings. You can turn it off at any time. Blocking features that depend on Accessibility will stop working when the service is disabled.

MindWarden does not prevent you from accessing Android's method to disable Accessibility or deactivate Device Admin.