Privacy by Design (PbD) — Seven Foundational Principles
Privacy by Design (PbD) is a framework developed by Dr. Ann Cavoukian (former Ontario Information and Privacy Commissioner) establishing seven foundational principles for embedding privacy into the design of IT systems, business practices, and networked infrastructure. PbD is enshrined in GDPR Article 25 (Data Protection by Design and by Default), referenced in the California Privacy Rights Act, and adopted by data protection authorities worldwide. The seven principles guide organisations to proactively embed privacy throughout the entire data lifecycle rather than treating it as an afterthought. The International Assembly of Privacy Commissioners unanimously adopted PbD as an international standard in 2010.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (15)
Corporate Transactions
| Code | Title |
|---|---|
| PBD-15 | Privacy by Design in Mergers and Acquisitions |
Emerging Technology
| Code | Title |
|---|---|
| PBD-16 | Algorithmic and AI Privacy Engineering |
Foundational Principles
Seven PbD principles
| Code | Title |
|---|---|
| PBD-FP-01 | Proactive and Preventive |
| PBD-FP-02 | Embedded and Full Lifecycle |
| PBD-FP-03 | Transparency and User-Centric |
Governance
| Code | Title |
|---|---|
| PBD-14 | Privacy Metrics and Reporting |
Implementation
| Code | Title |
|---|---|
| Art. 12 | Record-Keeping |
| Art. 13 | Transparency and Provision of Information to Deployers |
| Art. 14 | Human Oversight |
| BS65000-IM-01 | Resilience Assessment |
| BS65000-IM-02 | Scenario Planning |
| BS65000-IM-03 | Continuous Improvement |
| FATF-TR-IMP-01 | Technical Solutions |
| FATF-TR-IMP-02 | Jurisdictional Adoption |
| FATF-TR-IMP-03 | VASP AML/CFT |
| ILO-C149-08 | Article 8 — Implementation through national laws, collective agreements, or other means |
| ISO-8000-IMP-01 | Quality Measurement |
| ISO-8000-IMP-02 | Quality Improvement |
| ISO-8000-IMP-03 | Sector Applications |
| PBD-10 | Data Minimisation Operationalised |
| PBD-11 | Consent Management Platform |
| PBD-12 | Privacy Architecture Patterns Library |
| PBD-8 | Privacy Impact Assessment Methodology |
| PBD-9 | Privacy Enhancing Technology Adoption |
| PBD-IMP-01 | GDPR Article 25 |
| PBD-IMP-02 | Design Methodology |
| PBD-IMP-03 | Organisational Integration |
Implementation
Giving effect to provisions through national laws, collective agreements, or other appropriate means.
| Code | Title |
|---|---|
| Art. 12 | Record-Keeping |
| Art. 13 | Transparency and Provision of Information to Deployers |
| Art. 14 | Human Oversight |
| BS65000-IM-01 | Resilience Assessment |
| BS65000-IM-02 | Scenario Planning |
| BS65000-IM-03 | Continuous Improvement |
| FATF-TR-IMP-01 | Technical Solutions |
| FATF-TR-IMP-02 | Jurisdictional Adoption |
| FATF-TR-IMP-03 | VASP AML/CFT |
| ILO-C149-08 | Article 8 — Implementation through national laws, collective agreements, or other means |
| ISO-8000-IMP-01 | Quality Measurement |
| ISO-8000-IMP-02 | Quality Improvement |
| ISO-8000-IMP-03 | Sector Applications |
| PBD-10 | Data Minimisation Operationalised |
| PBD-11 | Consent Management Platform |
| PBD-12 | Privacy Architecture Patterns Library |
| PBD-8 | Privacy Impact Assessment Methodology |
| PBD-9 | Privacy Enhancing Technology Adoption |
| PBD-IMP-01 | GDPR Article 25 |
| PBD-IMP-02 | Design Methodology |
| PBD-IMP-03 | Organisational Integration |
People
| Code | Title |
|---|---|
| PBD-13 | Privacy Champions Network |
Principle 1 Proactive
| Code | Title |
|---|---|
| PBD-1 | Proactive Not Reactive Approach |
Principle 2 Default
| Code | Title |
|---|---|
| PBD-2 | Privacy as the Default Setting |
Principle 3 Embedded
| Code | Title |
|---|---|
| PBD-3 | Privacy Embedded into Design |
Principle 4 Full Functionality
| Code | Title |
|---|---|
| PBD-4 | Full Functionality Positive Sum |
Principle 5 End to End
| Code | Title |
|---|---|
| PBD-5 | End to End Security Lifecycle Protection |
Principle 6 Visibility
| Code | Title |
|---|---|
| PBD-6 | Visibility and Transparency |
Principle 7 User Centric
| Code | Title |
|---|---|
| PBD-7 | Respect for User Privacy User Centric |
Standards
| Code | Title |
|---|---|
| PBD-17 | ISO 31700 Conformance Assessment |
Your Compliance Coverage
If you comply with Privacy by Design (PbD) — Seven Foundational Principles, you already cover:
ILO Nursing Personnel Convention C149 (1977)
31%
11 controls mapped
Compare →6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673)
31%
11 controls mapped
Compare →ISO 8000 — Data Quality
31%
11 controls mapped
Compare →+ 675 more: FATF Recommendation 16 — Virtual Asset Travel Rule (31%), EU AI Act (28%)
See all 678 mapped frameworks ↓Maps to 678 other frameworks
Frequently Asked Questions
What is Privacy by Design (PbD) — Seven Foundational Principles?
Privacy by Design (PbD) — Seven Foundational Principles is a compliance framework from International with 15 domains and 36 controls. Privacy by Design (PbD) is a framework developed by Dr. Ann Cavoukian (former Ontario Information and Privacy Commissioner) establishing seven foundational principles for embedding privacy into the design of IT systems, business practices, and networked infrastructure. PbD is enshrined in GDPR Article 25 (Data Protection by Design and by Default), referenced in the California Privacy Rights Act, and adopted by data protection authorities worldwide. The seven principles guide organisations to proactively embed privacy throughout the entire data lifecycle rather than treating it as an afterthought. The International Assembly of Privacy Commissioners unanimously adopted PbD as an international standard in 2010. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does Privacy by Design (PbD) — Seven Foundational Principles have?
Privacy by Design (PbD) — Seven Foundational Principles has 36 controls organised across 15 domains. The largest domains are Implementation (16 controls), Implementation (5 controls), Foundational Principles (3 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does Privacy by Design (PbD) — Seven Foundational Principles map to?
Privacy by Design (PbD) — Seven Foundational Principles maps to 678 other compliance frameworks. The top mapping partners are ILO Nursing Personnel Convention C149 (1977) (31% coverage), 6th Anti-Money Laundering Directive (AMLD6, Directive (EU) 2018/1673) (31% coverage), ISO 8000 — Data Quality (31% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with Privacy by Design (PbD) — Seven Foundational Principles compliance?
Start your Privacy by Design (PbD) — Seven Foundational Principles compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about Privacy by Design (PbD) — Seven Foundational Principles requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 36 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 700 frameworks.
Get Started Free →Free forever — no credit card required