Content Shield
Overview
Content Shield provides three ways to filter adult content in the Chastify Android app: hide detected areas on screen, temporarily block apps after a detection, and filter website domains through Family DNS VPN.
Image classification runs on your phone. DNS requests and device-control activity have different privacy behavior; see Privacy before enabling the modes.

An enabled setting does not always mean the service is running. Look for Screening, Active, or the DNS filtering status. Detection can miss content or flag harmless images; none of these modes guarantees complete coverage.
Requirements
- The Android app: Content Shield does not run in the website or iOS app.
- An active subscription: required to start live filtering and use the Content Shield controls. Remotely enabling AI app blocking also checks the wearer's subscription.
- The permissions for your chosen mode: grant these on the phone when requested.
| Mode | Permissions and requirements |
|---|---|
| Live blur & pixelation | Screen capture and display-over-other-apps permission. Enable the Device Control accessibility service for browser blocking and supported foreground-window tracking. |
| AI app blocking | Android 11 or newer and the Device Control accessibility service. This uses accessibility screenshots rather than the live filter's screen-sharing session. |
| Family DNS VPN | Android VPN permission. Check its running status after approving the prompt. |
You can use Content Shield without granting another person Device Control. Locking settings against changes is a separate option for an active control session.
Three Protection Modes
Use one mode or combine them according to the behavior you want. Browser & app blocking is an additional control for live filtering, rather than a fourth detection mode.
1. Real-Time Screen Filter
The app labels this mode Live blur & pixelation. It checks captured screen content and covers detected regions while the app underneath stays open.
- Enable Live blur & pixelation.
- Approve the screen-capture prompt. Content Shield requests the whole display so it can follow the foreground app; a single-app capture is not sufficient for that behavior.
- Check that its status says Screening.
- Expand Live filter settings to choose the appearance and detection settings.
| Setting | What it changes |
|---|---|
| Solid Black, Pixelated, or Blur | How detected regions are hidden. Solid Black is the simplest rendering option; blur and pixelation need additional image processing. |
| Sensitivity: Low, Medium, High | How readily the live filter masks a region. Higher sensitivity can hide more harmless content. |
| Content categories | Which detected body-area categories the live filter masks. These choices are separate from AI app blocking's category policy. |
| Overlay Text | Short phrases shown inside masked regions. Separate multiple phrases with commas. |
| AI Acceleration | Auto, CPU, or NNAPI processing. Changes apply when Content Shield next starts. |
Android can stop or revoke a screen-capture session. After turning the screen off, locking the phone, or stopping screen sharing, check Screening again. If capture has stopped, start live filtering again and approve the prompt when shown. Do not assume that a remembered enabled setting means new frames are being checked.
Browser & app blocking blocks supported browsers and selected apps when live screening is off, even if AI app blocking is active. Its built-in targets include X, Bluesky, Tumblr, and Reddit; additional apps can be selected from Device Control when installed-app information is available.
When a blocked app shows the Content Shield blocking screen, use its enable button to open the screen-capture flow. After permission is granted, Chastify attempts to reopen that app. Denying capture leaves browser blocking enabled.
The Advanced setup section includes an ADB screen-capture shortcut for users already configuring their own phone through ADB:
adb shell appops set net.chastify.app PROJECT_MEDIA allow
This changes the app's capture permission behavior. It does not replace checking that live screening is actually running.
2. AI App Blocking
AI app blocking periodically checks the foreground app. After a matching detection is confirmed by another scan, it navigates away from the app and shows a temporary blocking overlay. It does not uninstall or force-stop the app process.
Its detection categories are exposed buttocks, exposed female breasts, exposed female genitalia, exposed male genitalia, and exposed anus. Covered body parts are not part of this blocking policy. Changing live filtering's category choices does not change this list.
Expand Blocking settings to configure:
- Scan resolution: 320, 480, or 640 px. Higher resolution can help detect smaller images but needs more processing.
- Detection sensitivity: Normal, High, or Very high. Higher sensitivity accepts less confident detections; every level still requires confirmation.
- Block duration: the local control offers a base duration from 5 seconds to 5 minutes, with 30 seconds as the default.
- Escalating block duration: repeated detections in the same app can increase the block to 1, 5, 10, then 30 minutes. A block is never shorter than the configured base duration. The sequence resets after an hour without a new detection in that app.
Scan resolution and sensitivity are saved on that device. During keyholder control, the controller manages the base duration and escalation; those controls may also be locked during self-control.
This mode skips some apps, including Chastify itself, cameras, keyboards, system settings, launchers, and apps marked always allowed. It also depends on Android being able to provide a screenshot. It does not inspect every app or every video frame.
3. Family DNS VPN
Family DNS VPN creates a local DNS-filtering connection using Android's VPN permission. It checks domains against downloaded adult-content and advertising lists, uses family DNS resolvers for allowed lookups, and pins supported Google search domains to SafeSearch.
Enable the mode, approve Android's VPN prompt, and check that DNS filtering is active. The panel shows queries checked, queries blocked, list-loading status, and upstream timeouts. Enabled but not running means the filter is not currently processing queries.
The optional blocked-site overlay controls whether a blocking notice appears. It does not determine whether the DNS request itself is blocked.
DNS filtering cannot inspect images or videos inside social feeds. Apps using their own DNS-over-HTTPS, direct IP addresses, or other routes can bypass this DNS layer. Use live filtering or AI app blocking as an additional layer when appropriate; combining modes still does not guarantee complete filtering.
This is a DNS filter, not an anonymity service or a tunnel for all internet traffic. Another VPN or a revoked VPN permission can interfere with it; check its running status after changing Android's VPN settings.
Only DNS request and response packets pass through the Family DNS service. Normal app and website traffic, including HTTPS packets, is not routed through it. Family DNS can read the domain names in the DNS requests it handles, but it does not read or decrypt HTTPS traffic, inspect page contents, or see URL paths, messages, or passwords carried inside HTTPS connections.
Android's “Block connections without VPN” Setting
Family DNS routes DNS requests through its local VPN, while normal app and website traffic connects directly over Wi-Fi or mobile data. Android's Block connections without VPN setting blocks those direct connections, so apps and browsers can lose internet access even while DNS filtering is active.
If enabling Family DNS stops internet access or Chromium shows ERR_NETWORK_ACCESS_DENIED:
- Open Android Settings, find VPN, and open the settings for Chastify Family DNS. The exact menu names vary by device.
- Turn off Block connections without VPN.
- Keep Family DNS enabled in Chastify, check that DNS filtering is active, and retry the affected app or website.
Turning off this Android setting leaves Family DNS filtering active, subject to the DNS-filtering limits above. It is separate from Chastify's Prevent disabling option, which restricts switching off the feature during active Device Control.
Supporting Android's blocking setting would require handling all internet traffic, including TCP, UDP, IPv4/IPv6, connection state, and network changes—effectively a full VPN networking implementation rather than a DNS filter. Family DNS does not currently provide that functionality.
Keyholder Controls
An active Device Control relationship is required for a keyholder to manage these protections remotely. Having a shared lock alone does not grant device access.

The controller can manage browser blocking, live-filter categories and additional blocked apps, AI app blocking, its duration and escalation, and the available lock options. They can also request that the wearer enable Family DNS VPN or send a disable command.
Remote commands do not grant Android permissions. The wearer must approve screen capture and any required VPN prompt on the phone. A request to enable a mode is not proof that the mode is running; check the reported device status.
During active device control, detected app blocks and blocked adult domains can appear in activity history and trigger configured device-control consequences. These are separate from AI app blocking's temporary app-block duration.
Without an active controller, local settings remain available subject to permissions and subscription access. Self-control has its own restrictions once its settings or release are locked.
Prevent Disabling (Lock Options)
Browser & app blocking, AI app blocking, and Family DNS VPN have options that prevent the wearer from switching them off during an active Device Control session. A regular lock session by itself does not activate these device-control locks.
- Browser blocking's lock also prevents changing the live filter's content-category selection in the settings screen.
- AI blocking's base duration and disabling escalation can be restricted while its lock is active. Its local scan resolution and sensitivity remain separate settings.
- A lock you enable during self-control cannot simply be unchecked while that control session remains active.
- An authorized external controller can manage the protection settings; a disabled wearer control does not mean every setting is permanently immutable.
The live screen-capture session can still stop. Browser blocking handles that by blocking its target apps until screening resumes. These switches do not guarantee that Android will keep every service running or that filtering cannot be bypassed.
Privacy
Different parts of Content Shield process different information:
| Information | How it is handled |
|---|---|
| Captured screen images | Classified on the phone with the bundled image model. These image checks use local model inference. |
| Allowed DNS queries | Sent off the device to the configured Cloudflare Family and AdGuard Family resolvers, with fallback between them. The local VPN does not make these requests private from the DNS providers. |
| Filter lists | Downloaded and stored on the device. Their coverage can change; there is no fixed guaranteed domain count. |
| Detection and DNS diagnostics | Local settings, recent detection details, and diagnostic logs can contain app identifiers, detection categories, or domain names. |
| Device-control activity | During an active control relationship, app-block reports and blocked-domain reports can be stored on Chastify's server and shown to the controller. Reports include identifiers, reasons, and timestamps, rather than the captured image. |
When the AI Coach's Device Control integration is enabled for a self-control session, its context can include summaries of recent blocked apps and websites. On-device image detection does not mean all related activity stays on the phone.
Tips
- Live filtering has stopped: check screen-capture permission and the Screening status after waking the phone. Restart the mode if necessary.
- A browser is blocked while AI blocking is active: browser blocking specifically requires the live filter. AI app blocking does not satisfy that requirement.
- Harmless images are blocked: adjust the sensitivity for the affected mode when those settings are available. Live-filter sensitivity and AI-blocking sensitivity are separate.
- Battery or performance problems: start with Solid Black for live masks and the default 320 px AI scan resolution. Compare behavior on your own phone before increasing resolution or running multiple modes.
- DNS appears enabled but sites are not filtered: check that the VPN is running, lists have loaded, and the panel is not reporting upstream failures. Also check whether another VPN is active.
- Apps and websites lose internet access with Family DNS: turn off Android's Block connections without VPN setting; see Family DNS VPN and Android VPN blocking.
- A setting cannot be changed: check whether Device Control or a self-control lock is active. A greyed-out control may be an intentional session restriction.
- Unexpected behavior persists: contact support with the Android/app version, active mode, displayed status, and steps to reproduce it.