Glossary · Privacy & regulation
Privacy by design
Privacy by design is the principle — codified as a legal obligation in GDPR Article 25 — that data protection must be built into a system’s architecture from the outset, not added afterward as a policy or a configuration toggle.
The term predates GDPR, originating with Ontario privacy commissioner Ann Cavoukian in the 1990s as a set of design principles: proactive rather than reactive, privacy as the default setting, embedded into design, full functionality without unnecessary trade-offs, end-to-end security, visibility and transparency, and respect for user privacy. GDPR Article 25 turned the core of this into a legal requirement — "data protection by design and by default" — obliging controllers to implement appropriate technical and organizational measures, such as pseudonymization and data minimization, at the time of determining the means of processing, not after launch.
In practice, privacy by design shows up as architectural decisions rather than policy statements: collecting only the fields a feature actually needs, defaulting new accounts to the most private setting rather than requiring opt-out, choosing authentication protocols that never transmit a password rather than merely promising not to log it, and encrypting data such that even the operator cannot read it where the product doesn’t require them to. It’s the difference between a company saying it protects data and a company built so that mishandling it is architecturally difficult.
Ciphera treats this as a build-time constraint: Ciphera ID uses OPAQUE so passwords never reach the server in any form, and Pulse is architected to run without cookies or persistent identifiers rather than collecting them and promising restraint.