Turn privacy policy into system behavior
Learn how Privacy by Design becomes requirements, controls, tests, and evidence across a system's lifecycle. Select each section to explore GDPR Article 25, the seven PbD principles, engineering patterns, and real architecture challenges.
GDPR Article 25: Data Protection by Design and by Default
Article 25 calls for appropriate technical and organizational measures to implement data-protection principles. This section connects legal language to engineering choices.
What Article 25 requires:
Privacy is an engineering requirement, not an afterthought. It shapes the system from conception.
Out-of-the-box settings must reflect the most privacy-protective option. Users should not have to opt in to privacy.
Record what you did, why you did it, and how you tested it. Evidence matters when regulators review your decisions.
The Seven Privacy by Design Principles
Select a principle to see what it means in a system and what evidence would make it concrete.
Privacy Engineering Across the Life Cycle
Privacy engineering runs with the system lifecycle. Each phase has distinct privacy responsibilities.
Threat model. Define data flows, actors, and what privacy means for this system.
Write privacy requirements. Name what behavior you expect and how to verify it.
Choose techniques. Encryption, access control, data minimization, retention policies.
Code. Translate requirements into architecture, APIs, and configurations.
Verify compliance. Privacy unit tests, integration tests, and manual security review.
Default settings. Make privacy the out-of-box state. Train operators.
Monitor. Log access, detect anomalies, respond to requests, audit controls.
Privacy-Enhancing Technology (PET) Selector
Choose the strongest factor for this case. Good selection connects a technique to a purpose and an asset.
Scenario: A healthcare provider wants to let researchers analyze patterns in patient records without exposing identities.
Which technique best protects privacy here?
The Billing-System Review
Architecture changes where personal data flows, which teams control it, and how you test privacy. Identify the choice that best reduces privacy risk in this scenario.
Situation: Your payment processor currently receives full customer records (name, email, phone, address, purchase history) for every transaction. This is a privacy risk: more data in the pipeline means more exposure if systems are breached or misused.
What's the best privacy fix?
Mastery Check
Answer from memory. Feedback explains the distinction the question tests.
Teaching aid, not legal advice. Legal content was last reviewed in August 2026. Adequacy decisions and implementing regulations change; verify sources before reusing this material in a later term.