Data Minimisation & Privacy by Design ยท Lesson 4 of 4
Privacy by design and by default
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Build privacy in from the first design decision and keep it there for the system's whole life. Don't bolt it on before launch.
In your work
Planning a tenant portal for a housing association client, you sketch the data flows on day one: what's collected, who sees it, where it's stored and when it's deleted. Gaps get fixed while they're cheap.
What the UK rules say
- Article 25 of UK GDPR requires data protection by design and by default: privacy built into how systems work, with privacy-friendly settings as the default.
- A data protection impact assessment (DPIA) is required before processing that's likely to result in a high risk to people.
What to do
- Map the personal data flows for every new feature.
- Choose privacy-friendly defaults, such as private profiles and opt-in sharing.
- Ask whether a DPIA is needed before you build, not after.
- Revisit privacy whenever the feature changes.
Watch out for
- Leaving privacy to a pre-launch review, when changes are expensive.
- Defaults that share or keep more than people would expect.
In your organisation
When does your organisation require a DPIA, and how do you start one?
Your employer's own policies come first.
Sources
- ICO, Data protection by design and by default (opens in a new tab), checked 6 October 2026.
- ICO, Data protection impact assessments (DPIAs) (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
