Privacy by design
Privacy by design is an approach to systems engineering and organisational design, developed by Ann Cavoukian in the 1990s and endorsed by the International Conference of Data Protection Commissioners in 2010, which holds that privacy must be built into technologies, business practices and infrastructures from the outset rather than added afterwards. Its seven foundational principles are: proactive not reactive; privacy as the default setting; privacy embedded into design; full functionality (positive-sum, not zero-sum); end-to-end security; visibility and transparency; and respect for user privacy.
The GDPR turned the concept into a binding obligation in Art. 25, split into data protection by design and data protection by default. ISO 31700 (2023) provides a standard for privacy by design in consumer goods and services, and the framework informs the EDPB Guidelines 4/2019. The EU AI Act applies the same lifecycle logic to high-risk AI systems through risk management and data governance requirements.
In life sciences, privacy by design means involving the DPO when the protocol and case report form are drafted, choosing pseudonymisation architectures and key custody before selecting vendors, specifying minimisation, encryption and retention in requirements for EDC, eCOA and health apps, and running the DPIA early enough to change the design. The evidence of these choices is also the best demonstration of accountability.
No. It also concerns protocol choices, vendor selection, responsibilities and working practices. Technical controls cannot fix unnecessary collection or unclear purposes on their own. Involve the people responsible for research operations and data protection early, so privacy requirements shape the workflow rather than being added as a final system check.
