I’m writing this from New York, where Apple’s WWDC 2026 keynote has just wrapped up, and the timing of everything that happened on Monday 9 June is genuinely hard to ignore. On the very same day, at London Tech Week back in the UK, Prime Minister Keir Starmer stood up and gave Apple, Google, and others a three-month ultimatum: activate device-level controls to stop children taking, sending, or viewing sexually explicit images, or face legislation. Same day. Not days apart. The same Monday. And Apple rolled out a significant parcel of child safety features as part of iOS 27. You can see why politicians are already reaching for the megaphone.
What Apple Actually Announced, and Why It Matters
The headline change is a properly guided Child Account setup for under-13s, with age-based safeguards built in from the start. More importantly, Apple is now extending similar protections to 13 to 17 year olds, regardless of whether their account was originally set up as a Child Account or a standard Apple Account. That closes a gap that has frustrated parents for years. A teenager who set up a standard Apple Account previously got adult-level defaults. That changes with iOS 27.
The features that caught my attention most are the practical ones. Ask to Browse means a child trying to visit a new website in Safari has to ask a parent first, and it works across iPhone, iPad, and Mac. That is exactly the kind of granular control that matters when your kid is getting online younger and the risks are moving faster than school internet filters can track. Time Allowances add category-based limits across entertainment, games, and social media, with recommended daily limits based on a child’s age developed with input from child development experts. That is smarter than a single blunt daily cap. Not all screen time is equal, and it is good to see Apple acknowledging that. Contact Approval lets parents manage who their children can communicate with across Messages, FaceTime, and Phone, including requiring approval before any new contact is added. Communication Safety, which already blurs nudity in Messages and FaceTime and is turned on by default for users under 18, is expanding to cover gore and violent video content too.
There are a couple of developer-facing additions worth mentioning as well. Apple is introducing a privacy-focused Declared Age Range API that lets apps tailor content based on broad age ranges rather than a child’s exact age. And a new PermissionKit framework will let kids send requests to their parents to chat, follow, or friend users in third-party apps. Scheduling tools will also let parents choose which apps are available at different times of the day, so educational apps can stay accessible during school hours while entertainment and gaming are restricted until later.
These are genuinely useful tools. They are not live yet. They arrive in autumn 2026 as part of iOS 27, iPadOS 27, and macOS 27. But the direction of travel is the right one.
The Political Timing, and Why It Gets Complicated
Here is where I am going to be straight with you, because this is the bit that matters beyond the feature list.
Apple does not design, build, test, and announce major iOS privacy infrastructure in a single morning because a Prime Minister made a speech a few hours earlier. These features were on Apple’s roadmap long before Starmer stood up at London Tech Week. The idea that Labour’s deadline conjured this update into existence is not credible, and anyone suggesting otherwise is playing politics rather than making policy.
That said, the question of what Labour is actually demanding versus what Apple has announced is worth unpacking carefully. Starmer’s ask is specific: prevent children from taking, sharing, and viewing nude images at a device level. As he put it, “This is not an impossible challenge. These are some of the most innovative companies in the world and I believe they can solve it.” The government has said it will bring forward legislation to force compliance if companies do not act voluntarily within three months, with potential fines or, as a last resort, criminal liability. The changes would apply to both existing and newly sold smartphones and tablets in the UK, and legislation could cover operating system providers and others in the supply chain, including retailers.
Apple’s Communication Safety can blur and warn in certain Apple-controlled contexts, but there is a meaningful gap between a safety warning that a teenager can still choose to dismiss and a hard block that works across every app, every camera roll action, and every third-party messaging route on the device. Apple has not publicly described a system that blocks camera capture, saving, search, or image sharing across third-party apps at a device level. The government is aiming for that kind of comprehensive blocking. Apple has announced progress toward warning and intervention in supported contexts. Those are not the same thing. If implemented, the UK would become the first country in the world to require specific measures like these from device manufacturers and operating system developers.
Privacy groups are already pushing back hard. James Baker, the Open Rights Group’s Platform Power Programme Manager, has warned that this “would turn every phone into a surveillance device.” The government denies the move amounts to surveillance, but that is not a fringe concern. When you build systems capable of scanning and blocking image content at the OS level, you are creating architecture that, once in place, can be asked to do other things. Governments change. Priorities shift. Expanding Apple’s current family-account system to mandatory, universal child protection means building infrastructure that could, in theory, morph into something broader. These are legitimate questions that deserve more than a three-month deadline and a press release.
The three-month clock also runs into a practical wall. iOS 27 is not landing until autumn 2026. Even Apple’s own roadmap does not fit neatly inside Starmer’s timeline, and that is Apple, the company arguably furthest along on this work. Google has said it is working “constructively” on privacy-preserving solutions, but has not committed to specific features or timelines.
My Verdict
I want these tools to exist. I genuinely do. My youngest is 13, I have teenagers in the house, and the conversation about what they encounter online is one I have every week. The Ask to Browse feature alone would have been useful two years ago. Apple’s autumn update looks like a serious step forward, and I will be setting it up the moment iOS 27 lands. But I am not going to pretend that a government speech caused it, and I am not willing to wave away the privacy concerns just because the stated goal sounds obviously good. The gap between “we want children protected from explicit images” and “here is a technically sound, privacy-respecting system that actually achieves that without creating new risks” is enormous. Politicians tend to announce the intent and leave everyone else to solve the engineering. Real progress happens when both sides stop posturing and do the hard work together.
What to Do Right Now
Nothing to download yet. iOS 27 arrives this autumn. What you can do today is check that Screen Time and Family Sharing are enabled for your kids’ devices, and make sure you are running at least iOS 18.4, which already includes a streamlined Child Account setup and some useful default protections. Get the foundations in place now so you are ready to layer on the new tools when they arrive.
If you want straightforward tech advice for families without the corporate spin, come and join the Tech Dads Life newsletter. No fluff, no filler, just the stuff that actually matters. Sign up at techdadslife.beehiiv.com .
