The UK Government has committed to introducing legislation requiring stronger device-level protections for children after deciding that measures proposed by Apple and Google do not yet go far enough.
The move follows a three-month period in which Apple and Google were asked to develop voluntary technical solutions designed to prevent children from taking, sharing or viewing nude imagery on their devices.
Both companies have made changes and given the Government further commitments, but ministers now say those measures do not provide the comprehensive protection they want across the wider device and app ecosystem.
Speaking to Parliament on 8 September, Digital Secretary Lisa Nandy confirmed that the Government intends to legislate to ensure stronger protections are implemented across the technology ecosystem. The Government’s parliamentary statement makes clear that ministers now want planning to turn into implementation.
Importantly, no new law has taken effect yet. The legislation still needs to be developed and passed through Parliament, and the Government has said it will continue assessing what measures are required as technology companies implement their commitments.
What could change on children’s smartphones?
The Government’s ambition goes considerably further than conventional parental controls.
When the policy was first announced in June, Apple, Google and other companies were given three months to develop systems that could prevent under-18s from taking, receiving, sharing or viewing nude imagery on smartphones and tablets.
The original June Government announcement said built-in features or other technical solutions should detect and block nude images for children, while adults would still be able to access such content through an age-verification process.
That potentially means protections operating across the device rather than only inside individual services.
The September announcement broadens the focus further. The Government has said apps used by children will also need to play a role in preventing access to or sharing of nude imagery, with ministers exploring what additional legislation may be needed to cover the wider ecosystem.
That distinction matters. Even strong protections built into iOS or Android may not be enough if a child can simply move to a third-party app where the same safeguards do not apply.
Apple already has Communication Safety
Apple already provides substantial protections through its Communication Safety system, part of the wider safeguards available across the Apple ecosystem.
On supported child accounts, Communication Safety can detect potentially nude photos or videos using on-device machine learning. The content can be blurred and warnings displayed before it is viewed or shared.
Apple says the analysis happens locally on the device, meaning Apple does not receive the image or an indication that nudity was detected.
The feature works across areas including Messages, AirDrop, FaceTime, shared photo albums and the system photo picker used by some third-party applications. Apple also says children under 13 can require approval through the Screen Time passcode before viewing detected sensitive content. Full details are available in Apple’s Communication Safety guidance.
Those are meaningful protections, but the Government’s concern is that current safeguards do not yet cover every way in which explicit imagery could be created, stored, searched for or transferred.
Google has protections too — but they are not device-wide
Google takes a similar approach in parts of Android.
Sensitive Content Warnings in Google Messages can detect and blur images that may contain nudity, while displaying warnings when a user attempts to receive, send or forward such an image.
Google says that detection happens on the device and that the feature does not send detected nude images to Google. It is enabled by default for supervised users and signed-in unsupervised teenagers, although the exact controls vary by account type.
However, Google’s own documentation confirms that the feature currently applies to Google Messages rather than everything taking place across an Android phone. The company explains the feature in its Sensitive Content Warnings guidance.
Again, that is a useful safeguard, but it is different from the wider system-level protection the Government wants.
Age assurance will become an important part of the system
One of the biggest unresolved questions is how a device reliably distinguishes between a child and an adult.
The Government’s June proposal envisaged protections being enabled for children while adults would be able to deactivate them after demonstrating that they are over 18 through an age-assurance process.
That creates an important technical and privacy challenge.
A system needs enough confidence about the user’s age to apply the correct restrictions without unnecessarily exposing personal information or forcing intrusive identity checks.
Apple and Google’s existing systems already show that image analysis can take place locally on a device rather than uploading private photographs for examination. Extending protections across cameras, storage, third-party apps and other system functions would still require much broader technical decisions.
The Government has not yet published the detailed technical standards, accuracy requirements or enforcement structure for the proposed law.
The legislation has been committed to — but it is not law yet
That distinction is particularly important for parents.
Nothing changed overnight on an iPhone, Pixel, Galaxy phone or other Android device as a direct consequence of Tuesday’s announcement.
The Government has committed to introducing primary legislation, but there is currently no confirmed implementation date.
There is also still room for Apple, Google and other affected companies to implement stronger measures while legislation is being prepared.
So this is a significant escalation in UK technology policy, but not yet a finished regulatory framework.
Tech Torque Verdict
The biggest change here is not another parental-control feature. It is the Government’s decision that protecting children from explicit imagery should potentially become a core responsibility of the smartphone operating system itself.
Apple and Google already have useful technology capable of detecting sensitive imagery locally, and both provide child-safety controls. The gap is coverage: neither currently provides the comprehensive device-wide blocking system the Government wants.
There are clear child-safety arguments for making protection harder to bypass, particularly when grooming or coercion can move between different apps and services.
But implementation matters just as much. Age assurance, false detections, privacy and the boundaries of device-level content analysis all need clear answers before legislation becomes operational.
For now, parents do not need to change anything because of this announcement. What has changed is the direction of travel: voluntary measures have not satisfied ministers, and legislation is now being prepared.
