Obligations

Privacy by Design

Defined in §8(4), DPDPA 2023; Rule 6(1), Rules 2025

Embedding data protection principles into the design and architecture of systems from the very beginning.

What does “Privacy by Design” mean?

Privacy by Design requires organisations to consider data protection throughout the entire lifecycle of systems and processes — from initial design through deployment and decommissioning. Under DPDPA Section 8(4), Data Fiduciaries must implement appropriate technical and organisational measures to ensure effective adherence to the Act. This means building privacy into product architecture rather than bolting it on after development.

Why does this matter for your business?

Retrofitting privacy into existing systems is 10x more expensive than building it in from the start. Privacy by Design reduces breach risk, simplifies compliance audits, and demonstrates proactive accountability to the Board.

Real example

A Bengaluru startup building a new CRM designs it with: purpose-tagged data fields, automated retention enforcement, granular access controls, consent-linked data visibility, and built-in anonymisation pipelines — all before writing the first line of business logic.

Common misconception

Privacy by Design does not mean making every feature privacy-restrictive by default. It means thoughtfully considering privacy implications at each design decision and implementing appropriate controls.

Related terms

DPDPA Shield automates Compliance Dashboard. See how →