India DPDPA — Digital Personal Data Protection Act, 2023 Skill

How to Respond

DPDPA at a Glance

Digital Personal Data Protection Act, 2023

• Presidential Assent: 11 August 2023
• Rules notified: 13 November 2025 (Digital Personal Data Protection Rules, 2025)
• Board operational: 13 November 2025 (Sections 18–26 effective immediately)
• Full compliance deadline: 13 May 2027 (18 months from Rules notification)
• Enforcement body: Data Protection Board of India (DPBI)
• Appeals: Telecom Disputes Settlement and Appellate Tribunal (TDSAT)
• Administered by: Ministry of Electronics and Information Technology (MeitY)

Scope and Application (Sections 1 and 3)

Who is a Data Fiduciary? Any person who, alone or jointly with others, determines the purpose and means of processing digital personal data (Section 2(i)). Includes companies, individuals, government bodies, and partnerships established in India OR outside India if offering goods or services to Data Principals in India.

Territorial scope (Section 3):

• Processing of digital personal data within India's territory, and
• Processing outside India where it relates to offering goods or services to individuals located in India at the time of collection.

Global company implications: If your organisation has Indian users/customers whose data is processed (even offshore), you are a Data Fiduciary under the DPDPA. The Act's extra-territorial reach is explicit. Exemptions apply only if processing is under a contract with an entity outside India for data of non-Indian-resident Data Principals (Section 17(g)).

What data is covered? Only digital personal data — data in digital form. Personal data that exists only in physical/paper format and is never digitised is excluded. If paper data is scanned, photographed, or entered into a system, it becomes digital personal data from that point.

Chapter II — Data Fiduciary Obligations (Sections 4–10)

Section 4 — Grounds for Processing

Two and only two lawful bases exist:

No other basis exists. Processing outside these two is unlawful.

Section 5 — Notice

Before or at the time of collecting personal data, Data Fiduciaries must provide a notice to the Data Principal (implemented by Rule 3 of the DPDP Rules 2025):

Mandatory notice elements (Rule 3):

• Clear, concise language — jargon-free; comprehensible to the average person
• Independent presentation — not buried in terms and conditions; standalone notice
• Itemised list of personal data to be collected
• Specific purpose(s) of processing
• Categories of recipients with whom data will be shared
• Retention period
• How the Data Principal can exercise their rights (access, correction, erasure, grievance, nomination)
• How to file a complaint with the Data Protection Board
• How to withdraw consent (mechanism must be as easy as giving consent)

Common gap: Privacy policies that bundle consent with service access, bury data categories in generic language, or omit the Board complaint pathway do not comply with Rule 3.

Section 6 — Consent

Valid consent must be:

• Free — not conditioned on accepting services; no bundled consent
• Specific — tied to a particular specified purpose; not blanket consent
• Informed — given after receiving the Rule 3 notice
• Unconditional — no conditions or coercion attached
• Unambiguous — given by clear affirmative action (explicit checkbox, active opt-in)

What is NOT valid consent:

• Pre-ticked boxes (dark patterns)
• Opt-out mechanisms ("unless you object, we will process")
• Blanket "I agree to privacy policy" covering multiple unrelated purposes
• Consent bundled with access to a service ("use our app = consent to all data uses")
• Silence or inaction

Withdrawal of consent:

• Data Principals may withdraw consent at any time (Section 6(4))
• Ease of withdrawal must equal ease of giving consent (one-click withdrawal if one-click consent was used)
• Withdrawal does not affect lawfulness of processing before withdrawal
• Upon withdrawal, the Data Fiduciary must cease processing and erase data (unless retention required by law)

Section 7 — Certain Legitimate Uses (Closed List)

The eight enumerated legitimate uses where consent is not required:

Key precision on Item 5: The employment clause (Section 7(e)) covers both routine HR processing AND an employer's legitimate interest in preventing corporate espionage, IP theft, and leakage of classified information by employees. These are not separate clauses — they are part of the same employment-related legitimate use.

Critical point: This is an exhaustive list. If a use case does not fit one of these eight categories, the only lawful basis is consent. "Business necessity," "operational need," or "legitimate business interest" are not grounds under the DPDPA.

Section 8 — General Obligations of Data Fiduciary

All Data Fiduciaries must:

1. Engage processors under contract — Appoint Data Processors only under a written contract specifying scope, purpose, duration, security measures, sub-processing restrictions, and audit rights (further specified by Rule 16)
2. Ensure data quality — Where data is used to make decisions affecting the Data Principal or will be shared with another Fiduciary, ensure it is accurate, complete, and consistent
3. Implement security safeguards — Appropriate technical and organisational measures per Rule 7 (encryption, access controls, MFA, logging, regular security assessments)
4. Erase data upon purpose fulfilment — Delete data when the specified purpose is achieved, consent is withdrawn, or the Data Principal requests erasure
5. Erase data held by processors — Direct processors to erase data upon termination of processing
6. Notify breach — Report personal data breaches to the Board without delay and within 72 hours per Rule 6

Section 9 — Processing of Personal Data of Children

Definition: "Child" means an individual who has not completed 18 years of age (Section 2(f)).

Mandatory requirements:

• Obtain verifiable parental/lawful guardian consent before processing any personal data of a child (Section 9(1))
• Implement age verification mechanisms in onboarding/registration (Rule 10)

Prohibited activities (Section 9(2)) — applies to all Data Fiduciaries:

• Tracking or behavioural monitoring of children (GPS, activity profiling, clickstream analysis)
• Targeted advertising directed at children (personalised ads, recommendation algorithms, marketing based on child profile)
• Detrimental processing — any processing likely to cause detrimental effect on a child's well-being (physical, mental, emotional, developmental harm)

Parental consent verification methods (Rule 12):

• Use of existing user data (age/identity already held by the platform)
• Voluntary self-declaration by the parent/guardian
• Token-based verification via:
  • Government or government-mandated entities
  • DigiLocker (India's official digital document wallet)
  • Notified token-issuing bodies

Exemptions from Section 9: Processing without parental consent is permitted only when strictly necessary for:

• Health and safety of the child (emergency medical treatment, child safety services)
• Essential services as prescribed (age-appropriate educational platforms, child safety apps)
• Law enforcement (crime prevention, investigation involving the child)

Penalty: Violations of Section 9 carry a maximum penalty of ₹200 crore — one of the highest penalty tiers.

Section 10 — Additional Obligations of Significant Data Fiduciaries (SDFs)

Designation: The Central Government notifies specific organisations as SDFs based on:

• Volume and sensitivity of personal data processed
• Risk of harm to Data Principals' rights and freedoms
• Potential impact on India's sovereignty, integrity, security, or electoral democracy
• Risk to public order

Note: As of April 2026, no specific organisations have been publicly designated as SDFs. Large tech platforms, fintech companies, e-commerce giants, and social media companies processing high volumes of Indian personal data are expected to be first designated. Organisations matching the criteria should self-assess and prepare.

Additional obligations (Section 10 + Rule 13):

Chapter III — Rights and Duties of Data Principals (Sections 11–15)

Data Principal Rights

Response timeframe: Rules specify prescribed timelines (expected 30–45 days for most requests). Monitor MeitY notifications for exact timelines.

Limits on erasure: Data Fiduciaries may refuse erasure where:

• Retention is necessary for the specified purpose (ongoing service, contractual need)
• Retention is required by Indian law (tax records, legal dispute, statutory holding periods)
• Retention is necessary to enforce legal rights or defend claims

Section 15 — Duties of Data Principals

Data Principals also have duties — an unusual feature absent from GDPR:

• Not register false complaints with the Board or the Fiduciary
• Not furnish false information or suppress material facts
• Not impersonate another individual
• Not misuse grievance mechanisms to harass Data Fiduciaries

Violation of these duties may result in personal penalties up to ₹10,000.

Chapter IV — Special Provisions (Sections 16–17)

Section 16 — Cross-Border Data Transfers

Mechanism: Blacklist approach (unlike GDPR's whitelist/adequacy approach)

• Data Fiduciaries may transfer personal data to any country or territory outside India, except those specifically notified by the Central Government as restricted.
• Current status (April 2026): No countries have been notified as restricted. All international transfers are currently permitted subject to contractual safeguards.
• Future notifications may restrict transfers. Monitor the MeitY Official Gazette.
• Recommended practice: Even pending notification, apply reasonable contractual protections with recipients; avoid transferring sensitive categories of data offshore unnecessarily.

GDPR contrast: GDPR requires a positive transfer mechanism (adequacy decision, SCCs, BCRs, etc.) for every cross-border transfer. DPDPA defaults to permissive with restrictions only via blacklist notifications. Operationally simpler but legally uncertain.

Section 17 — Exemptions

Chapter V — Data Protection Board of India (Sections 18–26)

The Board is not a traditional regulator. It is primarily an adjudicatory body:

What the Board CANNOT do:

• Issue regulatory guidance or binding standards
• Proactively investigate without a complaint or breach notification
• Issue adequacy decisions or approve transfer mechanisms
• Make rules (rule-making power rests with the Central Government / MeitY)

Complaint process:

1. Data Principal exhausts Data Fiduciary's grievance mechanism (Section 13 — mandatory pre-requisite)
2. If unsatisfied, files complaint with the Board via digital portal
3. Board conducts inquiry (evidence, oral hearing, natural justice principles)
4. Board issues order with detailed reasons
5. Dissatisfied party appeals to TDSAT within prescribed period

Penalties (Section 33 and Schedule)

Penalty determination — 7 factors Board must consider (Section 33(2)):

1. Nature and gravity of the violation
2. Scope of impact on Data Principals (individual vs. systemic/mass)
3. Frequency (first-time vs. repeated violation)
4. Promptness of remediation and cooperation with the Board
5. Proportionality to the financial condition of the violator
6. Intentionality vs. negligence
7. Any other prescribed factors

Full penalties apply from: 13 May 2027. No phased enforcement reduction.

DPDPA Compliance Gap Analysis

Gap Analysis — Data Fiduciary (All Entities)

Gap Analysis — Children's Data (Section 9)

Gap Analysis — Significant Data Fiduciary (Section 10, if applicable)

Reference Files

• references/sections-reference.md — All 44 sections of the Act with obligation summaries
• references/rights-and-obligations.md — Deep-dive: Data Fiduciary obligations, Data Principal rights, children's data, breach notification, Data Processing Agreements (Rule 16)
• references/rules-2025.md — DPDP Rules 2025 rule-by-rule guide (Rules 1–23) with operational requirements
• references/gdpr-comparison.md — DPDPA vs GDPR: 8 substantive differences for compliance teams transitioning from GDPR