Building a connected product and unsure how to ask for consent? Good iot privacy ux means a clear opt-in, plain-language explanations at the right moment, and withdrawal that is as easy as agreeing.
This guide is part of our wider coverage of iot user experience design.
| Item | Value |
|---|---|
| Finalised ICO consumer IoT guidance | Published 11 June 2026 |
| Consultation on the earlier draft | Ran until the end of Sunday 7 September 2025 |
| Consent standard | A clear, specific opt-in, not a pre-ticked box |
| Withdrawing consent | Just as straightforward as giving it |
| Data protection impact assessment (DPIA) | Most organisations will need one |
| Correction requests | Organisations expected to act within a month |
These figures come from Lewis Silkin’s summary of the finalised guidance and techUK’s summary of the earlier draft. They can change, so check the source before you rely on them.
What the ICO expects from connected products
The Information Commissioner’s Office (ICO) published finalised guidance on consumer Internet of Things products and services on 11 June 2026, as Lewis Silkin reports. It spans the full lifecycle of connected consumer products, from smart speakers to fitness trackers.
The core message is privacy by design: it should not be bolted on afterwards. Going by the same law firm’s summary, the guidance points to these expectations:
- Protective settings are the default, and collection stays within what the product strictly needs to work.
- Consent is an unticked, specific choice rather than a line buried in the terms.
- People can take consent back as easily as they gave it.
- Explanations use plain language and appear when they matter.
- Most organisations complete a DPIA before launch.
Scope matters too. The draft version, as techUK summarised it, left out connected and autonomous vehicles, smart meters, smart cities, and industrial and enterprise IoT applications.
DAC Beachcroft’s note on the draft adds that organisations should consider what personal data is collected at each stage or interaction in a product’s lifecycle. It also stresses considering data protection from an early design stage and documenting that this was done.
How should you ask for consent?
Consent has to mean something, according to Lewis Silkin’s reading of the guidance. In design terms that is a clear, specific opt-in, never a pre-ticked box.
techUK highlights that consent should be freely given and unambiguous. Its summary of the draft recommends avoiding unnecessarily disruptive prompts and steering clear of option labels that use emotionally charged language to invite guilt or other negative emotions. Prompt frequency and tone are explored further in our guide to iot notification design.
One idea cuts against usual product habits. Lewis Silkin notes that the ICO endorses positive friction, meaning deliberately slowing people down when they make consent choices so that they stop and think.
A consent flow built on those points could follow these steps:
- Present each choice as a separate, specific question with nothing pre-selected.
- Label the options neutrally, without guilt or pressure in the wording.
- Add a short, deliberate pause where a decision has real consequences for personal data.
- Give people a withdrawal route that takes no more effort than the opt-in did.
Transparency at the moments that matter
A long privacy notice does not count as openness by itself. Lewis Silkin quotes the ICO’s press release line that “genuine transparency is more than a privacy notice”.
The firm’s example is a smart thermostat whose owner agrees to a dense notice during setup. Consent was obtained, yet transparency came as an afterthought while the device built a portrait of the household’s routines.
The better pattern is timing. techUK’s summary says the guidance invites organisations to identify the appropriate point in a user journey at which to surface information.

For a device, that could mean a short explanation when a microphone, camera or location feature is first switched on, rather than only at account creation. Each explanation should say in plain language what the data is used for.
Shared homes, children and inferred data
Connected products rarely serve one person. The ICO admits that gathering consent from multiple users where not everyone has an account “may be difficult”, so a smart speaker in a flat share captures voices of people with no real controls.
That tension is a design problem as much as a legal one, and our piece on multi-device ux design looks at how several people and devices share one setup.
Children raise the bar further. Lewis Silkin summarises the expectations as:
- High privacy by default.
- Age-appropriate design.
- Child-friendly explanations.
- A DPIA that covers children’s rights and risks, not only those of adult account holders.
Inferences count as well. A step count on its own is “unlikely to be health data”, but used to generate a wellness score or fed to an insurer calculating premiums, it becomes special category health data.
The takeaway for designers is that the ICO cares about the conclusions you draw, not just what you collect. DAC Beachcroft gives a smart watch as an example of a device that can reveal information from which someone’s health can be inferred.
Rights, retention and a team checklist
Good iot privacy ux also covers what happens after setup. techUK’s summary of the draft sets out how people should be able to use their rights:
- Access: the request process should not be unnecessarily cumbersome.
- Rectification: organisations are expected to act within a month.
- Erasure: it should be made clear that simply deleting an app or account does not necessarily erase data.
- Portability: data should be provided in a usable format where technically feasible.
- Objection: this is an absolute right for direct marketing purposes.
On retention, the same source says the ICO recognises it cannot mandate specific time frames but strongly encourages regular reviews of retention periods. Security also continues after launch: Lewis Silkin lists regular updates, encryption and multifactor authentication, maintained throughout the product’s lifetime.
The stakes are practical. DAC Beachcroft points out that people can face fraud if a device is hacked, or burglary if a smart lock’s security is compromised.
A short checklist for your team, drawn from the sources above (educational design guidance, not legal advice):
- Bring legal, product, design, engineering and security together before the device ships, as Lewis Silkin advises.
- Run a DPIA and map data collected at each lifecycle stage.
- Test consent screens for pre-selection, pressure and effort to withdraw.
- Plan how guests, children and people without accounts are treated.
- Review retention periods and deletion behaviour on a schedule.
For teams selling in both the UK and the EU, the same firm suggests building a single EU and UK IoT compliance framework now, using the ICO guidance for design detail and EU materials for the wider overlays.
Frequently asked questions
Is a pre-ticked box ever fine for a smart device?
Show answer
Not under the ICO’s finalised guidance as Lewis Silkin describes it. The expectation is an active, specific opt-in, so any default selection works against it.
Does deleting the companion app remove my data?
Show answer
Not necessarily. The draft guidance, per techUK, wants companies to say plainly that removing an app or account may leave stored data in place.
Do the rules reach smart meters or connected cars?
Show answer
The draft, as summarised by techUK, excluded both, along with smart cities and industrial IoT. Check the ICO’s own text for the finalised scope before you assume anything.
How long may a product keep device data?
Show answer
There is no fixed period. According to techUK, the ICO says storage should last no longer than necessary and wants periods reviewed regularly.
Why would regulators want consent to feel slower?
Show answer
A quick tap can mean no real thought. The ICO’s idea of positive friction, noted by Lewis Silkin, is a brief pause so people understand what they are agreeing to.
