Why Device-Level Controls Work When Platform Bans Fail

Short answer: a platform ban asks a company that profits from your child to keep your child out. A device control doesn't ask anyone.

That's the whole difference, and it's why one keeps failing and the other doesn't.

Set up device-level controls →

Two places to enforce a rule

Australia banned under-16s from social media. Karnataka followed. Both revealed the same thing: where a rule is enforced matters more than what the rule says.

A platform ban depends on each company verifying age, choosing to enforce honestly, and children not finding a way round. Every one of those is out of your hands.

A device control depends on what's actually installed on the phone in your child's pocket. That one isn't.

Why platform-level enforcement keeps failing

Verification is weak by design. A self-reported birth date is a text box. Facial age estimation is defeated by an angle and a bit of makeup. ID checks are rare, because most people won't hand a social network their passport.

The predictable result: a 15-year-old signs up as a 17-year-old and nobody asks anything.

The incentives point the wrong way. Every account is potential ad revenue. A company will do what avoids a fine, not what protects a child. Expecting more than that is expecting a business to work against itself.

And it's whack-a-mole regardless. Ban Instagram and there's a next app. Ban that and there's another. New ones launch monthly, so any list of named platforms is out of date the day it's published.

What a device-level control sees

It's installed on the phone, so it sees the phone:

• Every app that's installed, including ones you've never heard of
• Actual minutes in each one, not what anyone reports
• Web activity in every browser, including private tabs
• The trend over weeks, which is where the real signal lives

The difference in practice looks like this. Platform approach: child enters a fake birth date, account created, parent never knows. Device approach: child installs the app, parent is alerted, the app is blocked or allowed with the usage visible.

One hopes children don't lie. The other assumes they might and works anyway.

And it catches the migration

This is the part platform bans structurally cannot do.

When Australia's ban pushed children off YouTube, their screen time didn't drop — it moved to Netflix and Spotify. By the ban's own measure that was a success: the platforms were blocked. By any measure a parent cares about, nothing happened.

If your goal is fewer hours rather than fewer logos, only device-level visibility tells you whether you got them.

What the controls can actually do

Beyond visibility, on the device:

• Block an app outright — it simply doesn't open
• Cap it — an hour of social, then it stops
• Bedtime — the phone locks on schedule, with calls, messages, alarm, maps and calculator still working
• Filter the web — 31 categories, 14 blocked by default, enforced in every browser including incognito and on mobile data
• Schedule it — restricted windows for homework, school hours and bedtime, set per day of the week

And the balance that keeps it usable with a teenager: you see which apps and how long, not what was said in them. ParentalEdge doesn't read messages. That's a deliberate limit, and it's what makes the arrangement survivable past about thirteen.

Bans still matter — just not for what you think

We're not arguing they're pointless. A ban does something no app can:

It makes "everyone has it" untrue. It gives your rules social backing so you're not the only strict parent in the class. It creates legal liability for platforms. And it shifts what a whole cohort considers normal.

Think of it as the school's no-phones-in-class rule. Genuinely useful. Also not a substitute for knowing what's on the phone.

Use both. Let the ban take the peer pressure off. Let the device enforce what you actually decided.

What to look for in any app you consider

What to avoid: anything that only covers one operating system, anything that needs you to check it manually every day, and any "kid mode" a determined ten-year-old can exit.

Frequently asked questions

Can a VPN get round device-level controls?
No. VPNs defeat geographic and network restrictions, not controls running on the device itself. VPN apps are blocked as apps too, and installing one shows up as an alert.

Isn't this too invasive for a teenager?
It's adjustable — with a 16-year-old most families run visibility only, no blocks, and use it for conversations. And there's no hidden mode: your child knows it's there, which is the setting that makes it defensible.

Karnataka has a ban. Do I still need this?
Yes, for the same reason Australian parents did. The ban obliges platforms to verify age; it doesn't change your child's phone this week. Full Karnataka guide.

How is this different from Google Family Link?
Family Link does app blocking and screen time limits, free, and does them fine. What it doesn't do is filter the web by category, force Safe Search across five engines, report YouTube titles and channels, or work across Android, iOS and macOS from one dashboard. Detailed comparison.

Enforce it where it actually works →

Related: what Australia's ban really showed.