Product1 publisher3 min readPublished
UK prepares to legislate nudity blocking into the camera and every third-party app
Talks with Apple and Google since June produced progress the government calls insufficient, so ministers will write device-level blocks into law. There is no bill text yet, and that is the part product teams have to plan around.
The Product Desk · Product desk
What happened
- The UK government says it will prepare legislation forcing technology companies to make it impossible for anyone under 18 to take, view or send nude images.
- Negotiations with Apple and Google, running since 8 June, produced progress that the government says does not meet the scale of its ambition.
- Under the stated principles, nude images must be blocked across all device features, including the camera and third-party apps.
- The only permitted route to taking, viewing or sending nude images would be for an adult to clear a robust age-assurance process.
- Separately, the government says it is exploring legislation that would require apps children use to stop them accessing or sharing nudity.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- constraint Teams that never wrote a detection path would inherit one from the device: they cannot toggle it, cannot A/B test it, and cannot see it in their own logs when a user complains.
- exposure Adults become the group with something to prove, and any adult who declines verification sits in the same blocked state as a child.
- decision Whether this becomes a legal obligation at all now turns on what Apple and Google ship voluntarily, because the government says it will reassess the need for legislation if companies implement solutions themselves.
- cost With no introduction date and an explicit commitment to take time over the drafting, the near-term spend for product teams is scenario work that ships nothing.
For a product team, the first version of this arrives as a support ticket. A user says the camera closed on them, or a picture would not attach to a message, and nothing the team shipped explains the behaviour.
The published principles put nudity detection filters on by default and say parents and carers should not have to take active steps to switch them on [5]. Andy Burnham, quoted in the release as Prime Minister, described the intended design: protection built into the device and switched on by default, with the companies proving a user is an adult rather than a child having to keep themselves out of harm's way, which he said no country has required before [10]. Detection on by default at the device layer is an engineering statement about where the code runs, and it puts an operating-system behaviour in the middle of a product decision an app team made months ago.
The release names no detection technology and no accuracy standard [16]. That gap is where the rollout pain sits, because any filter that inspects every image before it is saved has a false-positive rate, and the first person to hear about a wrongly blocked photo is a support agent at a camera app, not a minister. Lisa Nandy told Parliament that planning must now become implementation and that progress must translate into protections [11]. On the government's side, the plan is currently three principles and an undertaking to draft.
The pressure behind the drafting is documented. The Internet Watch Foundation reported last month that more child sexual extortion-related reports had been recorded in six months than in the whole of 2025 [12], and its Report Remove service took 19 sextortion reports in 2022 [13]. Hold that six-month pace for a full year and the annual total lands at more than double the 2025 figure [14].
Two questions sort how much of this is yours before any law exists. Does your feature touch the device camera or the system image pipeline, and can you read a platform signal telling you a user is a verified adult?
Touching the camera with no adult signal available is the worst quadrant: you will be explaining a block you did not write, and your deliverable is triage and support copy rather than code. Touching the camera with a signal available makes this integration work, plus a designed state for the user who declines verification and still wants their phone to take pictures. If your images only come from your own servers and never near the camera, the job is mapping which of your UK surfaces would be in scope, which is an afternoon with a feature list rather than a sprint. If neither applies, keep a watching brief and set the trigger to revisit at the moment a draft is published.
The honest read on timing is that nobody can build to this yet. The useful work now is knowing which of your surfaces would be affected, so that when a spec exists you are costing it rather than discovering it.
What to watch
- A published draft that says who actually verifies age: the platform, the app, or a third-party provider.
- Any Apple or Google announcement of on-by-default nudity blocking for UK devices ahead of the bill.
- Whether age assurance is demanded of existing adult accounts or only at new device setup.