Ofcom Sets Out Age-Check Approach to Keep Under-16s Off Social Media

What happened

Ofcom, the UK communications regulator, has set out how it wants social media platforms to keep under-16s off their services, with the restriction expected to take effect from a point next year. As reported by TechRadar, the regulator's explanation centres on age-check plans, and privacy experts quoted in the coverage are not yet convinced the approach will work without creating new risks.

The reporting treats the proposals as an operational question: how platforms would verify age in practice, not only whether a restriction should exist. TechRadar's framing suggests the debate has moved from policy intent to the mechanics of enforcement, where the practical consequences for users and providers become much harder to ignore.

The material available to us does not give a full technical specification or a confirmed start date, so this briefing sticks to what the reporting establishes.

Why it matters

Age assurance is, at heart, an experience design problem. Every checkpoint a platform introduces changes the journey for users of every age, from sign-up and login to the moment a young person is asked to prove something about themselves. When those checkpoints feel slow, opaque or intrusive, they tend to produce abandonment, workarounds and distrust, which is the opposite of what a regulator hopes to achieve.

For leaders in digital transformation, the story is a reminder that regulation of online services is increasingly defining requirements for identity, verification and data handling. Organisations that treat compliance as a late-stage technical addition may find those systems expensive to redesign once the rules are fixed.

The Renascence take

Most coverage of this kind centres on the age limit itself. The more consequential design question sits underneath it: how the verification step is built, what it asks of people, and what happens to the data it generates.

Most readers will focus on the age limit, but the harder question is whether the checks needed to enforce it create new data risks for the very users they are meant to protect. The behavioural principle underneath is that friction is never neutral; when verification feels disproportionate, people look for ways around it, and a rule that is routinely bypassed protects no one. A customer-obsessed operator should design age assurance as a visible, minimal and explainable step, test it with real users, and be explicit about what is and is not retained. Waiting for the final rulebook before thinking about the user journey is the mistake to avoid.