← All guides

The DPDP Act, 2023 and DPDP Rules, 2025: a practical guide to India's data protection law

What the Digital Personal Data Protection Act requires, when each part of the DPDP Rules applies, and how teams that hold personal data inside documents can prepare for 13 May 2027.

THE SHORT ANSWER

The Digital Personal Data Protection Act, 2023 (DPDP Act) is India's law on digital personal data. It lets organizations ("Data Fiduciaries") process personal data only with an individual's consent or for specified legitimate uses, requires security safeguards and breach notification, gives individuals rights to information, correction and erasure, and allows penalties of up to ₹250 crore.

The Act was passed in August 2023, but most of it waited for the Digital Personal Data Protection Rules, 2025, which the Ministry of Electronics and Information Technology (MeitY) notified in the Gazette on 13 November 2025. The Rules switch the law on in three phases over eighteen months, ending on 13 May 2027.

Not legal advice. This is an educational summary prepared by GritWorks, a software company, not a law firm. Read the Act and the Rules for the exact text, and take advice from qualified counsel on how they apply to you.

DPDP Rules 2025: the phased timeline

Rule 1 of the DPDP Rules sets three commencement dates, each counted from the date the Rules were published in the Gazette of India (G.S.R. 846(E), 13 November 2025).

  1. Act enactedThe Digital Personal Data Protection Act, 2023 received assent and was published in the Gazette.
  2. Rules notified, phase 1The DPDP Rules, 2025 were published in the Gazette (G.S.R. 846(E)). Rules 1, 2 and 17 to 21, which set up the Data Protection Board of India and its working as a digital office, came into force on publication.
  3. Phase 2: consent managersRule 4 came into force one year after publication. Consent managers, which must be companies incorporated in India with a net worth of at least ₹2 crore, can apply to the Board for registration.
  4. Phase 3: most obligationsRules 3, 5 to 16, 22 and 23 come into force eighteen months after publication: notices, security safeguards, breach intimation, retention and erasure, children's data, Significant Data Fiduciary duties, Data Principal rights and cross-border transfers.

As of 17 November 2026, phase 2 is in force and the main compliance deadline is 13 May 2027. Until then, the Information Technology Act, 2000 and its existing rules on sensitive personal data continue to apply. Check MeitY and the eGazette for any amendment before relying on these dates.

What counts as personal data under the DPDP Act

The Act defines personal data as "any data about an individual who is identifiable by or in relation to such data". It applies to digital personal data: data collected in digital form, and data collected on paper and digitized later (Section 3). A scanned application form, a PDF bank statement or a phone photo of an identity card is digital personal data once it sits in your systems.

  • Data Principal: the individual the data is about (for a child, including the parent or lawful guardian).
  • Data Fiduciary: whoever decides the purpose and means of processing, alone or with others.
  • Data Processor: anyone processing personal data on a Data Fiduciary's behalf, such as an OCR vendor, a cloud host or an AI service. The Data Fiduciary stays responsible for what its processors do (Section 8(1)).

The Act also applies outside India when processing is connected with offering goods or services to people in India. It does not apply to personal or domestic use, or to personal data that the person concerned (or someone legally required to) has made publicly available.

Processing needs a lawful purpose and either consent or one of the "certain legitimate uses" in Section 7 (Section 4).

  • Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the personal data necessary for the specified purpose (Section 6(1)). It can be withdrawn as easily as it was given.
  • Notice must come with or before the consent request. Under Rule 3 it must stand on its own, use clear and plain language, give an itemized description of the personal data and the specific purpose, and explain how to withdraw consent, exercise rights and complain to the Board.
  • Legitimate uses include data a person voluntarily provides for a specified purpose without objecting to its use, certain State functions, compliance with law or court orders, medical emergencies, disasters and specified employment purposes.
  • Consent managers are registered platforms through which people give, manage, review and withdraw consent across services. Their registration rules (Rule 4) took effect on 13 November 2026.

Key obligations for Data Fiduciaries

  • Reasonable security safeguards (Section 8(5), Rule 6): at minimum, measures such as encryption, obfuscation, masking or virtual tokens; access controls; logs and monitoring to detect unauthorized access; backups for continuity; one-year retention of those logs; and security terms in contracts with Data Processors.
  • Breach intimation (Section 8(6), Rule 7): tell each affected Data Principal without delay, and tell the Board without delay, followed by a detailed report within 72 hours of becoming aware of the breach.
  • Accuracy where data is used for a decision about the person or shared with another Data Fiduciary (Section 8(3)).
  • Erasure once consent is withdrawn or the specified purpose is no longer served, unless the law requires retention, and the same from processors (Section 8(7)). Rule 8 sets three-year inactivity periods for large e-commerce, online gaming and social media platforms, with 48 hours' notice before erasure, and requires processing logs to be kept for at least one year.
  • A published contact for questions about processing: a Data Protection Officer where applicable, or another person who can answer (Rule 9), and a grievance system that responds within 90 days (Rule 14).
  • Children: verifiable consent of a parent before processing the data of anyone under 18, and no tracking, behavioral monitoring or targeted advertising directed at children (Section 9, Rule 10), subject to exemptions in the Rules.

Rights of Data Principals

Individuals can obtain a summary of the personal data processed about them and the processing activities, and the identities of other Data Fiduciaries and Processors it was shared with (Section 11); ask for correction, completion, updating and erasure (Section 12); use a grievance redressal mechanism before complaining to the Board (Section 13); and nominate someone to act for them in case of death or incapacity (Section 14). Individuals also have duties, such as not filing false or frivolous complaints (Section 15).

Significant Data Fiduciary duties

The central government can notify a Data Fiduciary, or a class of them, as a Significant Data Fiduciary (SDF) based on factors including the volume and sensitivity of data, risk to Data Principals and to the State (Section 10). An SDF must:

  • appoint a Data Protection Officer based in India and responsible to its board;
  • appoint an independent data auditor;
  • carry out a Data Protection Impact Assessment and an audit once every twelve months, and send the Board a report of significant observations (Rule 13(1) and (2));
  • verify that its technical measures, including algorithmic software, are not likely to pose a risk to Data Principals' rights (Rule 13(3));
  • keep personal data that the government specifies, and the traffic data about its flow, inside India (Rule 13(4)).

Cross-border transfers

The DPDP Act takes a restrict-by-exception approach. Transfers abroad are allowed unless the central government restricts a country or territory by notification (Section 16(1)). Rule 15 adds that transfers must meet any requirements the government sets about making data available to a foreign State or its agencies. Stricter sector rules, such as those from financial regulators, continue to apply (Section 16(2)), and SDFs may face localization for specified data under Rule 13(4).

Penalties under the DPDP Act

The Data Protection Board can impose financial penalties set out in the Schedule to the Act (Section 33), taking into account the nature, gravity and duration of the breach and the mitigation taken.

BreachMaximum penalty
Failing to take reasonable security safeguards to prevent a personal data breach (Section 8(5))Up to ₹250 crore
Failing to notify the Board or affected Data Principals of a breach (Section 8(6))Up to ₹200 crore
Breaching the additional obligations for children's data (Section 9)Up to ₹200 crore
Breaching the additional obligations of a Significant Data Fiduciary (Section 10)Up to ₹150 crore
Any other breach of the Act or the Rules by a Data FiduciaryUp to ₹50 crore
Breach of a Data Principal's own duties (Section 15)Up to ₹10,000

Source: the Schedule to the DPDP Act, 2023; also summarized in the PIB backgrounder.

DPDP vs GDPR: how India's data protection law compares

Teams with a GDPR program have a head start, but the two laws are not interchangeable. The main differences:

TopicDPDP Act, 2023 and Rules, 2025GDPR
ScopeDigital personal data, including paper records that are later digitized. Personal data a person makes public themselves is excluded.Personal data processed by automated means or held in a filing system, including paper. Publicly available data is still covered.
Legal basisConsent, or one of the 'certain legitimate uses' listed in Section 7. No general 'legitimate interests' or 'contract' basis.Six lawful bases, including contract, legal obligation and legitimate interests.
Sensitive dataNo separate category of sensitive personal data in the Act.Special categories (such as health, biometric and religious data) with stricter conditions.
ChildrenUnder 18. Verifiable parental consent; no tracking, behavioral monitoring or targeted advertising directed at children.Member States set the age of digital consent between 13 and 16 for information society services.
Breach notificationEvery personal data breach: to each affected person without delay and to the Board, with a detailed report within 72 hours.To the supervisory authority within 72 hours unless the breach is unlikely to result in a risk; to individuals when the risk is high.
Cross-border transfersAllowed unless the government restricts a country by notification; stricter sector rules still apply.Allowed with an adequacy decision or appropriate safeguards such as standard contractual clauses.
Data Protection OfficerRequired for Significant Data Fiduciaries, based in India. Others publish a contact person.Required for public authorities and for certain large-scale monitoring or special-category processing.
Individual rightsInformation, correction, completion, updating, erasure, grievance redressal and nomination.Also includes portability, objection and rights about solely automated decisions.
Maximum penaltyUp to ₹250 crore (for failing to take reasonable security safeguards).Up to €20 million or 4% of worldwide annual turnover, whichever is higher.
RegulatorData Protection Board of India, a digital office; appeals go to TDSAT.Independent supervisory authorities in each Member State.

Personal data in documents: practical steps

Databases are comparatively easy to inventory. Documents are not: KYC copies, salary slips, bank statements, claim forms, lab reports and scanned applications sit in shared drives, email, loan-origination and claims systems, and increasingly in OCR and LLM pipelines. Personal data appears in free text, tables, stamps, handwriting and Indian-language scripts. Before May 2027, document-heavy teams in banking, insurance and healthcare can work through these steps:

  1. Inventory document types. For each document you collect, list the personal data fields it carries, the purpose in your notice, and every system and processor it flows to, including AI and OCR vendors.
  2. Minimize at intake. Keep only the fields the specified purpose needs. Consent under Section 6(1) is limited to necessary data, so a full copy kept "just in case" is hard to justify.
  3. Mask or redact before sharing. When a document goes to a vendor, a support team, a test environment or an LLM, send only what the task needs. Remove the rest from both the text layer and the page image, ideally inside your own environment. Rule 6 names masking and obfuscation as example safeguards.
  4. Use synthetic documents where real ones are not needed. Development, QA and model evaluation rarely need a real person's records. Fictional documents with known values avoid processing personal data for those purposes at all.
  5. Plan retention and erasure. Map how long each document type is kept, who must erase it once the purpose ends (including processors), and how you will keep the one-year processing logs Rule 8 requires without keeping the documents themselves longer than needed.
  6. Be breach-ready. A 72-hour report to the Board needs you to know which documents held which personal data, and where copies went.
  7. Keep evidence. Record what was detected and removed in each document, under which policy and who approved it.

Two limits apply. Redaction is one safeguard, not compliance: it does not replace notice, consent, retention decisions or rights handling. And redaction is not authorization: if a person or system is not entitled to a record, the right answer is to block access, not to send a redacted copy.

Where GritWorks fits

GritRedact detects personal data and custom entities in PDFs, scans, images and audio, applies your policy with human review, permanently redacts approved values and keeps an audit trail. Offline, you install Docker in your environment and it runs with no network egress, so source documents stay inside your boundary. GritRender generates fictional documents with known values for testing. To check how a redaction or extraction workflow copes with Indian documents, the free Indian-languages sample pack has fictional Hindi, Marathi and Bengali documents, readable and degraded. For background, see our DPDP Phase 2 Is Live: A Six-Month Checklist for Document-Heavy Teams and the document redaction evaluation checklist.

DPDP Act: common questions

What is the DPDP Act?

The Digital Personal Data Protection Act, 2023 is India's law on digital personal data. Organizations (Data Fiduciaries) may process personal data only with consent or for specified legitimate uses, must protect it with reasonable security safeguards and report breaches, and must honor individuals' rights. The DPDP Rules, 2025 set out how it works in practice.

When do the DPDP Rules come into force?

In three phases from the Gazette notification of 13 November 2025: the Data Protection Board provisions immediately, the consent manager provisions on 13 November 2026, and most obligations for Data Fiduciaries, including notices, security safeguards, breach intimation and rights, on 13 May 2027.

What is the maximum penalty under the DPDP Act?

Up to ₹250 crore for failing to take reasonable security safeguards to prevent a personal data breach. Failing to notify a breach and breaching the obligations for children's data can each attract up to ₹200 crore, Significant Data Fiduciary breaches up to ₹150 crore, and other breaches up to ₹50 crore.

Does the DPDP Act apply to companies outside India?

Yes, when the processing is connected with offering goods or services to people in India. Processing of digital personal data within India is covered regardless of where the company is based.

Does the DPDP Act cover scanned documents and PDFs?

Yes. The Act covers personal data collected in digital form and personal data collected on paper and digitized later, so scanned forms, PDFs and images of identity documents held in digital systems are in scope.

Is redaction enough to comply with the DPDP Act?

No. Rule 6 lists masking and obfuscation among example security safeguards, but redaction does not replace notice, consent, purpose limitation, retention and erasure, rights handling or access control. Redaction is not authorization: if someone is not entitled to a record, block access instead.

How is the DPDP Act different from GDPR?

The DPDP Act covers only digital personal data, relies on consent or a short list of legitimate uses rather than six lawful bases, has no separate category of sensitive data, treats everyone under 18 as a child, requires notice of every breach, and permits transfers abroad unless the government restricts a country.

Sources

Section and rule numbers refer to the Act as published on 11 August 2023 and the Rules as published on 13 November 2025. The PIB backgrounder gives 14 November 2025 as the notification date; the Gazette notification itself is dated 13 November 2025, and the commencement dates above are counted from it.

Start with your workflow

Put your unstructured data to work.

Tell us what your team needs to achieve. We’ll help you choose the right products, work through your requirements and explore on-premises or SaaS deployment.

Request a working session