The DPDPA (Digital Personal Data Protection Act, 2023), explained

A complete, plain-English guide to India's Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025: who it applies to, what it requires, and when.

Last updated 18 min read Reviewed by [Reviewer name, credentials]
TL;DR
  • The DPDPA (Digital Personal Data Protection Act, 2023) is India's data protection law, enacted by Parliament and administered by the Ministry of Electronics and Information Technology (MeitY). The Data Protection Board of India enforces it.
  • It applies to digital personal data processed in India, and to processing abroad that is connected with offering goods or services to people in India.
  • Businesses (Data Fiduciaries) must give clear notice, get valid consent or rely on a listed legitimate use, keep data secure, report breaches, honour individuals' rights and erase data they no longer need.
  • The DPDP Rules, 2025 were notified on 13 November 2025. Most obligations apply from 13 May 2027.
  • Penalties go up to ₹250 crore. The law requires compliance. It does not require a certificate.

What is the DPDPA?

The DPDPA is India's first comprehensive law on personal data. It sets out how organisations may collect and use digital personal data, what rights individuals have over it, and the penalties for getting it wrong.[1]

Its full name is the Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023). It is often shortened to DPDP Act, DPDPA or DPDP. Parliament passed it in August 2023, and it received Presidential assent on 11 August 2023.[1] The operational detail (how notices must look, how quickly to report breaches, how long to keep logs) sits in the Digital Personal Data Protection Rules, 2025, which MeitY notified on 13 November 2025.[2][3] See the DPDP Rules 2025 explained rule by rule.

Three bodies matter. Parliament made the law. MeitY administers it and frames the Rules. The Data Protection Board of India is the independent adjudicating body that inquires into breaches and imposes penalties.

Does the DPDPA apply to you?

If your organisation handles personal data in digital form in India, or offers goods or services to people in India from abroad, the DPDPA almost certainly applies. Size, sector and turnover don't change that.

Every company that has employees, customers, users or leads handles personal data. Smaller organisations don't get a general exemption. The Government can, however, notify narrower relief for certain classes, including start-ups (see exemptions). Try the quick check below. It runs in your browser and nothing is sent.

1. Does your organisation collect or use personal data, for example about customers, users, employees or leads?
2. Is any of it in digital form, or paper records that you later digitise (for example, scanned forms)?
3. Do you process it in India, or offer goods or services to people in India?
4. Is the processing only for an individual's personal or domestic purposes (not a business)?
5. Do you handle children's data (under 18), or personal data at very large scale?

Runs in your browser. Nothing you select is sent to us or stored.

Why the law exists

The DPDPA grew out of the Supreme Court's 2017 ruling that privacy is a fundamental right, and six years of drafting that followed.

  • 24 August 2017: Puttaswamy judgment. A nine-judge bench of the Supreme Court held in Justice K.S. Puttaswamy (Retd.) v. Union of India that privacy is a fundamental right protected under Article 21 and Part III of the Constitution. The judgment noted the need for a data protection regime.[4]
  • July 2017 – July 2018: the Srikrishna Committee. MeitY set up a Committee of Experts under Justice B.N. Srikrishna. Its report, A Free and Fair Digital Economy, and a draft Bill were submitted on 27 July 2018. The report framed the relationship between an individual and a company as a fiduciary one, and the Act keeps that idea.[5]
  • 2019–2022: earlier Bills. The Personal Data Protection Bill, 2019 went to a Joint Parliamentary Committee and was later withdrawn. MeitY then published a shorter draft Digital Personal Data Protection Bill in November 2022 for public consultation.
  • August 2023: the Act. The Digital Personal Data Protection Bill, 2023 was passed by both Houses and received assent on 11 August 2023.[1]
  • January–November 2025: the Rules. Draft Rules were published on 3 January 2025 for consultation, and the final Rules were notified on 13 November 2025.[2][3]

Key definitions

The Act uses its own vocabulary. Six terms carry most of the weight.

Personal data
Any data about an individual who is identifiable by or in relation to that data. The Act doesn't create a separate "sensitive" category.
Data Principal
The individual the data is about. For a child, this includes the parent or lawful guardian. For a person with a disability who has a lawful guardian, it includes that guardian.
Data Fiduciary
Anyone who, alone or with others, decides the purpose and means of processing personal data. Most businesses are Data Fiduciaries for at least their customer and employee data.
Data Processor
Anyone who processes personal data on behalf of a Data Fiduciary, such as a cloud host, payroll provider or support-desk vendor. The Data Fiduciary remains responsible for what its processors do.
Significant Data Fiduciary (SDF)
A Data Fiduciary, or class of them, that the Central Government designates based on factors such as the volume and sensitivity of data and the risk to individuals' rights. SDFs carry extra obligations.
Consent Manager
A company registered with the Board that gives individuals a single, interoperable platform to give, manage, review and withdraw consent across Data Fiduciaries. Registration conditions are in the First Schedule to the Rules and include being an Indian company with a net worth of at least ₹2 crore.[2]
Personal data breach
Any unauthorised processing, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data that compromises its confidentiality, integrity or availability. This is broader than "a hack". A mis-sent email can count.
Data Protection Board of India
The independent body set up under the Act to inquire into breaches, direct remedies and impose penalties. It works as a digital office.

Definitions are in Section 2 of the Act.[1]

Territorial scope and exemptions

The Act covers digital personal data processed in India, and processing outside India when it is connected with offering goods or services to people in India. Some purposes, such as personal or domestic use, are outside it.

What's covered

  • Personal data collected in digital form, or collected on paper and digitised later, when processed within India.
  • Processing outside India if it's connected with any activity related to offering goods or services to Data Principals in India. A foreign SaaS or e-commerce company selling to Indian users is covered.

What's not covered

  • Personal data processed by an individual for a personal or domestic purpose.
  • Personal data the individual has made publicly available themselves, or that someone else is legally obliged to make public.
  • Purely offline data that is never digitised.

Exemptions (Section 17)

Some processing is exempt from parts of the Act. Examples include enforcing legal rights or claims, functions of courts and tribunals, preventing and investigating offences, and processing in India of non-residents' data under a contract with a foreign party, which matters for Indian outsourcing and GCCs. Others are approved mergers and demergers, and ascertaining the financial position of loan defaulters. Research, archiving and statistical processing can also be exempt when the prescribed standards are met.[1]

Start-ups: read this carefully

Section 17(3) lets the Government notify classes of Data Fiduciaries, including start-ups, that are exempt from certain duties (such as some notice, accuracy and erasure requirements). MeitY has described a simplified compliance framework for start-ups.[7] As of 19 November 2026 we have not found a notification that exempts start-ups as a class. Plan to comply until an exemption is actually notified.

Grounds for processing: consent and legitimate uses

You may process personal data only for a lawful purpose, and only on one of two grounds: the individual's consent, or one of the "certain legitimate uses" listed in Section 7.

Unlike the GDPR, the DPDPA has no open-ended "legitimate interests" ground. The legitimate uses are a closed list, including:

  • Data the individual voluntarily provides for a specified purpose without objecting to its use. For example, a customer who shares their phone number to get an order update.
  • Performing a function under law, or complying with a law, judgment or order.
  • Responding to a medical emergency, an epidemic or a disaster.
  • Employment purposes, such as safeguarding the employer from loss or liability, preventing corporate espionage, and providing benefits the employee asks for.
  • Certain State functions, such as providing subsidies, benefits and services.

Everything else needs consent.[1]

Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the data the stated purpose needs. Every request for consent must come with a clear notice.

The notice

Under Section 5 and Rule 3, a notice must:[1][2]

  • stand on its own, so a person can understand it without reading anything else, and use clear, plain language;
  • give an itemised description of the personal data and the specific purpose it will be used for, including the goods, services or uses that processing enables;
  • provide a communication link (on your website or app, or another means) to withdraw consent as easily as it was given, exercise rights, and complain to the Board;
  • be available in English or any of the 22 languages in the Eighth Schedule to the Constitution, if the individual chooses.

Need a starting draft? Try our free consent notice generator.

Consent in practice

  • No pre-ticked boxes and no bundling. Consent to marketing can't be a condition of a service that doesn't need it.
  • Withdrawal must be as easy as giving consent. Once someone withdraws, you and your processors must stop processing within a reasonable time, unless the law requires otherwise. Processing done before withdrawal stays lawful.
  • For data you collected before the Act's commencement on the basis of consent, you must send a notice as soon as reasonably practicable.
  • Individuals may give and manage consent through a registered Consent Manager. Registration provisions took effect on 13 November 2026.
Key takeaway

If your sign-up flow has a single "I agree to the terms and privacy policy" checkbox covering everything, it will almost certainly need redesigning.

Data Fiduciary obligations

Beyond notice and consent, a Data Fiduciary must keep data accurate, protect it, report breaches, erase data it no longer needs, publish a contact for privacy questions, and run a working grievance process.

Accountability for processors

You're responsible for complying with the Act, including for processing your Data Processors carry out on your behalf. You may engage a processor only under a valid contract.[1]

Accuracy

Where personal data will be used to make a decision affecting the individual, or shared with another Data Fiduciary, you must make sure it is complete, accurate and consistent.

Reasonable security safeguards

Section 8(5) requires reasonable security safeguards to prevent a personal data breach, and failing to do so carries the highest penalty in the Act. Rule 6 sets minimums:[2]

  • encryption, obfuscation, masking or virtual tokens;
  • access controls over the computer resources used for processing;
  • logs, monitoring and review to detect and investigate unauthorised access;
  • backups and measures to keep processing going after a compromise;
  • retaining logs and personal data for at least one year to detect, investigate and remediate breaches, unless another law says otherwise;
  • security clauses in your contracts with Data Processors;
  • appropriate technical and organisational measures to make sure these safeguards are actually followed.

Breach notification

On becoming aware of a personal data breach, Rule 7 requires you to:[2][3]

  • inform each affected Data Principal without delay, in plain language, covering what happened, the likely consequences, what you're doing about it, what they can do to protect themselves, and who to contact;
  • inform the Board without delay, and then send a detailed report within 72 hours (or longer if the Board allows on written request) covering the facts, cause, mitigation, any findings about the person responsible, and the notifications sent to individuals.

There is no "low risk" exception. Every personal data breach must be reported to the Board and the affected people.

Retention and erasure

Erase personal data, and have your processors erase it, when consent is withdrawn or when it's reasonable to assume the purpose is no longer being served, whichever is earlier, unless a law requires you to keep it.[1] Under Rule 8 and the Third Schedule, large e-commerce entities (at least 2 crore registered users in India), online gaming intermediaries (at least 50 lakh) and social media intermediaries (at least 2 crore) must treat the purpose as served three years after the user last interacted, for most purposes. They must give users 48 hours' notice before erasure.[2] Separately, Rule 8(3) requires every Data Fiduciary to keep personal data, associated traffic data and processing logs for at least one year for the purposes in the Seventh Schedule.[2]

Contact person and grievance redressal

Publish the business contact details of a person who can answer questions about your processing, or your Data Protection Officer if you are an SDF, prominently on your website or app (Rule 9). Run an effective grievance mechanism that resolves complaints within a reasonable period of no more than 90 days (Rule 14).[2]

Children's data and persons with disabilities

Under the DPDPA a child is anyone under 18. Before processing a child's personal data you need the verifiable consent of a parent or lawful guardian, and you may not track, behaviourally monitor or target advertising at children.

  • Verifiable parental consent (Rule 10). Take appropriate technical and organisational measures to confirm that the person consenting is an identifiable adult and the child's parent. You can rely on identity and age details you already hold, details the person provides voluntarily, or a virtual token from a government-authorised entity such as a digital locker service.[2]
  • No detrimental processing. Don't process children's data in a way likely to harm a child's well-being.
  • No tracking, behavioural monitoring or targeted advertising directed at children.
  • Limited exemptions (Fourth Schedule). Some exemptions exist for specific purposes, including healthcare professionals, educational institutions and childcare providers, and only to the extent needed for things like the child's health, education or safety.[2]
  • Persons with disabilities. For a person with a disability who has a lawful guardian, the guardian's verifiable consent is needed (Rule 11), and you must verify the guardian's appointment. The DPDP (Removal of Difficulties) Order, 2026 corrected the wording of Section 9(1) to make clear that this applies to children and to persons with disabilities with a lawful guardian.[6]

Significant Data Fiduciaries

The Government can designate a company as a Significant Data Fiduciary based on the volume and sensitivity of the data it processes and the risks involved. SDFs must appoint an India-based DPO and an independent data auditor, and run regular impact assessments and audits.

Under Section 10 the Government considers factors including the volume and sensitivity of personal data, risk to individuals' rights, potential impact on India's sovereignty and integrity, electoral democracy, security of the State and public order.[1] An SDF must:

  • appoint a Data Protection Officer based in India, answerable to its board of directors or similar governing body, as the point of contact for grievances;
  • appoint an independent data auditor to carry out a data audit;
  • conduct a Data Protection Impact Assessment and an audit at least once every 12 months, and report significant observations to the Board (Rule 13);[2]
  • check that any algorithmic software it uses is not likely to pose a risk to individuals' rights;
  • follow any restrictions the Government sets, on the recommendation of a committee, about specified personal data that must not leave India.

The Removal of Difficulties Order, 2026 (5 October 2026) clarified that the periodic audit an SDF must undertake is a data audit.[6] In January 2026 MeitY consulted industry on bringing some SDF obligations forward from 18 to 12 months.[9] As of 19 November 2026 we have found no notification that changes the dates. See the timeline for updates.

Rights and duties of Data Principals

Individuals can ask what data you hold and who you've shared it with, have it corrected or erased, raise grievances, and nominate someone to act for them. They also have duties, such as not filing false complaints.

Data Principal rights (Sections 11–14)
RightWhat it means for you
Access to informationProvide a summary of the personal data you process and the processing activities, and the identities of other Data Fiduciaries and Processors you've shared it with.
Correction and erasureCorrect, complete, update or erase data on request, unless retention is legally required.
Grievance redressalOffer a readily available way to complain and resolve it within 90 days at most. Individuals must use your process before going to the Board.
NominationLet individuals nominate someone to exercise their rights if they die or become incapacitated.

Rule 14 requires you to publish how people can exercise these rights and what identifiers you need from them.[2] Data Principals also have duties under Section 15: comply with the law, don't impersonate anyone, don't suppress material information, don't file false or frivolous complaints, and give verifiably authentic information. Breaching these carries a penalty of up to ₹10,000.[1]

Cross-border data transfers

The DPDPA allows personal data to be transferred abroad by default. The Government can restrict transfers to countries it notifies, and stricter sector rules, such as RBI data localisation, still apply.

Section 16 takes a "negative list" approach: transfers are permitted unless the Central Government restricts them for a notified country or territory.[1] Rule 15 adds that transfers are subject to any requirements the Government specifies about making data available to a foreign State.[2] Any other Indian law that gives a higher degree of protection, or restricts transfers further, continues to apply.

The Data Protection Board, complaints and penalties

The Data Protection Board inquires into breaches, on a complaint, a reference or its own motion, and can impose penalties of up to ₹250 crore per breach as set out in the Schedule. Its decisions can be appealed to the Appellate Tribunal (TDSAT).

  • Established: the Board was established on 13 November 2025, with its head office in the National Capital Region, and the Rules fix it at four Members.[2]
  • Appointments: MeitY invited applications for the Chairperson and four Members in May 2026.[8] As of 19 November 2026, we have found no official notification of appointments.
  • Process: complaint, reference or intimation → preliminary review → inquiry with a hearing → directions or penalty. The Board can also accept a voluntary undertaking or refer parties to mediation.
  • Appeals: to the Telecom Disputes Settlement and Appellate Tribunal within 60 days.
  • Blocking: if a Data Fiduciary has been penalised in two or more instances, the Board can refer the matter to the Government, which may block public access to its platform.[1]
Penalty Schedule (summary)
BreachMaximum
Failing to take reasonable security safeguards (s. 8(5))₹250 crore
Failing to notify a personal data breach (s. 8(6))₹200 crore
Breaching the additional obligations on children's data (s. 9)₹200 crore
Breaching the additional obligations of an SDF (s. 10)₹150 crore
Breach of any other provision of the Act or Rules₹50 crore

Full penalty Schedule and how the Board decides amounts →

Implementation timeline

The DPDPA is coming into force in three phases: 13 November 2025, 13 November 2026 and 13 May 2027.

  1. 13 Nov 2025 In forceDefinitions; establishment and constitution of the Board (Sections 18–26); Rules 1, 2 and 17–21.[2]
  2. 13 Nov 2026 In forceConsent Manager registration: Section 6(9), Section 27(1)(d) and Rule 4.

The notification is dated 13 November 2025, but the Gazette was published electronically on 14 November 2025, so some summaries give 14 November dates. Check the Gazette text for your own planning. Full timeline →

DPDPA vs GDPR: key differences

If you already comply with the GDPR you have a head start, but not a free pass. The DPDPA has fewer lawful grounds, no sensitive-data category, a stricter definition of a child, and breach reporting that has no risk threshold.

TopicDPDPA (India)GDPR (EU)
Data coveredDigital personal data, or paper data later digitisedAll personal data, including structured paper records
Sensitive categoriesNone definedSpecial categories with extra conditions
Lawful groundsConsent or a closed list of legitimate usesSix bases, including legitimate interests and contract
ChildrenUnder 18; verifiable parental consentUnder 16 for online services (member states may lower to 13)
Breach reportingEvery breach, to the Board and affected people; detailed Board report within 72 hoursTo the regulator within 72 hours unless unlikely to pose a risk; to individuals if high risk
RightsAccess, correction, erasure, grievance, nominationAdds portability, objection, restriction and automated-decision rights
Cross-borderAllowed unless the country is restricted by notificationAdequacy decisions or safeguards such as SCCs
DPORequired for SDFs; must be based in IndiaRequired for certain controllers and processors
PenaltiesFixed maximums per breach type, up to ₹250 croreUp to €20m or 4% of global annual turnover

What this means for your business

With about six months until the main obligations apply, the practical work is to find your personal data, fix your notices and consent, tighten security and vendor contracts, and rehearse your breach response.

  1. Map your data. Record what personal data you hold, where it lives, why you hold it, who you share it with and how long you keep it.
  2. Pick the right ground for each purpose. Decide between consent and a legitimate use, and stop collecting what you don't need.
  3. Redesign notices and consent flows to the Rule 3 standard, with easy withdrawal.
  4. Raise security to the Rule 6 minimums, including one-year log retention, and update processor contracts.
  5. Build a breach playbook that can notify individuals without delay and file a detailed Board report within 72 hours.
  6. Stand up rights and grievance workflows that meet the 90-day limit.
  7. Set retention schedules and erasure routines, and check whether you handle children's data.
  8. Assign ownership. Publish a privacy contact, train your teams, and decide how you'll show compliance to customers.

Track all of this with our interactive DPDPA compliance checklist, and keep up with changes on what's new.

Want a second pair of eyes?

In a free 30-minute readiness call we'll go through your data flows and tell you plainly which of these steps matter most for you.

Book a free DPDPA readiness call

Sources

  1. The Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023), India Code, Legislative Department, Government of India. Consolidated text as on 19 November 2025
  2. Digital Personal Data Protection Rules, 2025, MeitY (Gazette notification dated 13 November 2025)
  3. Press Information Bureau: “DPDP Rules, 2025 Notified” backgrounder (17 November 2025)
  4. Supreme Court of India: Justice K.S. Puttaswamy (Retd.) v. Union of India, W.P.(C) No. 494 of 2012, judgment of 24 August 2017
  5. Committee of Experts under Justice B.N. Srikrishna: “A Free and Fair Digital Economy”, report to MeitY (27 July 2018)
  6. Digital Personal Data Protection (Removal of Difficulties) Order, 2026, S.O. 5458(E), Gazette of India (issued 5 October 2026, published 6 October 2026). Search the e-Gazette for S.O. 5458(E)
  7. MeitY / Digital India: “Simplified compliance framework for start-ups and certain data fiduciaries under DPDP Act and Rules” (PIB, 3 December 2025)
  8. MeitY circular F. No. 2(1)/2026-Pers.I: appointment to the posts of Chairperson and Members, Data Protection Board of India (6 May 2026)
  9. Press Information Bureau: MeitY stakeholder consultation on the DPDP Rules implementation timeline (22 January 2026)