Privacy by Design and Data Minimization
Good privacy architecture limits unnecessary data before it creates unnecessary risk.
Privacy by design
Privacy considerations are embedded into system design, defaults, workflows, and controls from the beginning.
Data minimization
Organizations collect, use, retain, and disclose only the personal data reasonably needed for the stated purpose.
Risk reduction
Less unnecessary data means a smaller privacy and breach exposure surface.
Exam strategy
If a control reduces collection before data enters the system, think minimization and design-stage privacy.
The takeaway
Privacy by design embeds protection early; data minimization reduces unnecessary collection and retention.
Related Summit resources
FAQ
What is the core idea?
Privacy by design embeds protection early; data minimization reduces unnecessary collection and retention.
What should you identify first?
Good privacy architecture limits unnecessary data before it creates unnecessary risk.
Why does this matter on the CPA Exam?
Understand why privacy controls should be built into systems rather than added only after deployment.