Quick answer
The Digital Personal Data Protection Act, 2023 (Act 22 of 2023) is India's general data protection law. It governs digital personal data processed in India, and abroad when linked to offering goods or services in India. It requires consent or a legitimate use, security safeguards and breach intimation, grants individuals rights, and allows penalties up to ₹250 crore. Most obligations apply from 13 May 2027.
- The DPDP Act received assent on 11 August 2023 and is implemented through the DPDP Rules, 2025, notified on 13 November 2025.
- It applies to digital personal data processed in India and to processing abroad linked to offering goods or services to people in India.
- Processing needs either consent under section 6 or one of the legitimate uses in section 7.
- Penalties run up to ₹250 crore per instance, decided by the Data Protection Board, with appeals to TDSAT.
- Board provisions are live; Consent Manager registration started 13 November 2026; core obligations start 13 May 2027.
Who this is for: Founders and CEOs of Indian companies, CTOs and engineering leaders, Foreign companies serving Indian users, Compliance, legal and privacy teams, Data Protection Officers
What is the DPDP Act and who does it apply to?
The Digital Personal Data Protection Act, 2023 is India's first comprehensive law on personal data. It received Presidential assent on 11 August 2023 and is implemented through the DPDP Rules, 2025, notified on 13 November 2025.
Territorial scope (section 3)
The Act applies to processing of:
- digital personal data within India, whether collected digitally or collected offline and digitised later; and
- personal data processed outside India, if the processing is connected to offering goods or services to Data Principals in India.
So a foreign SaaS company selling to Indian users is covered even without an Indian entity. See territorial scope.
What is excluded
- Processing by an individual for personal or domestic purposes.
- Personal data made publicly available by the Data Principal herself, or by someone under a legal obligation to publish it. See publicly available data.
"Personal data" means any data about an individual who is identifiable by or in relation to that data. Unlike the GDPR and the old SPDI Rules, the Act has no separate category of sensitive personal data, although sensitivity matters for Significant Data Fiduciary designation and penalties. See what counts as personal data.
Key roles: Data Principal, Fiduciary, Processor and others
The Act uses its own vocabulary. Getting the roles right determines who owes which duty.
| Role | Who it is | Main point |
|---|---|---|
| Data Principal | The individual the data relates to; for a child, includes parents or lawful guardian; for a person with disability, includes the lawful guardian | Holds rights and owes limited duties |
| Data Fiduciary | Determines the purpose and means of processing | Bears almost all obligations |
| Data Processor | Processes on behalf of a fiduciary | Bound by contract; the fiduciary stays responsible |
| Consent Manager | Registered platform for giving, managing, reviewing and withdrawing consent | Registers with the Board; acts in a fiduciary capacity |
| Significant Data Fiduciary | Fiduciary notified by government on volume, sensitivity and risk | Extra duties: DPO, auditor, DPIA |
| Data Protection Board | Adjudicating body | Inquiries, directions, penalties |
| Appellate Tribunal | TDSAT | Hears appeals from Board orders |
The most important practical rule: a Data Fiduciary is responsible for processing done by its processors (section 8(1)). Using a cloud provider, analytics vendor or LLM API does not move liability. See Data Fiduciary vs Data Processor and the DPDP glossary.
When can you process personal data? Consent and legitimate uses
Section 4 allows processing only for a lawful purpose and on one of two grounds.
1. Consent (sections 5 and 6)
Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the data necessary for the specified purpose. It must be preceded by a notice; Rule 3 requires the notice to be standalone, in clear and plain language, with an itemised list of data, the purposes and links to withdraw consent, exercise rights and complain to the Board.
Withdrawal must be as easy as giving consent. After withdrawal the fiduciary must stop processing within a reasonable time and make its processors stop. For consents obtained before the Act, notice must be given as soon as reasonably practicable. See consent requirements, privacy notice requirements and consent withdrawal UX.
2. Legitimate uses (section 7)
No consent is needed for listed uses, including: data voluntarily provided for a specified purpose where the person has not objected; State subsidies, benefits, services and licences; legal obligations; court orders; medical emergencies; epidemics; disasters or breakdown of public order; and employment purposes. See legitimate uses.
Consent can also be managed through a registered Consent Manager, a regime live since 13 November 2026.
What must every Data Fiduciary do? (section 8)
Section 8 sets the general obligations that apply to every fiduciary, large or small. The Rules add detail.
| Obligation | Act | Rules detail |
|---|---|---|
| Use processors only under a valid contract | s.8(2) | Rule 6(1)(f) security clauses |
| Keep data complete, accurate and consistent when used for decisions or disclosed | s.8(3) | — |
| Reasonable security safeguards | s.8(5) | Rule 6: encryption, masking or tokens, access control, logs, backups, one-year log retention |
| Intimate every personal data breach to the Board and affected individuals | s.8(6) | Rule 7: without delay, detailed report to the Board within 72 hours |
| Erase data when consent is withdrawn or purpose is served, unless law requires retention | s.8(7) | Rule 8: deemed purpose expiry for large platforms; one-year minimum retention in Rule 8(3) |
| Publish a DPO or contact person | s.8(9) | Rule 9 |
| Run effective grievance redressal | s.8(10) | Rule 14(3): published period, not more than 90 days |
Two points surprise teams. First, there is no materiality threshold for breach intimation: every breach is reportable. Second, Rule 8(3) requires keeping personal data, traffic data and logs for at least a year even if the user deletes her account.
Deep dives: security safeguards, 72-hour breach rule, retention and erasure, one-year log retention.
Children's data and Significant Data Fiduciaries
Children (section 9)
A child is anyone under 18. Fiduciaries must:
- obtain verifiable parental consent before processing a child's data — Rule 10 explains how to check that the parent is an identifiable adult, including via virtual tokens and DigiLocker;
- not undertake processing likely to cause a detrimental effect on a child's well-being; and
- not carry out tracking, behavioural monitoring or targeted advertising directed at children.
The Fourth Schedule exempts specified classes (such as clinical establishments, educational institutions and crèches) and purposes (such as real-time location for safety) from the consent and tracking rules, but never from the bar on detrimental processing. See verifiable parental consent, children's data exemptions and children's data obligations.
Significant Data Fiduciaries (section 10)
The government may notify fiduciaries as SDFs based on factors such as the volume and sensitivity of data, risk to Data Principals, and potential impact on sovereignty, electoral democracy, State security and public order. Once notified, an SDF must appoint a DPO based in India, an independent data auditor, and conduct periodic DPIAs and audits. Rule 13 adds an annual DPIA and audit, algorithmic due diligence and possible localisation of specified data. No SDF has been notified yet. See SDF obligations and SDF criteria.
Rights and duties of Data Principals
Rights
| Right | Section | What it gives |
|---|---|---|
| Access to information | s.11 | Summary of data and processing, and identities of other fiduciaries and processors it was shared with |
| Correction and erasure | s.12 | Correction, completion, updating and erasure |
| Grievance redressal | s.13 | A response from the fiduciary; must be exhausted before approaching the Board |
| Nomination | s.14 | Nominate someone to exercise rights in case of death or incapacity |
Rule 14 makes these rights operational: fiduciaries must publish how to make a request and which identifiers (username, customer ID, email, mobile number and so on) are needed, publish a grievance response period of no more than 90 days, and allow nomination of one or more individuals. See Data Principal rights, the 90-day rule and right to nominate.
Duties (section 15)
Unusually, the Act also places duties on individuals: comply with applicable law, not impersonate anyone, not suppress material information when providing data for official documents, not file false or frivolous complaints, and provide only verifiably authentic information when seeking correction. Breach carries a penalty of up to ₹10,000. See duties of Data Principals.
Cross-border transfers and exemptions
Cross-border transfers (section 16)
The Act takes a negative-list approach: transfers are allowed except to countries the Central Government restricts by notification. Stricter sectoral rules, such as RBI's payment data storage requirements, continue to prevail. Rule 15 adds that fiduciaries must meet any requirements the government specifies by order about making data available to a foreign State or entities it controls. There is no general localisation mandate; the exception is Rule 13(4) for data specified for SDFs. See cross-border transfers and data localisation for AI workloads.
Exemptions (section 17)
Key exemptions include processing for:
- enforcing legal rights or claims, and by courts and tribunals;
- preventing, detecting, investigating or prosecuting offences;
- data of non-Indian residents processed in India under a contract with a foreign person — most obligations do not apply, but security safeguards still do;
- court-approved mergers and schemes, and ascertaining financial information of loan defaulters;
- notified State instrumentalities; and
- research, archiving and statistics under the Second Schedule standards (Rule 16).
The government may also exempt classes of fiduciaries, including startups, from certain provisions. See section 17 exemptions and research exemption.
Enforcement: the Board, penalties and appeals
The Data Protection Board of India enforces the Act. It acts on breach intimations, complaints, government references and court directions, and must finish an inquiry within six months, extendable by up to three months at a time (Rule 19(9)). See how a Board inquiry works.
Penalties (Schedule, per instance)
| Breach | Maximum |
|---|---|
| Failure to take reasonable security safeguards | ₹250 crore |
| Failure to notify a breach | ₹200 crore |
| Children's data obligations | ₹200 crore |
| SDF additional obligations | ₹150 crore |
| Any other provision | ₹50 crore |
| Data Principal duties | ₹10,000 |
Breach of a voluntary undertaking attracts up to the amount for the underlying breach. The Board weighs factors including gravity, duration, type of data, repetition, gains made or losses avoided, and mitigation. Penalties go to the Consolidated Fund of India, not to individuals. After penalties in two or more instances, the government may block public access to a platform on the Board's reference (section 37). See DPDP penalties explained.
Appeals lie to TDSAT within 60 days (section 29), filed digitally under Rule 22. See appeals to TDSAT.
When does the DPDP Act apply, and what should you do now?
The Act is being commenced in three phases.
| Date | What came or comes into force |
|---|---|
| 13 Nov 2025 | Sections 1(2), 2, 18–26 (Board), 35, 38–43, 44(1) and 44(3); Rules 1, 2 and 17–21 |
| 13 Nov 2026 | Section 6(9) and 27(1)(d) — Consent Manager registration; Rule 4 |
| 13 May 2027 | All remaining sections, including obligations, rights and penalties; Rules 3, 5–16, 22 and 23 |
Section 44(2) omits section 43A of the IT Act, the basis of the SPDI Rules, 2011, from 13 May 2027 — so the SPDI regime continues until then. See DPDP and the SPDI Rules and the full commencement timeline.
With about six months to go, prioritise:
- A data map of what you collect, why, where it lives and which processors touch it.
- Rule 3 notices and consent flows, with withdrawal as easy as consent.
- Rule 6 security controls and Rule 7 breach runbooks.
- Retention and erasure, including the one-year minimum log rule.
- Rights request and grievance handling within 90 days.
- Processor contracts.
For a sequenced plan, see the compliance roadmap to May 2027; AI teams should also read DPDP for AI systems.
Further reading on suhasbhairav.com
- BlogData Privacy Laws for AI Users: Enterprise Patterns
- BlogCross-Border Data Compliance for Agentic AI Systems
- AI AgentsAI Agents for Privacy and GDPR Requests in Legal and Compliance
- AI Use CasesAI Agent Use Case: Gdpr Consultants Using Website Forms and Data Flows to Identify Privacy Risks
- AI SkillsAGENTS.md Template for Privacy and Data Governance Agents
Key dates
DPDP Act, 2023 receives Presidential assent
Draft DPDP Rules published for consultation (G.S.R. 02(E))
DPDP Rules, 2025 notified; Board provisions in force
Consent Manager registration provisions in force
Core obligations, rights, penalties and remaining Rules in force; IT Act section 43A omitted
Answers
Frequently asked questions
Is the DPDP Act 2023 in force?
Is the DPDP Act 2023 in force?
Partly. The Board provisions and definitions came into force on 13 November 2025, and Consent Manager registration on 13 November 2026. The core obligations on Data Fiduciaries, Data Principal rights and penalties come into force on 13 May 2027, along with most of the DPDP Rules, 2025.
Does the DPDP Act apply to foreign companies?
Does the DPDP Act apply to foreign companies?
Yes, where they process personal data of individuals in India in connection with offering goods or services to them. Section 3 extends the Act to processing outside India in that situation, so a foreign app or SaaS product with Indian users is covered even if it has no office or entity in India.
What is the maximum penalty under the DPDP Act?
What is the maximum penalty under the DPDP Act?
The highest penalty in the Schedule is up to ₹250 crore per instance, for failing to take reasonable security safeguards to prevent a personal data breach. Failure to notify a breach and breaches of children's data obligations carry up to ₹200 crore each. The Board decides the amount after an inquiry.
Does every company need a Data Protection Officer under the DPDP Act?
Does every company need a Data Protection Officer under the DPDP Act?
No. Only Significant Data Fiduciaries must appoint a DPO, who must be based in India. Every other Data Fiduciary must publish the business contact information of a person who can answer Data Principals' questions about processing, under section 8(9) and Rule 9.
Does the DPDP Act cover offline or paper records?
Does the DPDP Act cover offline or paper records?
Only once they are digitised. The Act applies to digital personal data, including data collected in non-digital form and digitised later. Purely paper records that are never digitised fall outside it, though other laws may still apply to them.
How is the DPDP Act different from the GDPR?
How is the DPDP Act different from the GDPR?
The DPDP Act has fewer lawful grounds, no separate sensitive data category, a single age threshold of 18 for children, no materiality threshold for breach reporting, a negative-list approach to transfers and fixed rupee penalty caps instead of turnover-based fines. The DPDP Act vs GDPR page has a full side-by-side comparison.
Legal references and sources
- Digital Personal Data Protection Act, 2023 — Sections 3–17 and Schedule (official text)
- Digital Personal Data Protection Rules, 2025 — Rules 1–23 (official text)
- Gazette of India — G.S.R. 846(E), 13 November 2025 (official text)
- MeitY data protection framework (DPDP Act and Rules) ↗
- DPDP Rules, 2025 (G.S.R. 846(E)) full text ↗
- Gazette of India ↗
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- DPDP Rules 2025DPDP Rules 2025 Explained: The Complete Guide for Indian CompaniesA rule-by-rule guide to all 23 rules and seven schedules of the DPDP Rules, 2025: what each requires, when it applies, and what to build before 13 May 2027.
- DPDP Act 2023DPDP Act vs GDPR: Side-by-Side Comparison for Tech TeamsA row-by-row comparison of India's DPDP Act 2023 and Rules 2025 with the EU GDPR: scope, lawful bases, children, rights, breach timelines, DPOs, transfers and penalties.
- DPDP Act 2023DPDP Penalties Explained: What a Data Breach CostsThe full DPDP Act penalty schedule, from ₹10,000 to ₹250 crore per instance, the section 33(2) factors the Board weighs, and how penalties are imposed and appealed.
- DPDP Act 2023Who Does the DPDP Act Apply To? Territorial Scope ExplainedSection 3 of the DPDP Act decides who is in scope: anyone processing digital personal data in India, and offshore businesses offering goods or services to people in India.
- DPDP Act 2023DPDP Consent Requirements: Free, Specific, Informed and UnambiguousWhat valid consent means under section 6 of the DPDP Act and Rule 3: the five qualities, clear affirmative action, necessity, withdrawal parity and proof of consent.
- Templates & playbooksDPDP Compliance Roadmap to May 2027A month-by-month DPDP compliance plan from December 2026 to 13 May 2027, when Rules 3, 5–16, 22 and 23 take effect: inventory, notices, security, breach, retention and rights.