Privacy by Design Principles

Module 07 · Lesson 01

Privacy by design, not by afterthought

Seven foundational principles that transform privacy from a compliance checkbox into an architectural requirement. Embed privacy into every system from day one.

Principle 1-2

Proactive + Default

Principle 1

Proactive not reactive

Anticipate privacy risks before they materialize. Conduct assessments during design, not after launch. Prevention beats remediation.

Principle 2

Privacy as the default

Most privacy-protective settings out of the box. Users opt in to data collection, not opt out. No dark patterns.

GDPR Article 25: data protection by design and by default is a legal requirement, not a best practice.

Principle 3-4

Embedded + Positive-sum

Principle 3

Embedded into design

Privacy is a core architectural component, not an add-on. Data minimization is a design constraint from the start.

Principle 4

Full functionality

Privacy doesn't sacrifice features. Design for both privacy AND business goals. Positive-sum, not zero-sum.

If your privacy implementation breaks user experience, you designed it wrong.

Principle 5-7

Security + Transparency + Respect

Principle 5

End-to-end security

Protect data across its entire lifecycle — collection through deletion.

Principle 6

Visibility

Operations transparent to users and regulators. Audit trails, clear notices.

Principle 7

User respect

Individual at the center. Strong defaults, user-friendly controls.

PbD vs Bolt-on

The cost of doing it backwards

Aspect	Privacy by Design	Bolt-on Privacy
When	Before first line of code	After launch
Data collected	Only what's needed	Everything, then restrict
Cost	Built into budget	Expensive retrofit
User experience	Clean, intentional	Consent banners everywhere
Compliance risk	Low — designed compliant	High — gaps inevitable

Real-World Example

Apple Find My

Apple's Find My network uses end-to-end encryption and rotating Bluetooth identifiers. Apple physically cannot see where your devices are.

This isn't a privacy policy promise — it's an engineering decision. The privacy protection is embedded in the cryptographic design.

Compare: a competitor storing plaintext GPS coordinates server-side and promising "we won't look at them." That's bolt-on trust. Apple's approach is privacy by design — technically impossible to violate.

Key Takeaway

Design for privacy first

Remember this

Ask "what data do we actually need?" before writing code — not after.

Every field you don't collect is a field that can't be breached, misused, or create compliance obligations.

GDPR Article 25 makes PbD a legal requirement. The fine for non-compliance is separate from any actual breach.

The best privacy architecture makes violations technically impossible, not just policy-prohibited.

1 / 7