About this module
Privacy by Design means privacy is part of the build, not something added after launch. This lesson explains GDPR Article 25, Privacy by Default, and the practical checks product, engineering, and operations teams need before development starts. Learners cover data flow mapping, DPIA triggers, minimization, retention schedules, privacy-protective defaults, encryption, pseudonymization, access controls, audit logs, deletion mechanisms, and third-party processor records. The lesson is direct about launch discipline too: if a project needs a DPIA and it has not been completed, the launch should wait.
Key takeaways
Welcome to CS04-09. In this module we explore Privacy by Design — the discipline of embedding privacy into products, processes, and systems from day one, not as an afterthought.
Most organizations think about privacy after a product ships — when regulators come knocking or a breach makes headlines. Privacy by Design flips that approach.
It treats privacy as a core engineering requirement, embedded at the architecture stage, before a single line of code is written. Privacy by Design means building privacy controls into your architecture from the start.
It's proactive: you anticipate risks before data is ever collected, rather than patching gaps after problems emerge. Privacy by Default is the companion principle.
When your system launches, it should automatically provide the highest privacy settings. Users receive maximum protection without having to do anything — privacy is the default, not an option.
Privacy by Design isn't just best practice — it's law. Article 25 of the GDPR requires that data protection be integrated into processing systems by design and by default.
Organizations that skip this step face fines of up to four percent of global annual revenue. The practical roadmap for Privacy by Design comes from seven foundational principles developed by Dr.
Ann Cavoukian. Adopted by privacy regulators worldwide, these principles define what it means to build privacy into every facet of an organization — not just its technology.
Principle one: be proactive, not reactive. Privacy risks should be anticipated and prevented before they materialize.
Waiting for a breach or complaint and then fixing it is not Privacy by Design — it's damage control. Principle two: the strongest settings apply automatically.
If a user does nothing, their data should still be protected. Maximum privacy should be the starting point for every system — not something users must actively opt into.
Principle three: full functionality. Privacy by Design rejects the false choice between privacy and utility.
A well-architected system doesn't sacrifice features to add privacy controls — it achieves both at the same time, a positive-sum outcome. Article 35 of the GDPR mandates a formal impact assessment before launching high-risk processing.
Triggers include large-scale processing of sensitive categories, systematic monitoring of individuals, and automated decisions with significant legal effects. Schedule this assessment at architecture stage — before build, not before launch.
Here is a critical warning. Launching a product or feature that triggers Article 35 without a completed DPIA is a regulatory violation — full stop.
Authorities don't need to wait for a data breach to act. They can order processing to stop and issue fines the moment the gap is discovered.
No DPIA means no launch. When starting any new system or project, run through this checklist before development begins.
Map every personal data flow. Determine whether a DPIA is required.
Minimize data collection to what is strictly necessary. Set retention schedules from day one.
And ensure privacy-protective defaults are locked in before the first release. Principle four is end-to-end security — privacy must be enforced through the entire data lifecycle, from the moment data is collected to the point it is securely deleted.
Encryption at rest and in transit, role-based access controls, and pseudonymization are not optional extras — they are the baseline for any Privacy by Design compliant system. Privacy by Design is also a sound financial decision.
According to IBM's Cost of a Data Breach Report, organizations that apply privacy by design principles save an average of one point three million dollars per breach compared to those that do not. Prevention is measurably cheaper than remediation.
For developers and product managers, here is your build-phase privacy checklist. Pseudonymize or anonymize wherever possible.
Apply least-privilege access controls. Encrypt data in transit and at rest.
Maintain an audit log of access to personal data. Build the deletion mechanism before you launch, not after.
And document every third-party processor handling personal data — because you are responsible for them too. The core message of this module: build privacy in — don't add it on.
Privacy by Design protects users, reduces breach costs, satisfies regulators, and creates more trustworthy products. Start with privacy.
Stay with privacy.
