What does privacy by design entail?

• A. Embedding privacy requirements into systems and processes from the outset; implement data minimization, default privacy settings, and impact assessments early.
• B. Applying privacy measures only after deployment.
• C. Treating privacy as a separate, non-integrated function.
• D. Collecting as much personal data as possible to maximize analytics.

Answer: (A)

Privacy by design means weaving privacy into every part of a system from the very start. It’s about designing with privacy in mind from the beginning, applying data minimization, setting strong default privacy controls, and conducting privacy impact assessments early so risks can be identified and mitigated before any deployment. When these protections are built into the design, privacy becomes the default behavior rather than something added later.

Options that wait to apply privacy after launch, treat privacy as a separate, standalone function, or aim to collect as much data as possible run counter to this approach, because they don’t embed privacy protections into the core design or limit data usage from the outset.