privacy-by-design

Map the data lifecycle for new features, select lawful bases, and define retention and user-rights handling before implementation. This structured workflow makes privacy requirements explicit, enforceable, and testable prior to writing code.

Privacy-by-design is a framework that proactively integrates data minimization, purpose limitation, and user-rights readiness into product decisions. You need to apply it when building features that process personal data, ensuring governance controls are defined before implementation begins.

Define data minimization and lawful basis by mapping the data lifecycle for your feature and selecting appropriate legal bases before development. This ensures explicit purpose limitation and retention boundaries are established and documented prior to implementation.

Yes, this workflow applies to features that process personal data across product development, privacy risk assessment, and governance teams. It guides cross-team governance by ensuring privacy controls are defined before implementation through templates and reference materials.

The workflow focuses on defining privacy controls before implementation and does not handle post-launch monitoring. It provides templates and reference materials for purpose limitation and retention boundaries, but requires manual integration into existing feature development lifecycles.