How the concept is used

In an identity journey, this can involve selecting necessary attributes, separating responsibilities, protecting access and planning deletion. Default settings matter too: a way to restrict sharing is less useful if the system starts by sharing everything. Operational procedures also matter, so employees understand how to handle information during support, errors and changes to a supplier’s service.

A practical example

For example, an online shop selecting age verification decides that staff need to see whether a check completed, without exposing complete identity documents in the support screen. It also examines whether technical error logs might retain responses that are not needed. Those decisions should shape the data model, access rights and support process while the integration is being built.

Important distinctions

Data protection by design does not mean a particular technology automatically satisfies every legal requirement. A well-protected login method can still be embedded in an unnecessarily intrusive data journey. Encryption, minimisation and understandable procedures address different parts of the problem. The business should document its choices and test their behaviour during ordinary use and exceptions. If the purpose or integration changes, protections need reassessment; they are not a property checked only on launch day.

Sources

  1. EUR-Lex: Regulation (EU) 2016/679, Articles 5 and 25 Checked
  2. Datatilsynet: Databeskyttelse gennem design og standardindstillinger Checked

These explanations were prepared with AI assistance and draw on the sources listed.