Device Control

What is Device Control?

Device Control, also called Parental Control in some parts of the app, lets you restrict an Android phone for focus, accountability, and self-control. It can enforce screen time limits, app restrictions, time windows, and optional browser filtering.

When enabled, a controller can:

• Set daily screen time limits
• Block specific apps
• Filter websites and block adult content
• View app usage for each synced Android device
• Take screenshots, only with your consent
• Set time windows for when you can use your phone
• Manage more than one Android device on the same Chastify account

Who can use it?

• Wearers can enable Device Control in the Chastify Android app and grant access to a keyholder.
• Keyholders can manage restrictions after the wearer grants control.
• Self-control users can grant control to themselves to test the system or run a self-control session.

AI assistance

AI coaches can help guide setup and configure restrictions after Android permissions are granted. Use self-control mode first if you want to test app blocking, time limits, browser filtering, screenshots, and release behavior before giving access to a keyholder.

Multiple Android devices

Device Control supports Chastify accounts with more than one Android phone or emulator connected.

The control session and rules are shared for the wearer account, but runtime data is tracked per device. This means a keyholder can set one rule set, while each Android device reports its own screen time, app usage, permission status, installed apps, and online state.

For example, if a keyholder sets a 4 hour daily screen time limit, that limit applies to each controlled Android device. Phone A using 3 hours does not consume Phone B's tracked usage for the day.

If a wearer has multiple synced devices, the keyholder view may show separate device entries such as Samsung Galaxy S24+ and Android Emulator. Open the correct device entry before reviewing usage or device-specific status.

See Multi-Device Support for the detailed behavior.

Getting started

1. Install the Android app

Device Control is only available in the Chastify Android app. It is not available in the browser or on iOS.

2. Open Device Control

1. Open Chastify on the Android device.
2. Go to Device Control.
3. Tap Start Setup.

3. Grant permissions

The setup screen guides you through each permission. Some permissions open Android settings pages, so you may need to press Back after enabling each one.

Permission	What it does	Why it is needed
Device Admin	Prevents uninstall through normal app removal flows	Helps prevent bypassing Device Control while a session is active
Overlay	Allows Chastify to show blocking screens over other apps	Blocks restricted apps and websites
Accessibility	Detects foreground apps and supported browser URLs	Enables app blocking, browser filtering, and time restrictions
Usage Stats	Reads app usage duration	Calculates screen time and per-app limits
Notifications	Keeps status and control feedback visible	Improves reliability and user feedback
Screen Capture	Allows live screenshots	Only used if screenshot consent is enabled
Secure Settings	Can restore accessibility if disabled	Optional ADB-granted recovery permission

Secure Settings recovery

Secure Settings is optional. It lets Chastify attempt to restore its accessibility service if it is disabled during an active Device Control session.

Grant it from a computer with ADB:

adb shell pm grant net.chastify.app android.permission.WRITE_SECURE_SETTINGS

On macOS, if ADB is installed in the default Android SDK path:

~/Library/Android/sdk/platform-tools/adb shell pm grant net.chastify.app android.permission.WRITE_SECURE_SETTINGS

After running the command, return to Device Control and refresh the permission status.

4. Give control to a keyholder

After setup is complete:

1. Review the permissions and capabilities.
2. Confirm the keyholder shown in the Device Control screen.
3. Tap Give Control to Keyholder.

Your keyholder can then manage the device from their dashboard.

What keyholders can do

Screen time limits

Keyholders can set a daily screen time limit. When the limit is reached, Chastify blocks non-protected apps and shows a blocking screen.

Time restrictions

Keyholders can define allowed or blocked time windows. Outside allowed hours, restricted apps are blocked.

App blocking

Keyholders can:

• Block specific apps
• Set per-app time limits
• Set per-app launch limits
• Mark apps as protected or always available
• View installed app metadata used for configuration

Browser control

Keyholders can:

• Enable adult-site filtering
• Block specific domains
• Use allowlist mode
• View recent browser activity used for enforcement
• View blocked browser attempts

Screenshots

Screenshots require explicit wearer consent. If screenshot consent is disabled, the keyholder cannot take screenshots.

Screenshots are transmitted live and are not stored by Chastify as a permanent media library. Android can also stop screen capture sessions for privacy and battery reasons, so screenshots may require fresh consent or reactivation.

Privacy information

Data Device Control may collect

• Installed app names and package names
• App icons or icon metadata
• Screen time and app usage summaries
• Browser URLs or domains used for filtering and activity views
• Blocked app and blocked website attempts
• Live screenshots only when screenshot consent is enabled

Data Device Control does not collect

• Passwords
• Private message contents
• Payment information
• Screenshots without explicit consent

Retention

• Browser history is kept for a short period and automatically removed.
• App usage is shown in recent activity views for enforcement and accountability.
• Screenshots are not stored as a long-term gallery.
• Device Control records are removed when control ends, unless a feature is explicitly designed to persist after the lock session.

Persist after lock session

Persist After Lock Session keeps keyholder control active after the related lock ends. Use it only with a trusted keyholder.

This is separate from a Self-Control Release Lock, which prevents disabling self-control until a timer or active lock session condition has ended.

Managing Device Control

Wearers can open Device Control to see:

• Who currently controls the device
• Whether self-control is active
• Today's screen time for the current Android device
• Remaining time
• Active app restrictions
• Browser rules
• Permission status
• Sync status

If a permission is missing, open the permission row and re-grant it from Android settings.

Releasing control

When control is released:

• The keyholder loses access to device management.
• Device Control restrictions are removed.
• Cached enforcement data is cleared.
• The wearer can disable Device Control services from the app.

warning

Do not rely on Device Control as a safety-critical system. Network issues, OEM Android behavior, permission changes, and device restarts can affect enforcement. Always keep a realistic recovery path.

Keyholder access

When someone grants you Device Control:

1. Open the lock or keyholder dashboard.
2. Choose Device Control.
3. If the wearer has more than one Android device, choose the device you want to inspect.
4. Configure screen time, app blocking, browser filtering, and consent-based features.

Troubleshooting

Device offline

If the device appears offline:

• Ask the wearer to open Chastify.
• Ask them to confirm accessibility is still enabled.
• Ask them to tap manual sync.
• Check whether battery optimization or network restrictions are interfering.

Permission issues detected

If permissions are missing:

1. Open Device Control on the Android device.
2. Check Permissions Status.
3. Re-grant any missing permissions.
4. Restart Chastify if Android settings do not update immediately.

Android Restricted Settings

info

On Android 13 and newer, sideloaded APKs can be affected by Android Restricted Settings. Accessibility access is one of the protected permissions. If Chastify was installed or updated outside Google Play or another trusted installer, Android may gray out the Chastify accessibility services after an app update and mark Device Control as set up but not active. This can happen even when Secure Settings recovery or Device Owner hardening is enabled.

If the Chastify Parental Control or Lockink Blocker accessibility service is grayed out, open Android App info for Chastify, allow Restricted Settings for the app, then return to Accessibility and enable the services again. Restricted Settings must also be allowed on first install before the accessibility services can be enabled.

Can I uninstall Chastify while Device Control is active?

Device Admin can prevent uninstall while Device Control is active. If optional Device Owner hardening is enabled, uninstall protection can be stronger. See Device Ownership for the advanced setup.

What happens when my lock ends?

Device Control ends with the lock unless Persist After Lock Session is enabled or a self-control release condition is still active.