How Anchor holds ยท Route 03

My kid factory reset the device. Now what?

Yes, a factory reset removes most parental control apps completely. The wipe defeats Bark, Qustodio, Family Link, and Mobicip the same way. Anchor takes a different approach: the Child app survives a reset because re-enrollment is required before the device leaves setup, and the parent feed shows the reset event.

Factory reset is the bypass route that removes most parental controls completely. Anchor's verdict is Partial: the wipe itself succeeds, but parent-side pair persistence forces re-pairing through the parent's six-digit code.

See the bypass route Read the Bypass Test

The most destructive bypass route on Android parental controls is factory reset. Open Settings, navigate to System, then Reset options, and tap Erase all data (factory reset). After confirmation, Android wipes the device. The parental control app, the configured rules, the activity history, and the bind to the parent account all disappear with the wipe. Per Anchor's Bypass Test methodology, Bark, Qustodio, and Family Link all fail Route 3 (factory reset) because the bind lives entirely on the device. Anchor's verdict on this route is Partial: the wipe itself succeeds, but parent-side pair persistence preserves the binding on the parent's side. The newly wiped device cannot re-pair without the parent's six-digit code, which only shows in the parent app. The kid ends up with a freshly wiped device that cannot connect back to Anchor and a parent who sees a sudden device-unbound event in their feed. Anchor is Android-exclusive at present, with other platforms on the roadmap without committed timing.

The exact route

What your kid does, step by step.

Four steps through Settings on a standard Android device. No root access, no special tools, no recovery-mode procedure required. A kid willing to lose all their data to lose the parental control can complete this in under three minutes.

  1. 01
    Open Settings → System

    Settings, then System on stock Android. Samsung One UI nests the same destination under General management → Reset. Other OEMs vary similarly. All paths lead to the Reset menu.

  2. 02
    Tap Reset options → Erase all data (factory reset)

    Android may show "Reset phone" or "Erase all data" as the label. Same outcome. Some Android versions require the device PIN or pattern to be entered before reaching this screen. If the kid knows the device PIN, the screen unlocks.

  3. 03
    Confirm the wipe dialog

    Android shows a wipe-confirmation screen listing what will be erased. The kid taps Erase all data. On most devices, a second confirmation appears. The kid taps it. The wipe begins.

  4. 04
    Wait roughly two minutes

    The device reboots, runs the wipe process, and boots into the initial setup screen. The parental control app is gone. The configured rules, history, and account bind are gone with it.

Factory reset is the cleanest bypass for a kid willing to lose all their other data. The device returns to initial setup state. Apps, photos, accounts, settings, all of it wipes alongside the parental control.

The structural gap

Why most parental controls fail this route.

Bark, Qustodio, and Family Link store the device-to-parent bind on the device. The configured rules, the activity log, and the device identity used to pair with the parent account all sit in the app's local data. When Android wipes the device, that data is gone. The parental control vanishes with the wipe.

Where the failure happens: on the next boot, the device is in a fresh state. The kid can complete initial setup with a personal Google account instead of the family account. With no parental control installed, no Device Admin enrolled, no accessibility service running, the device functions as an unmanaged Android device. The kid has effectively traded their other apps and data for an unrestricted device.

The structural gap is that the bind was device-side. Per the Bypass Test methodology Route 3 verdicts, Bark, Qustodio, and Family Link share the same outcome: the wipe succeeds, the bind disappears with the wipe, the device re-emerges unmanaged. The parent dashboard shows a sudden disconnect. The kid shows up with a freshly set-up device and a story about Android needing an update.

How Anchor closes it

Layer 03: Parent-side pair persistence.

03 Attack: factory reset

Wipe succeeds. Re-pairing requires the parent code.

Parent-side pair persistence means the device-to-parent binding lives encrypted on the parent's side of Anchor, not exclusively on the device. The factory reset still erases the child device. That part Anchor cannot prevent and does not claim to prevent. What Anchor's pair persistence prevents is silent reconnection. After the wipe, the freshly initialized device cannot pair back to Anchor without the parent entering a six-digit code from the parent app.

The result is the kid ends up with a device that no longer has Anchor installed, but also cannot re-pair. The parent sees a device-unbound tamper event in the activity feed within minutes of the wipe. The conversation that follows is unavoidable: the parent knows a wipe occurred, the kid cannot present the device as still managed, and re-pairing requires the parent to type a code that only the parent app shows.

Verdict: Partial Anchor closes the silent-bypass path. The wipe itself happens.

The full moat

Layer 03 in the four-layer context.

This route is the third of four bypass attempts Anchor was engineered against. The other three layers close the uninstall route, clock manipulation, and offline tamper hiding.

01 Tampering

Watchdog-protected Device Admin

Uninstall and permission revocation defeated by continuous watchdog plus OS-level rejection.

02 Clock

Server-truth time

Schedule enforcement runs on backend time. Device clock manipulation has no effect.

03 Reset

Parent-side pair persistence

Reboot does not unlink. Factory reset removes Anchor Child, but re-pairing requires the parent's six-digit code.

04 Offline

Offline tamper queue

Tamper events queue locally with original timestamps and flush to the parent app on reconnect.

What this means

For your household.

Your kid can still factory reset the device. The Android wipe is a hardware-level OEM feature. Anchor does not have OS-level access to prevent a factory reset, and no parental control app on Android can. The wipe will succeed.

What changes is what happens next. The device boots into initial setup with no managed account, no Anchor binding, and no path to silently re-pair. Your Anchor parent app shows a device-unbound event within minutes of the wipe. You know. The kid cannot return the device to a managed state without you entering the six-digit pair code that only your app displays.

A factory reset becomes a visible event. Not a silent escape. The conversation that has to happen, happens.

See Anchor pricing Join the Founders Offer

Compare against the major Android parental controls

Side-by-side coverage of how Anchor stacks up against the four major Android parental control products on this route and the others.

Bark vs Anchor

Content surveillance vs bypass-resistant enforcement.

Qustodio vs Anchor

Engagement reports vs enforcement that holds.

Family Link vs Anchor

Google's free option vs Anchor's enforcement layer.

Mobicip vs Anchor

Cross-platform basics vs Android bypass resistance.

How Anchor holds, the other routes

Per-route deep dives on the other three bypass attempts Anchor was engineered to close, plus the consolidated bedtime entry point.

Uninstall block

Watchdog-protected Device Admin in detail.

Clock change defense

Server-truth time in detail.

Permission revocation defense

The continuous watchdog in detail.

Bedtime bypass routes

All four routes through a bedtime lens.

Or read the full Bypass Test methodology for the verdict table across all four routes and four competitors.

FAQ

About this route.

No. Factory reset is a hardware-level OEM feature on Android, controlled by the device settings menu and the recovery boot menu. Anchor does not have OS-level access that could prevent a factory reset, and no parental control app on Android can. What Anchor prevents is silent re-pairing after the wipe.
The Anchor parent app shows a device-unbound tamper event in the activity feed within minutes of the reset. The event is timestamped and persistent. If the device is offline at the moment of the wipe, the unbinding is detected the next time the parent app polls the backend, and the event still surfaces.
No. Re-pairing requires the parent's six-digit pair code, which only shows in the parent app. The freshly wiped device cannot connect to a child account on Anchor without that code. Until the parent enters it, the device remains in an unbound state from Anchor's perspective.
The device can complete Android initial setup with any Google account, and the kid can use the device as an unmanaged Android device. Anchor does not enforce on devices that are not paired. The device is no longer managed and no longer counts against the Anchor family device limit. To re-establish enforcement, the device needs to be paired back to Anchor with the parent's six-digit code. Until then, the parent has visibility that a wipe occurred but no enforcement on the wiped device.