Apple's New Parental Controls Are the Best Yet. Here Is What They Still Do Not Cover

On 14 September 2026, Apple shipped the most substantial rework of its parental controls in the history of the iPhone. iOS 27, iPadOS 27 and macOS 27 introduced Ask to Browse, extended Communication Safety to violent imagery, replaced a single blanket screen-time limit with age-tailored Time Allowances, added approval for new contacts, and rebuilt the Screen Time interface around what a parent actually needs to see.

These are genuine improvements, and some of them close loopholes that parents have been complaining about for the better part of a decade. It is worth saying that plainly before saying anything critical, because the criticism that follows is not that Apple did too little. It is that a set of controls this good invites a dangerous assumption: that the problem is now handled.

It is not handled. Four significant gaps remain, and every one of them is the kind a determined eleven-year-old finds in an afternoon.

What Apple Genuinely Fixed

Ask to Browse is the headline, and it deserves to be. Until now, a child blocked from the TikTok app could simply open Safari and use the website instead, with no friction at all. App-level blocking had a web-shaped hole in it. Ask to Browse closes that hole: when a child tries to visit a site they have not been to before, the request goes to a parent, who sees what was asked for and approves or declines it in Messages. It works the way Ask to Buy already works for purchases, which means most families already understand the pattern.

Communication Safety now detects gore and graphic violence, not only nudity, and it applies to shared images and video including live FaceTime calls. The detection runs on the device. This matters because violent content has long been the category that parents worried about and no automated tool addressed.

Time Allowances replace one daily number with per-category guidance that varies by the child’s age — social media, entertainment and games treated as different things, because they are different things. Apple says the suggested values draw on expert research.

And the setup experience has been rebuilt, which sounds like a minor detail and is not. Parental controls that are tedious to configure are parental controls that never get configured. A guided flow at device setup, with a recommended set of apps for a new child account, will do more good in aggregate than any individual feature on this list.

Gap One: The Browser Is Only One Browser

Ask to Browse is confirmed for Safari. Apple’s own description names Safari specifically, and coverage of the release notes it extends to other WebKit-based browsers once Screen Time is updated.

What that leaves out is harder to pin down than it first looks. Outside the European Union, Chrome and Firefox on iOS are WebKit builds, so they should be covered — though Apple has not confirmed it app by app. Inside the EU, where Apple now permits alternative browser engines, a child can install a browser the feature does not watch at all. For a European family the hole is therefore real rather than hypothetical. The blunt fix is the old one: block the alternative browser entirely at the app level through Screen Time.

The subtler version of the same problem is the in-app browser. When a link is tapped inside Snapchat, Instagram or TikTok, the page usually opens in a web view embedded in that app rather than in Safari. These embedded views are fully capable browsers. Apple has not publicly stated whether Ask to Browse reaches them, and until parents can test it on their own devices, the honest answer is that nobody outside Apple knows. Assume it does not, and verify before relying on it.

This matters more than it first appears, because the apps most likely to surface content a parent would want to intercept are precisely the apps that open links internally.

Gap Two: A Deleted App Can Come Back

Ask to Buy requires a child to request permission before acquiring a new app. It has always had a documented exception, and iOS 27 does not appear to have closed it: an app that was previously acquired on the account can be reinstalled from purchase history without triggering a fresh approval request, because the system treats a reinstall as a redownload rather than as a new acquisition.

The practical consequence is that a parent who discovers an app and deletes it has not necessarily removed it. It can return, quietly, and the parent gets no notification that it did.

This also undercuts the fix in the first gap. Blocking an alternative browser at the app level is the recommended workaround wherever Ask to Browse does not reach — but that workaround only holds if removing an app actually keeps it removed. Blocking is more reliable here than deleting.

Gap Three: Guidance Is Not Enforcement

Apple’s own language around Time Allowances is careful. The company describes them as expert-informed guidance and as a helpful starting point. That is an accurate description of what they are, and parents should read it as precisely as Apple wrote it.

Screen Time’s weak point has never really been the quality of its suggestions. It has been reliability. The feature has a long and well-documented history of limits that silently fail to apply, settings that do not persist, and bypass routes through Siri, through widgets, and through simply changing the device’s date and time. Apple has fixed a number of these over successive releases, but reports of limits failing to apply have continued through 2026. But the standing verdict in the technology press — unchanged by this release, even where individual controls genuinely improved — is that Screen Time is not something to rely on as a household’s only line of defence.

The reasonable posture is to treat Time Allowances as what they are: a structured conversation starter about how a child spends their day, backed by a mechanism that usually works. A child who understands and accepts the limit is the thing that makes it hold. The software is the reminder, not the wall.

Gap Four: It Is One Vendor, on One Device

Every control described in this article runs on an iPhone, an iPad or a Mac signed into a child Apple Account. That is the boundary, and it is a hard one.

The average household with children does not contain only Apple hardware. There is the Android tablet the grandparents bought. The games console in the living room, with a browser in it. The smart TV, which also has a browser in it. The school-issued Chromebook, which the school manages and the parents do not. The friend’s phone, at the friend’s house, on the friend’s network.

None of these are touched by anything Apple shipped in September, and no amount of refinement to Screen Time will ever touch them, because a device maker can only govern its own devices. This is not a criticism of Apple so much as a structural fact about device-level controls: they stop at the edge of the device.

Protection that follows the household rather than the handset has to live somewhere else — on the network, where every device that connects is subject to the same policy regardless of who made it or who manages it. That is a different layer of the problem, and it is the layer Apple’s announcement does not address at all. The trade-off is that network-level filtering applies where the network reaches, which typically means the home. Neither layer is sufficient by itself, which is rather the point.

What Parents Can Do Right Now

The new controls are worth turning on. They are also worth turning on with clear eyes about where they stop.

1. Update, then run the setup flow deliberately. The rebuilt configuration experience is the single highest-value change in this release. Go through it properly once rather than accepting defaults and intending to return later.

2. Block alternative browsers rather than deleting them. Because Ask to Browse is Safari-scoped and because deleted apps can return from purchase history, blocking Chrome and Firefox at the app level is more durable than removing them. Check Screen Time → Content & Privacy Restrictions → Allowed Apps.

3. Test the in-app browsers yourself. Open a link inside whichever social app the child actually uses and see whether the approval prompt appears. Five minutes of testing beats an assumption that may not hold.

4. Set a Screen Time passcode that is not the device passcode. Use a distinct alphanumeric code. A shared or guessable code defeats every control above in one step, and it remains the most common way these settings get undone.

5. Cover the devices Apple cannot reach. Take an inventory of everything in the house that connects to the internet and ask which layer protects each one. For the non-Apple devices, that answer has to be network-level filtering or nothing.

6. Keep the conversation going. Every technical measure in this article is defeatable by a motivated child with time and an internet search. Controls buy time and reduce accidental exposure. Understanding is what does the durable work.

The Road Ahead

The most significant thing about this release is not any individual feature. It is that child safety has become a headline item in a platform vendor’s marketing — the German version of Apple’s own release page gives child safety its own headline section, Features für die Kindersicherheit, alongside Apple Intelligence and the new design. Regulatory pressure, including sustained demands in the United Kingdom for device-wide child protections, is part of why these controls shipped when they did.

That direction of travel is good news, and it will continue. Apple has a strong commercial reason to keep improving here, and competitors have a strong reason to follow. Expect the gaps described above to narrow over the next few releases, starting most likely with clarity about which apps Ask to Browse and contact approval actually cover.

What will not change is the structural limit. A device maker protects its own devices. A household contains more than one maker’s devices, and children move between networks and between houses. That gap is not a bug in Apple’s implementation, and it will not be fixed by a future version of Screen Time.

Last updated: September 16, 2026. We update this article as Apple clarifies the scope of these features and as parents report real-world behaviour.