Why this matters:How to recognise this workaround on your side, and what closes it on your side — without telling you how to do the workaround.
Detection
The child uses Android, Chromebook, iPhone/iPad, Windows, Mac or Linux beyond the parent’s inventory.
Fix (technical)
Google says a supervised child account can sign in to Chrome on those device classes; eSafety says controls need configuration on all devices the child accesses. Maintain an inventory and set the appropriate control per device. [google-chrome-child-account; esafety-parental-controls]
Fix (relational)
Treat disclosure of a new device as a normal safety conversation, not an automatic penalty.
Residual risk
An inventory cannot automatically discover every borrowed or public device.
Sources
-
google-chrome-child-account
-
esafety-parental-controls
Why trust this page?
Belief-disclosure in plain language. Everything the page claims is sourced; instructions are tested against the software version stated above; nothing is bought or affiliate-linked.
- Standing of evidence
- Primary (first-hand or regulatory source)
- Last verified
- 2026-08-16
Sources used on this page, in the order they appear:
- No external sources were cited.