/ THE SHORT ANSWER
The UK government plans legislation intended to prevent users under 18 from taking, viewing, or sharing nude images through devices and platforms. The exact legal text, implementation standard, privacy safeguards, enforcement model, and treatment of edge cases are not yet available.
- 01The government has announced planned legislation, not a final enacted technical standard.
- 02The intended scope includes taking, viewing, and sending nude images by under-18s.
- 03Apple and Google have made progress, but the government says current action is insufficient.
- 04Teams should begin scenario analysis while avoiding assumptions about the final implementation.
/ dotSuper point of view
Device-level safety requirements can reshape operating systems, apps, age assurance, privacy architecture, and developer responsibilities at the same time.
What the UK government announced
The UK government says it will prepare legislation requiring technology companies to implement stronger safeguards intended to prevent children from taking, sharing, or viewing nude images.
The announcement follows a three-month period of work with Apple and Google. The government says progress has been made but does not meet its stated ambition, so legislation will be brought forward.
- Proposed coverage for users under 18
- Device-level and platform responsibilities
- Potential relevance to cameras, messaging, media viewing, and third-party apps
- Final legislative text and technical standards still pending
Why implementation will be complex
A control that affects image capture, viewing, and sharing crosses operating-system permissions, app behavior, content classification, age assurance, accessibility, and privacy. False positives and false negatives can each create serious harm.
The system must also distinguish between prevention, warning, reporting, and enforcement. Apple’s existing Communication Safety feature warns children when nudity is detected in supported communication contexts, but proposed legislation may set a broader outcome.
- Define age and account assurance
- Determine where classification runs
- Protect sensitive image data and model outputs
- Create safe handling for medical, educational, and reporting contexts
What product teams should prepare
Teams should map every feature that captures, uploads, generates, stores, or displays images for UK users. Identify which controls sit with the device, operating system, app, service, parent, or account owner.
Run privacy and child-rights assessments before selecting a technical design. A rushed implementation could introduce surveillance, exclusion, or safety risks while trying to reduce another harm.
- Inventory image pathways and third-party SDKs
- Document youth account and family-control behavior
- Test accessibility and legitimate-use edge cases
- Prepare transparent notices and appeal routes
What this page cannot conclude
- 01The government has announced legislation but has not published the final legal text cited here.
- 02Technical feasibility and privacy effects depend on the eventual standard.
- 03This article does not provide legal advice or evaluate every platform feature.
Sources
- 01UK prepares legislation on nude images and child safetyUK Government · accessed Sep 10, 2026
- 02New plans to stop children taking, sharing or viewing nude imagesUK Government · accessed Sep 10, 2026
- 03UK Online SafetyApple · accessed Sep 10, 2026
Our editorial standard · Found an error? Send a correction with its source.
/ CITE OR SHARE THIS GUIDE
Make the evidence easy to verify.
When you reference this guide, link to its canonical URL. That gives readers one stable place for the evidence, limitations and future updates.
dotSuper Research Desk. (September 10, 2026). UK Plans Device-Level Nude Image Blocking for Under-18s: What Platforms Must Prepare. dotSuper. https://dotsuper.net/feeds/daily-briefing/2026-09-10-uk-device-level-child-safety-law