We've covered PETs and TOMs as tools for protecting data. But what if privacy was baked into the entire system design from day one, rather than bolted on later?

Privacy by Design is a framework for embedding privacy into every stage of system development, while Privacy by Default ensures the most protective settings are active without any user intervention.

Privacy by Design means thinking about privacy proactively, from the very first architecture decisions. It's not a checklist you run at the end of development... it's a design philosophy that shapes every decision along the way. The concept was developed by Ann Cavoukian, former Information and Privacy Commissioner of Ontario, Canada.

Privacy by Default takes this one step further. The factory settings of any system should be the most privacy-friendly option available. Users who want less privacy can actively opt out, but the default always protects everyone. No one should have to dig through settings menus to secure their own data.

The distinction matters: Privacy by Design is about the development process. Privacy by Default is about the user experience. Together, they shift the burden from users who don't know what to configure to developers who should know better.