Skip to main content

Device Control

What is Device Control?​

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

A controller can manage restrictions, review device usage, and use optional sharing features when you have granted the required consent. Device Control is separate from Bluetooth control of a chastity device.

Looking for a quick answer?

Who can use it?​

  • Wearers set up the Android permissions and can grant control to the current keyholder of an eligible active shared lock.
  • Keyholders manage restrictions through Chastify after the wearer grants control. The controller's phone does not itself need to be the controlled Android device.
  • Self-control users can manage their own restrictions, including when they do not have an active shared lock.
Try the controls before locking them

Use self-control first to check permissions, app blocking, time limits, browser filtering, and release behavior. Leave optional release locks and one-way settings off while testing. AI Coach can assist with supported controls when its access is enabled, but cannot grant Android permissions for you.

Where and when can I access Device Control?​

In the Android app, open the main menu and choose Parental Control under Quick Actions. This opens the Device Control page. The Devices shortcut is for external devices such as QIUI/Lockink, not your synced phones.

You can open Device Control before, during, and after a control session. Opening the page does not mean every action is available:

SituationWhat is available
No active Device Control sessionSet up permissions, start self-control, or remove another saved phone under Synced devices. Giving control to a keyholder also requires an eligible active shared lock.
Active keyholder controlReview status, permissions, and available consent controls. The controller manages restrictions; saved phones cannot be removed.
Ordinary self-controlUse Manage self-control to change rules, pause, or disable control. End self-control before removing a saved phone.
Self-control with an active release lockCheck the release condition and status. Ordinary settings changes, pausing, and disabling remain locked until release is allowed.
Website or iOS appAn authorized controller can manage an Android wearer's restrictions. Android permission setup and the wearer's Synced devices removal list require the Android app.

Synced devices appears when there are saved Android phone entries. It can remain visible during active control, but Remove is only offered for another phone after Device Control has ended. See removing a phone.

Share control with a second controller​

A primary phone controller can invite one other person through Overview → Session controls → Shared Phone Control. The person does not need a secondary-keyholder role or a linked lock. The wearer, primary controller, and invited person must all explicitly approve the same permissions before shared access starts.

Live screenshots and location are separate optional permissions, both off by default. The wearer and controller views identify everyone sharing control with avatars, usernames, and role labels. Secondary controllers can use Leave shared control under Session controls to leave without ending the primary session.

See the Second Phone Controller guide for invitation steps, included controls, privacy permissions, leaving or removing access, and FAQs. Secondary Keyholders covers the separate lock role.

Multiple Android devices​

The control session and rules belong to your Chastify account. Changing app restrictions, schedules, or limit settings applies the change across your controlled phones, so your controller can manage one set of rules. Separate rule sets for each phone are not currently supported.

Selecting a phone, including the phone named in the header, chooses which device's usage, installed apps, and status you inspect. It does not limit settings changes to that phone. Choose the correct device before reviewing its status or requesting screenshots.

The daily screen time allowance is separate for each phone. With a 5-hour daily limit, 2 hours of counted usage on Phone A leaves 3 hours on A, while 3 hours on Phone B leaves 2 hours on B. Neither phone has reached its limit, even though the combined usage is 5 hours. With no extra time granted, two phones can therefore use up to 10 hours of counted screen time between them. See the daily limit example.

Each phone still needs its own Android setup. See Multi-Device Support for sync, offline behavior, and removing an old device.

Temporary PLE app blocks​

During active Phone Control, the wearer can see Temporary PLE blocks below screen time on the Android Device Control page. The main controller can find the same list on Device control → Overview, including when managing self-control.

Each entry shows the app's reported icon and name, the restriction name chosen by the program, and time remaining. If the icon is missing or cannot load, a generic icon appears instead. Until released means the program must release that named restriction, or its originating session or authority must end. For example, Instagram might have phone-break with 20 minutes left and a separate task-reward restriction until released. Ending phone-break alone does not remove task-reward.

The overview is read-only and refreshes automatically. Expired, released, or no-longer-authorized PLE restrictions disappear; saved app blocks and other limits remain separate and can still prevent access. The countdown shows the server's expiry time, not confirmation that an offline phone has received the change. See temporary restriction blocks and examples.

Getting started​

1. Install the Android app​

Install the Chastify Android app on the phone you want to restrict. Device Control enforcement is Android-only; the website and iOS app do not provide these Android permissions or restrictions. A keyholder can still use Chastify's management interface to control an Android wearer device.

2. Open Device Control​

  1. Open Chastify on the Android device.
  2. Open the main menu, then Quick Actions → Parental Control to reach Device Control.
  3. Tap Start Setup and review the requested access.

3. Grant permissions​

The setup screen guides you through the permissions. Some steps open Android settings; return to Chastify afterward and refresh the status.

Permission or accessPurpose
Device AdminAdds protection against normal uninstall flows.
OverlayDisplays blocking screens over restricted apps.
AccessibilityDetects foreground apps and supported browser activity and enforces restrictions.
Usage StatsReads usage needed for screen time and per-app limits.
NotificationsShows ongoing status and control feedback.
Screen CaptureSupports screenshot capture where required by the Android version and capture method; screenshot sharing also needs Chastify consent.
Secure SettingsOptional ADB permission that allows accessibility recovery attempts.

Review battery optimization too, because Android background restrictions can interrupt enforcement or reporting. See HyperOS and Android Battery Restrictions for power-saving limitations and restoring protection afterward. Optional Device Owner setup adds stronger Android administration controls, but is not required for ordinary Device Control.

Secure Settings recovery​

Secure Settings lets Chastify attempt to restore its accessibility service if it is disabled during an active control session. It does not guarantee recovery from every Android permission or installer restriction.

Grant it from a computer with ADB and an authorized connection to your phone:

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

Return to Device Control and refresh the permission status. If accessibility is still blocked, check Android Restricted Settings.

4. Give control to a keyholder​

  1. Review the permissions and capabilities.
  2. Confirm that the screen shows the intended keyholder from your active shared lock.
  3. Tap Give Control to Keyholder.
  4. Review Privacy & sharing separately; Android permissions alone do not enable every sharing feature.

Your keyholder can then manage the controlled devices from their dashboard. If no eligible shared lock is available, use self-control or set up the intended shared lock first.

What keyholders can do​

Screen time limits​

Set daily screen time limits and review per-device usage. When a configured limit is reached, Chastify blocks applicable apps. Protected apps and the configured enforcement rules determine what remains available.

With multiple phones, the same limit is applied separately to each phone's counted usage. There is currently no combined allowance across devices. See how daily limits work.

On an updated Android app, the wearer can open Device Control → Today's screen time → Time limit warnings and select 5 minutes, 15 minutes, 30 minutes, or 1 hour. All options start unchecked. These preferences belong to the phone and do not change the controller's limits.

Warnings use the controller-message popup style and work offline while Device Control is active. They cover the daily counted allowance, including extra time granted today, and the app currently being used. Protected apps and paused control do not trigger warnings. Each selected warning appears at most once per device-local day for the daily limit and once for each app's limit; granting extra time does not repeat warnings already shown that day. Thresholds longer than the allowance are skipped. If a check catches several thresholds at once, only the nearest one is shown, with the current approximate time remaining. Checks run periodically, so warnings may appear slightly after a threshold is crossed. Controller popups take priority.

Time restrictions​

Configure allowed or blocked time windows. Check the phone's time zone and the schedule shown in the controls when investigating unexpected blocking.

App blocking​

Controllers can block specific apps, set per-app time or launch limits, and configure protected apps. Installed-app information helps identify which app to restrict. Review the protected list before enabling broad restrictions.

Recently installed apps lists apps that are already installed. With automatic blocking enabled, they remain blocked until approved. Choose Keep blocked to decline access and dismiss the review, or Approve to remove that app's block. An app that is not currently blocked offers Block app instead. These actions affect only the selected app; other time and usage restrictions can still apply.

Block All Apps and Allow All Apps are in a separate All installed apps section and ask for confirmation. They apply to the full app list. Wearer-protected apps cannot be blocked.

Request another protected app during control​

When another person controls your device, you can request protection for an additional app without ending the session:

  1. On your Android device, open Phone Control → Protected apps → Choose apps.
  2. Search for the app and select Request protection. You can have one pending request at a time.
  3. Your controller sees the pending request at the top of your Device control page and receives an ordinary notification, without an automatic full-screen popup. Tapping the notification opens the request for review. They can review the app icon, name, and package, then choose Approve protection or Decline from either view. Icons also appear in the app picker and your request status when available.
  4. Reopen the picker to see the request status. While it is open, the status refreshes automatically. An approval triggers a device sync; an offline device receives the change when it reconnects and syncs.

Requesting an app does not change blocking or limits. Approval adds it to your persistent protected list across your devices, exempting it from app blocks, app time and launch limits, time windows, and daily screen-time enforcement. Protection remains after the control session ends, until you remove the app from the protected list.

An unanswered request expires after seven days or when the control session ends or changes. A former controller cannot approve a pending request for a new session. Self-control and AI/bot-managed sessions do not use this approval flow. Existing protected apps can still be removed.

Browser control​

Browser controls include adult-site filtering, blocked domains, allowlist mode, recent activity, and blocked attempts. Coverage depends on the browser and enabled enforcement method. Optional content-filtering or VPN controls have their own availability, permission, and locking conditions; check the controls shown on the phone.

Screenshots​

Screenshots require explicit Screenshot consent, active control, and a working capture service on the selected Android device. The controller cannot request screenshots while consent is disabled.

Consent can cover both live requests and periodic captures for recent screenshots. On supported Android versions, Chastify keeps up to nine recent periodic captures in the phone's local app storage and can send a contact sheet to the controller. This is broader than a single live screenshot request.

Prevent screenshots in protected apps skips live and periodic captures while a protected app or Android notification surface is visible. Enable and review this privacy setting separately. Android's own protected-screen behavior can also prevent capture.

Consent can be locked for the control session

Screenshot consent, location sharing, and wallpaper consent have controls that can prevent disabling an already-enabled option for the rest of the control session. Do not assume an enabled sharing toggle will always remain reversible. Review its lock state before granting access.

Location and wallpaper​

Location sharing allows the controller to see current location and location history when enabled and the phone has the required permission. Wallpaper consent permits the controller to set an enforced wallpaper. These are separate from screenshot consent and each other.

Privacy information​

Data Device Control may collect​

Depending on enabled features, Device Control uses:

  • Installed app names, package names, and icon information.
  • Device identity, permission status, connection status, and sync information.
  • Screen time, app usage, and blocked app attempts.
  • Browser URLs or domains and blocked website attempts.
  • Live and recent screenshots when screenshot consent is enabled.
  • Location and location history when location sharing is enabled.

Limits of privacy protection​

Screenshot sharing requires consent, but a permitted capture can include anything visible on the screen, including messages, payment details, or other sensitive content. Browser activity can also contain sensitive URLs. Do not interpret app blocking or a protected-app list by itself as a promise that all private information is excluded from sharing.

Review Privacy & sharing, consent locks, and Prevent screenshots in protected apps with your controller before enabling them.

Retention​

Ending control stops the controller's management access and resets active per-device usage and enforcement status. It does not remove every synced-device record: device inventory can remain available for later setup and management.

Recent screenshots are a limited local archive, not just an image passing through a live request. Older captures are replaced as new captures are saved. Disabling consent blocks further authorized capture and requests, but should not be treated as confirmation that previously stored captures have been erased.

Browser, usage, and location history have their own feature-specific retention. Ending control is not the same as deleting your Chastify account or all historical data.

Persist after lock session​

The setting shown as Keep device control after lock ends (also called Persist After Lock Session) keeps keyholder control active after the related chastity lock ends. The same keyholder remains your Device Control controller, not just the person whose saved restrictions are still applied. This also applies to timer-based chastity locks: ending the lock does not end persistent Device Control.

One-way setting

Enabling this requires Hardcore mode consent. Once enabled, it cannot be switched off for that control session, and the wearer cannot use the ordinary end-control action to release persistent keyholder control. The controller must end it, unless an eligible recovery flow applies.

This differs from a Self-Control Release Lock. Self-control can be locked until a timer expires or an associated active lock session ends. Those conditions can also prevent pausing or ending self-control; review them before confirming. See Self-Control & Release Locks for setup, extensions, and release instructions.

Starting another lock​

Starting another chastity lock does not reset persistent Device Control or automatically give a different keyholder control of your phone.

When you start a new shared lock that requires Device Control:

New lock's keyholderWhat happens while persistent Device Control is still active
The same keyholderThe existing Device Control session is reused and linked to the new lock. The keyholder stays in control, and Keep device control after lock ends remains enabled.
A different keyholderThe new lock cannot start with Device Control because it would replace the existing controller. End the existing Device Control session before assigning control to someone else.

The ordinary release rule still applies: the existing controller must end persistent control, unless an eligible recovery flow applies. Ending only the old chastity lock is not enough.

Managing Device Control​

Open Device Control to review the controller, self-control state, current device's usage, restrictions, browser rules, privacy choices, permissions, and sync status. For multiple phones, inspect the intended device rather than assuming all entries have identical permissions or connectivity.

When a permission is missing, follow its row to Android settings and return to recheck. Some setup and protection controls are deliberately locked while a session is active; see Device Ownership for its setup and recovery restrictions.

Releasing control​

Use the end-control action when the current release rules allow it. Persistent keyholder control and self-control release locks impose the conditions described above.

After control ends, the controller loses management access and connected phones receive the release. An offline phone may continue enforcing its last received state until it reconnects and processes the release. Open Chastify on each phone, restore its connection, and confirm restrictions are actually removed.

Ending the session and removing optional Android administration setup are separate actions. If Device Owner is enabled, follow its recovery guide rather than assuming all Android protections disappear immediately.

Inactive controller recovery​

When a human controller has been inactive long enough for Chastify to offer recovery, the Parental controller inactive prompt lets you continue with that controller or remove them. The app shows the applicable inactivity period.

Remove controller keeps Device Control running under your own control, so you can review or change restrictions and end control yourself. It does not end or transfer ownership of a separate chastity lock.

Check release on the phone

Network loss, Android permissions, manufacturer restrictions, and device restarts can affect enforcement and recovery. Test release behavior before enabling restrictive settings and keep a practical recovery route.

Keyholder access​

  1. Open the lock or keyholder dashboard after the wearer grants control.
  2. Choose Device Control.
  3. Select the Android device you want to inspect if more than one is synced.
  4. Configure shared rules and review that device's usage and permissions.
  5. Check consent and the selected device before requesting screenshots or location.

Troubleshooting​

Device offline​

Ask the wearer to open Chastify on that phone, restore internet access, confirm accessibility is running, and use manual sync. Check battery optimization and background restrictions if reporting stops when the app is closed. An online account or another online phone does not prove that the selected device is connected.

Permission issues detected​

  1. Open Device Control on the affected Android device.
  2. Check the permission status and follow the missing permission's setup action.
  3. Return to Chastify and refresh or sync.
  4. If the permission is grayed out, check Restricted Settings below. If it appears granted but inactive, reopen Chastify and check the service status.

Android Restricted Settings​

On Android 13 and newer, some installations can trigger Restricted Settings, preventing accessibility access. If Android shows this restriction, open Settings → Apps → Chastify → More → Allow restricted settings, then return to Accessibility and enable the required Chastify service. Menu names vary by Android version and manufacturer.

Only grant this access if you trust the installed app. See Google's Restricted Settings instructions. Secure Settings recovery and Device Owner do not guarantee that this installer restriction is bypassed.

Banking or payment app will not open​

Some apps refuse to operate while a sideloaded app has an accessibility service enabled, even when they are in Protected apps. Chastify cannot override another app's security restrictions. See Banking and Payment App Compatibility for more about these restrictions and where to get help.

Frequently asked questions​

How do I remove a phone from Device Control?​

When you have no active Device Control session:

  1. Open Chastify's Android app on a different phone, signed in to the same account.
  2. Go to Device Control → Synced devices.
  3. Find the phone you want to remove and choose Remove.
  4. Confirm Remove device.

The phone marked This device cannot remove its own entry. Removal forgets the saved entry; it does not end a session or change settings on that phone. See Multi-Device Support for the full removal checklist.

Why is Remove missing?​

  • Device Control is still active: end the keyholder-control or self-control session first, subject to its release rules. Pausing restrictions does not end the session.
  • The entry says This device: use another Android phone signed in to the same account.
  • You cannot find Synced devices: use the Android app, not the website or iOS app. The section only appears when saved phone entries exist.

Having no active chastity lock does not necessarily mean Device Control has ended. Persistent keyholder control or a separate self-control session can still be active. Check release rules or ending self-control.

Why did a removed phone reappear?​

If Chastify is opened and syncs again on that phone, it can register another saved entry. Remove does not sign the phone out, uninstall the app, or prevent future syncing.

Can I remove just one phone during an active session?​

No. The Device Control session and rules belong to the account, and removing saved phones is unavailable while that session is active. Selecting a different phone changes the usage and status you inspect, not which phone the shared rules apply to. See shared rules and per-device usage.

Does removing a phone also remove Device Owner?​

No. Forgetting a synced entry, ending Device Control, and removing Android's optional Device Owner role are separate actions. Follow Clearing Device Owner if you want to remove that role from the phone.

Why is my phone still restricted after control ended?​

First check that Device Control itself has ended, rather than only its linked chastity lock. An offline phone cannot receive a release immediately. Reconnect the affected phone, open Chastify, and use Sync protection status under Protection recovery. Confirm the restrictions clear on each phone before removing old entries.

If restrictions remain after a successful release and sync, contact Support with the phone model, displayed control state, and the action that failed.

Can I uninstall Chastify while Device Control is active?​

Device Admin can block normal uninstall flows, and optional Device Owner protections can add restrictions on uninstall, force-stop, or clearing data. Do not assume uninstalling is an available release method during a session. See Device Ownership for the supported setup and recovery controls.

What happens when my lock ends?​

Keyholder Device Control normally ends with its linked lock, unless Keep device control after lock ends is enabled. A self-control timer lock can keep self-control active until its own release time; a session-bound self-control release lock follows the associated session. A separate self-control session is not automatically tied to every chastity lock.

After a release, reconnect any offline phones and verify their local state. See Multi-Device Support.