Skip to main content

Multi-Device Support

Overview​

Device Control can sync more than one Android device for the same Chastify account.

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

This prevents one phone from overwriting another phone's live status while still letting the controller manage the wearer with one shared rule set.

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
  • Screenshot and location 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.

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 runtime data when showing usage and health status.

How daily limits work​

The controller sets one daily screen time limit, but each Android device tracks usage separately.

Example:

  • Daily limit is set to 4 hours.
  • Phone A has used 3 hours today.
  • Phone B has used 30 minutes today.

Phone A has 1 hour remaining. Phone B has 3 hours and 30 minutes remaining.

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.

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 may show multiple Device Control entries for the same wearer.

Each entry should use the device label when available, 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 hardening.

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.

Ending control​

When Device Control ends, active restrictions are removed for the session.

Chastify may keep device inventory data such as device name, installed apps, and last report time. This helps identify devices and makes future setup easier. Active runtime lock state should not remain after the control session has ended.

Web fallback records​

Device Control enforcement is Android-native. Browser or web-only sessions may create limited fallback status records, but those records are not real controllable Android devices.

For actual Device Control actions, use Android devices reported by the Chastify Android app.

Troubleshooting multiple devices​

If a device is missing:

  1. Open Chastify on that Android device.
  2. Go to Device Control.
  3. Check permissions.
  4. Run manual sync if available.
  5. 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.