At London Tech Week on June 8, 2026, Prime Minister Keir Starmer gave Apple and Google three months to introduce device-level controls that prevent children from taking, sending, receiving, or viewing nude images, or face legislation.
The government's argument sounds simple: the technology already exists on phones and tablets, so companies should switch it on more broadly. That is partly true, but it needs precision.
Apple's UK support documentation says its Communication Safety feature can detect nude photos and videos in Messages, AirDrop, Contact Posters, FaceTime calls and video messages, shared photo albums, and some third-party app sharing flows. Apple says the analysis happens on the device, not in the cloud.
That is not the same as a full device-wide blocking system. Apple's current tools are built around warnings, blurring, and safety prompts in supported contexts. The UK government is pushing for something stricter: default controls that stop children from taking, viewing, sending, receiving, or saving nude images across smartphones and tablets unless the user is verified as an adult.
The issue is being framed around self-generated child sexual abuse material. 2024 data from the Internet Watch Foundation found that 91% of the criminal child sexual abuse reports it assessed contained self-generated imagery. Separately, Children's Commissioner research found that the average age of first exposure to online pornography remained 13.
What the UK wants Apple to change
The UK proposal is aimed at smartphones and tablets, not just social media apps. That distinction matters because the government is pushing responsibility down to the device and operating-system level, where Apple and Google have more control than individual apps do.
Starmer's demand covers three broad actions: taking nude images, sharing them, and viewing them. Apple's Communication Safety already addresses parts of that problem in several Apple-controlled or system-level sharing contexts. But Apple has not publicly described a system that blocks camera capture, saving, search, third-party messaging, or every app-level image-sharing route across the device.
That is the central gap. Apple has relevant on-device nudity detection. The UK wants broader prevention.
The functional difference comes down to warning versus blocking. Apple's documented system can blur sensitive photos or videos and present safety prompts in supported contexts, but it still lets older children choose to proceed in some situations. The UK proposal is aiming for a stricter default: blocking children from taking, viewing, sending, receiving, or saving nude images unless the user is verified as an adult.
The privacy design is also important. The government has described the proposal as one that would not involve routine reporting, monitoring, data collection, or images leaving the device. That broadly matches Apple's on-device approach. However, Apple's current feature also includes optional child-initiated reporting in some iMessage and FaceTime situations, which can send reported content to Apple for review.
Where Apple's current tool falls short
Apple has confirmed several important limits and requirements. Communication Safety requires a child Apple Account, Family Sharing, and supported software, and Apple says it is on by default for children under 18 on iPhone, iPad, Mac, and Apple Watch with the latest software.
The open question is not whether Apple has a child-safety feature. It is whether that feature, as currently deployed, satisfies the UK's proposed whole-device blocking standard.
That standard appears to go beyond Apple's current blur-and-warn model. A system that warns a child before opening or sending a sensitive image is different from one that prevents the image from being taken, saved, shared, searched for, or viewed across the device.
The Home Office also says the proposal would cover existing and newly sold UK phones and tablets, not only future devices. Adults would still be able to take, share, or view nude content after verifying their age, which makes age assurance one of the biggest unresolved practical questions for iPhone and Android users.
For families, that means the most important details may come down to account setup and device settings: whether a child is using a proper child account, whether Family Sharing or parental controls are configured, whether the device has current software, and how Apple or Google would handle users who have not verified their age.
Why the deadline matters
This is not the UK's first recent clash with Apple over device and account security.
In February 2025, Apple removed Advanced Data Protection from the UK after the government sought access to encrypted iCloud data under the Investigatory Powers Act. That move meant UK users could no longer use Apple's strongest optional iCloud encryption, though iMessage and FaceTime remained end-to-end encrypted by default.
The nudity-detection proposal is different. A local tool that analyzes images on a device is not the same as giving the government access to encrypted cloud backups. Still, privacy groups have raised concerns that mandatory device-level scanning could expand beyond its stated child-safety purpose.
The iCloud episode matters because it shows Apple may remove or limit features in the UK rather than change its global privacy architecture. That makes the three-month deadline more than a routine policy request.
What UK families should watch next
If Apple moves toward compliance, families may see Communication Safety or a related setting expand beyond supported sharing and messaging contexts into camera capture, saving, search, third-party messaging, and broader app flows. That would be a bigger change than Apple's current system.
Google will face similar pressure on Android. The proposal is not limited to Apple, but Apple is a key test case because it already has child nudity warnings, privacy-focused on-device processing, child account tools, and tight control over iOS and iPadOS.
Even then, "impossible" is a high bar. Nudity detection can produce false positives and false negatives, and the government has not yet defined how compliance would be measured. There are also unanswered questions about appeals, misclassified users, adults who do not want to verify their age, teenagers using adult accounts, and children using shared family devices.
The key question now is what the UK will count as compliance: stronger warnings, default blocking, camera-level prevention, or a whole-device system tied to age verification.
For Apple users, the takeaway is straightforward. Apple already has Communication Safety, and parents can check whether a child account, Family Sharing, and supported software are in place now. But the UK is asking for more than Apple's current warning system. It wants default device-level blocking for children, and the next three months will determine whether Apple and Google build that voluntarily or face a new legal requirement.
Comments
Be the first, drop a comment!