Multi-Device Support
Overview
Device Control can sync more than one Android device for the same Chastify account. Install Chastify, sign in to the same wearer account, and complete Device Control setup on each phone.
This is useful when a wearer has a main phone and a spare phone, an emulator used for testing, or a replacement phone that is being prepared before the old phone is retired.
The important rule is:
- Device Control session and rules are account-level
- Usage, app inventory, permissions, and runtime status are device-level
Selecting a phone changes the usage and status you inspect. The phone named in the header identifies the device being viewed; settings changes still apply across the wearer's controlled phones. This lets the controller manage one set of rules without configuring each phone separately. Separate rule sets for individual phones are not currently supported.
The same applies to Self-Control Release Locks: switching to another synced Android phone does not reset the account's release timer or session condition.
What is shared across devices?
The active Device Control session is shared for the wearer account. These settings normally apply to every synced Android device:
- Daily screen time limit setting
- Time windows
- Blocked apps
- Protected or always-available apps
- Browser control settings
- Adult-site filtering settings
- AI Content Shield settings, where available
- Screenshot, location, and wallpaper consent state
- Self-control or keyholder control state
If the controller blocks an app, enables browser filtering, or changes the daily screen time limit, the change is intended to sync to all active Android devices for that wearer.
Shared consent does not grant Android permissions on another device. Accessibility, Usage Access, overlays, battery settings, and any requested capture or VPN permission must be set up on each phone. Optional Device Owner provisioning and protections are also configured separately on each phone.
What is tracked per device?
Each Android device reports its own runtime data:
- Device name and model
- Online or last-seen status
- Today's screen time
- Today's app usage
- Installed apps
- Permission health
- Device Owner status
- AI Content Shield runtime status
- Family VPN runtime status
- Browser blocking runtime status
The keyholder view uses the selected device's latest report when showing usage and health status. A saved device entry is not proof that the phone is currently connected or enforcing every control.
How daily limits work
Each phone gets its own daily allowance using the same limit setting. Usage on one phone does not reduce the allowance on another phone. There is currently no combined daily allowance across devices.
For example, with a 5-hour daily limit and no extra time granted:
| Phone | Counted usage today | Time remaining |
|---|---|---|
| Phone A | 2 hours | 3 hours |
| Phone B | 3 hours | 2 hours |
Neither phone has reached its limit, even though the combined usage is 5 hours. Phone A reaches its limit when its own counted usage reaches 5 hours; Phone B does the same independently. Two phones can therefore use up to 10 hours of counted screen time between them under this setting. Protected-app use remains exempt, and other restrictions can still apply.
The same model applies to app screen time limits and app launch limits: the rule is shared, but each device tracks its own usage and launches. Extra daily screen time granted to the account changes the shared allowance; each phone still subtracts only its own counted usage.
Extra time is dated using the most recently reporting Android phone's local day. On each phone, the grant counts only on that calendar date and expires at local midnight. The displayed remaining time uses the selected phone's timezone too. If your phones use different timezones, they can enter or leave the grant's calendar date at different times.
How app blocking works
Blocked apps, protected apps, and browser rules are shared across the active Device Control session.
If a blocked app exists on more than one synced Android device, Chastify attempts to enforce the block on each device. If an app only exists on one device, it only affects that device.
Protected apps are still available when screen time is exhausted. Time spent in protected apps is not counted against the daily screen time limit.
Keyholder view
If a wearer has more than one synced Android device, the keyholder dashboard can show multiple Device Control entries for the same wearer.
Use the device label to identify the phone, for example:
- Samsung Galaxy S24+
- Google Pixel 8
- Android Emulator
Open the device you want to inspect before reviewing usage, installed apps, permission status, or Device Owner status. Check Last synced as well as the online indicator when deciding whether the report is current. Changes to shared session settings still affect the other synced phones.
Wearer setup view
On Android, the Device Control setup page shows the current device's state.
If the same wearer opens Chastify on another Android device, that device reports a separate status snapshot after it syncs. This lets Chastify distinguish between the main phone, a spare phone, and test devices.
The Synced devices section lists saved phones, marks the current phone as This device, and shows each phone's online state and last sync time.
When is Synced devices accessible?
Open the Android app, then the main menu's Quick Actions → Parental Control to reach Device Control. Scroll to Synced devices. The list appears when your account has saved Android phone entries, including after control has ended. The website and iOS app do not show this wearer removal list.
The list can be viewed during an active Device Control session, but removing phones is unavailable until that session ends. The current phone, marked This device, never offers removal from its own list.
Remove an old device
To remove a phone, go to Device Control → Synced devices when no Device Control session is active. Use a different Android phone signed in to the same wearer account.
- End the Device Control session according to its release rules, or disable self-control. Pausing restrictions is not enough.
- Reconnect the old phone if possible and let it sync the release. Check that its session restrictions have cleared.
- On an Android phone you are keeping, open Device Control → Synced devices.
- Identify the old phone by its label and last sync time. Choose Remove, then confirm Remove device.
Here, “no active session” means no active Device Control session, not merely no active chastity lock. Keep device control after lock ends and separate self-control sessions can keep phone control active after a lock ends.
If Remove is missing, check that control has ended and that the entry is not marked This device. You cannot use a phone to remove itself. If you no longer have another Android phone available and need help with a saved entry, contact Support.
Removal only forgets the saved entry. It does not remotely release restrictions, wipe the phone, sign it out, uninstall Chastify, or remove Device Owner. The old phone does not need to be online for its entry to be removed, but deleting its entry does not confirm that it received the release. If Chastify opens and syncs again on that phone, it can reappear.
Ending control
Ending Device Control ends the shared session. Each phone must receive and apply the updated state to clear its session restrictions. Keep the phones connected and open Chastify on any phone that still shows old restrictions; an offline phone cannot process a remote release immediately.
Chastify keeps saved device information such as the name, app inventory, and last report time, while clearing the session's reported usage and active runtime flags. You can remove old entries afterward using Synced devices.
Ending control does not remove the optional Device Owner role. See Clearing Device Owner for that separate action.
Web fallback records
Device Control enforcement is Android-native. Opening Chastify in a web browser or the iOS app does not turn that device into an Android Device Control target. Web-only activity can provide limited account status, but it does not replace a report from a synced Android phone.
Use the Android device entries when checking enforcement. A keyholder can manage the account through the web interface, while the controlled phone runs the Android app.
Troubleshooting multiple devices
If a device is missing:
- Open Chastify on that Android device.
- Confirm that it is signed in to the same wearer account, then open Device Control.
- Check that the required permissions are granted on that phone.
- Use the manual sync action and check its result.
- Return to the keyholder view and refresh.
If one device looks stale or offline, it does not necessarily mean every device is offline. Check each synced device separately.
If the wrong apps or usage appear, reopen the intended device entry and compare its label and last sync time. For delayed updates, check the phone's internet connection and Android battery restrictions. If controls remain after a successful release and sync, contact Support with the affected phone's model and the action that failed.