All research
Guide··Updated ·4 min read·GDPR·Privacy·UK Compliance

What Is Privacy-by-Design and Why It Matters for UK Businesses

Privacy by design is a legal duty under Article 25 of the UK GDPR. This guide sets out the seven original principles and how a UK business can apply them.

Last reviewed: 16 November 2026.

What privacy by design means

Privacy by design means building privacy into a system from the start: its architecture, its defaults and the processes around it.

The idea was set out by Dr Ann Cavoukian, then Information and Privacy Commissioner of Ontario, in seven foundational principles. Article 25 of the UK GDPR puts a version of it into law under the name “data protection by design and by default”.

Article 25 requires a controller to implement appropriate technical and organisational measures “both at the time of the determination of the means for processing and at the time of the processing itself”. In practice that means considering privacy:

  • Before you build a product or service
  • During development and testing
  • After launch, through monitoring

Article 25 makes this a legal duty, and the regulator’s guidance on data protection by design and by default sets out what it expects.

The seven foundational principles

1. Proactive not reactive; preventative not remedial

Anticipate privacy problems and prevent them. Do not wait for them to happen.

In practice: Check every new product, feature or processing activity for whether it needs a Data Protection Impact Assessment (DPIA), and carry one out where the processing is likely to be high risk.

2. Privacy as the default setting

Personal data should be protected without the individual having to do anything.

In practice: Ship with the most protective settings switched on. If you offer analytics, make it opt-in.

3. Privacy embedded into design

Privacy is part of the architecture, not an add-on.

In practice: Design data flows to collect as little personal data as possible. Pseudonymise and encrypt in the storage layer so every application inherits it.

4. Full functionality: positive-sum, not zero-sum

The framework rejects the idea that privacy must be traded against security or functionality.

In practice: Look for a design that meets the business objective and protects personal data, before accepting a trade-off.

5. End-to-end security: full lifecycle protection

Data is kept securely and then destroyed securely at the end of its life.

In practice: Set a retention period for every category of personal data. Automate deletion. Encrypt data at rest and in transit.

6. Visibility and transparency

Keep processes open to individuals and regulators.

In practice: Write privacy notices in plain English. Publish your list of sub-processors.

7. Respect for user privacy: keep it user-centric

Offer strong defaults, clear notice and options that are easy to use.

In practice: Make it easy for users to access, correct and delete their information.

Why do it

Beyond the legal duty:

  • Cost. A privacy problem found at design stage is cheaper to fix than one found after launch.
  • Breach risk. A system that holds less personal data exposes less when something goes wrong.
  • Enforcement. Article 83(2)(d) lists the measures a controller has taken under Article 25 among the factors in deciding a fine.

Getting started

  1. Map your data flows. Record what personal data you collect, why, where it goes and how long you keep it.
  2. Carry out DPIAs for processing likely to result in a high risk to individuals.
  3. Review your defaults. Check whether your products ship with the most protective settings.
  4. Train your team. Developers, product managers and designers all need to understand the principles.
  5. Get an outside review. Someone who did not design the system will see things the team does not.

We offer Privacy-by-Design Reviews for teams that want that outside review.

Sources

  1. UK GDPR, Article 25: data protection by design and by default.
  2. Information Commissioner’s Office, Data protection by design and by default.
  3. UK GDPR, Article 83: general conditions for imposing fines.
  4. Ann Cavoukian, Privacy by Design: The 7 Foundational Principles, Information and Privacy Commissioner of Ontario.

Interested in working with us?

Get in touch to discuss our products, partnerships, or research collaborations.