Privacy by Design
An approach that embeds privacy protections into the design and architecture of systems, processes, and products from the outset rather than as an afterthought.
On this page
What is Privacy by Design?
Privacy by Design (PbD), developed by Ann Cavoukian, is based on seven foundational principles: proactive prevention, privacy as default, embedded into design, full functionality, end-to-end security, visibility/transparency, and user-centricity. GDPR Article 25 codifies this concept as "data protection by design and by default," requiring controllers to implement appropriate technical and organizational measures throughout the development lifecycle.
Application to Vendor Screening
Assess whether vendors implement privacy by design in their products. Look for data minimization (collecting only necessary data), privacy-preserving defaults (opt-in rather than opt-out), granular consent management, and privacy features embedded in the product architecture rather than bolted on.
Practical Examples
- Evaluating whether a vendor's product collects only necessary personal data
- Assessing a vendor's default privacy settings for new user accounts
- Reviewing a vendor's development lifecycle for privacy integration points
Frequently Asked Questions
Is Privacy by Design a legal requirement?
GDPR Article 25 requires data protection by design and by default, making it a legal obligation for controllers. While the original PbD framework is a set of principles, its core concepts are now legally enforceable in the EU.
How do you assess a vendor's Privacy by Design maturity?
Evaluate data minimization practices, default privacy settings, consent mechanisms, data retention policies, privacy in the development lifecycle, privacy impact assessments, and the role of privacy professionals in product decisions.