DPDP Act

The Digital Personal Data Protection Act, 2023

A plain-language guide to India's data protection law and the Rules made under it: who it applies to, what it asks for and when each part comes into force. Every statement carries its section or rule.

Checked against the official text on 16 November 2026.

Overview

What the law is

Not legal advice. This page is general information about the Digital Personal Data Protection Act, 2023 and the Rules made under it. It is not legal advice. Read the official text and take advice from a qualified lawyer on how the law applies to your organisation.

The Digital Personal Data Protection Act, 2023 (22 of 2023) sets the rules for processing digital personal data in India. It gives individuals, whom it calls Data Principals, rights over their data, and it places obligations on the organisations that decide how that data is used, which it calls Data Fiduciaries.

The detail is in the Digital Personal Data Protection Rules, 2025, notified on 13 November 2025 as G.S.R. 846(E). A corrigendum of 10 December 2025 corrects wording in the Rules as first published.

This page separates two things. What the Act and the Rules require is listed under The Act and the Rules. What we suggest an organisation does to meet those requirements is listed under Recommended practice, and is not a legal requirement.

Personal data
Section 2(t)
Any data about an individual who is identifiable by or in relation to such data.
Data Principal
Section 2(j)
The individual to whom the personal data relates. For a child, this includes the parents or lawful guardian; for a person with disability, the lawful guardian acting on her behalf.
Data Fiduciary
Section 2(i)
Any person who alone or in conjunction with other persons determines the purpose and means of processing of personal data.
Data Processor
Section 2(k)
Any person who processes personal data on behalf of a Data Fiduciary.
Consent Manager
Section 2(g)
A person registered with the Board who acts as a single point of contact to enable a Data Principal to give, manage, review and withdraw her consent through an accessible, transparent and interoperable platform.
Board
Sections 2(c) and 18
The Data Protection Board of India, established by the Central Government.

More terms are defined in the glossary.

Commencement

When it comes into force

The Act did not come into force on a single day. A notification of 13 November 2025, G.S.R. 843(E), appoints three dates for different provisions, and Rule 1 of the Rules follows the same three stages.

  1. Stage one

    On publication

    13 November 2025

    • Definitions
    • Establishment and composition of the Data Protection Board of India
    • The power to make rules, and related provisions
    • The Act's relationship with other laws
    Act
    Sections 1(2), 2, 18 to 26, 35, 38 to 43, and 44(1) and 44(3)
    Rules
    Rules 1, 2 and 17 to 21
  2. Stage two

    One year after publication

    13 November 2026, counted from publication

    • Registration of Consent Managers with the Board
    • The Board's power to inquire into a breach of a condition of that registration
    Act
    Sections 6(9) and 27(1)(d)
    Rules
    Rule 4
  3. Stage three

    Eighteen months after publication

    13 May 2027, counted from publication

    • Notice, consent and certain legitimate uses
    • The obligations of Data Fiduciaries, including security safeguards and breach intimation
    • Children's data and Significant Data Fiduciaries
    • The rights and duties of Data Principals
    • Transfers outside India, exemptions, inquiries, appeals and penalties
    Act
    Sections 3 to 5, 6(1) to 6(8) and 6(10), 7 to 17, 27 (except 27(1)(d)), 28 to 34, 36, 37 and 44(2)
    Rules
    Rules 3, 5 to 16, 22 and 23
Dates are counted, not quoted. The notification states periods (“one year” and “eighteen months” from publication), not calendar dates. The dates shown are counted from publication on 13 November 2025. Confirm them against the notification, and check the Ministry's page for any later notification, before relying on them. Read G.S.R. 843(E).

Roles

Data Fiduciary and Data Processor

The Act places its obligations on the Data Fiduciary. A Data Processor acts on the fiduciary's behalf and under its contract. The two do not carry the same duties.

Data Fiduciary

Section 2(i) Any person who alone or in conjunction with other persons determines the purpose and means of processing of personal data.

  • Answers for processing done by it or on its behalf by a Data Processor (Section 8(1)).
  • Gives notice and obtains consent, or relies on a certain legitimate use (Sections 4 to 7).
  • Takes reasonable security safeguards and intimates breaches (Sections 8(5) and 8(6)).
  • Responds to the rights and grievances of Data Principals (Sections 11 to 14).
ControlMap for Data Fiduciaries

Data Processor

Section 2(k) Any person who processes personal data on behalf of a Data Fiduciary.

  • Is engaged by a Data Fiduciary only under a valid contract (Section 8(2)).
  • Meets most of its duties through that contract; Chapter II is addressed to the fiduciary.
  • Has to be able to stop processing and erase data when the fiduciary is required to cause it (Sections 6(6) and 8(7)).
  • Is itself a Data Fiduciary for data it controls, such as its own employees' data.
ControlMap for Data Processors

Which role an organisation holds depends on the facts of each processing activity, and one organisation can hold both. If the answer is unclear, take legal advice.

Section 3

What the Act applies to

The Act governs the processing of digital personal data. It reaches processing inside India and, in one case, processing outside it.

The Act and the Rules

  • It applies to processing within India of personal data collected in digital form, or collected in non-digital form and digitised subsequently (Section 3(a)).
  • It applies to processing outside India if that processing is in connection with any activity related to offering goods or services to Data Principals within India (Section 3(b)).
  • It does not apply to personal data processed by an individual for a personal or domestic purpose (Section 3(c)(i)).
  • It does not apply to personal data made publicly available by the Data Principal herself, or by a person under a legal obligation to make it publicly available (Section 3(c)(ii)).

Recommended practice

  • Record which of your processing activities fall within the Act, and why any are treated as outside it.
  • Include data that begins on paper and is later typed or scanned into a system.

Related: Data Inventory

Section 7Rule 5

Certain legitimate uses

Section 7 lists the uses for which personal data may be processed without consent. The list is closed. The Act has no general ground based on the legitimate interests of the Data Fiduciary.

The Act and the Rules

  • The specified purpose for which the Data Principal has voluntarily provided her personal data, where she has not indicated that she does not consent to its use (Section 7(a)).
  • Provision by the State or its instrumentalities of a subsidy, benefit, service, certificate, licence or permit, on the conditions in Section 7(b) and following the standards in the Second Schedule (Rule 5).
  • Performance by the State of a function under law, or in the interest of the sovereignty and integrity of India or the security of the State (Section 7(c)).
  • Fulfilling an obligation under law to disclose information to the State, and compliance with a judgment, decree or order (Sections 7(d) and 7(e)).
  • Responding to a medical emergency involving a threat to life or an immediate threat to health; providing medical treatment or health services during an epidemic or other threat to public health; and measures for safety or assistance during a disaster or breakdown of public order (Sections 7(f), 7(g) and 7(h)).
  • Purposes of employment, or those related to safeguarding the employer from loss or liability (Section 7(i)).

Recommended practice

  • For each processing activity, record whether it rests on consent or on a named clause of Section 7, with the reasoning.
  • Review that record when the purpose of an activity changes.

Related: Records of Processing

Section 8Rules 6, 8 and 9

Obligations of a Data Fiduciary

Section 8 sets out the general obligations. They rest on the Data Fiduciary even where the processing is carried out by a Data Processor.

The Act and the Rules

  • The Data Fiduciary is responsible for complying with the Act and the Rules for any processing undertaken by it or on its behalf by a Data Processor, irrespective of any agreement to the contrary (Section 8(1)).
  • A Data Processor may be engaged only under a valid contract (Section 8(2)).
  • Where personal data is likely to be used to make a decision that affects the Data Principal, or disclosed to another Data Fiduciary, its completeness, accuracy and consistency are to be ensured (Section 8(3)).
  • Appropriate technical and organisational measures are to be implemented to ensure effective observance of the Act and the Rules (Section 8(4)).
  • Personal data is to be protected by reasonable security safeguards to prevent a personal data breach (Section 8(5)). Rule 6 lists the minimum: measures such as encryption, obfuscation, masking or virtual tokens; access control; logs, monitoring and review; measures for continued processing such as backups; retention of logs and personal data for one year for detection and investigation; contract provisions with processors; and technical and organisational measures to make the safeguards effective.
  • Personal data is erased when consent is withdrawn or as soon as it is reasonable to assume the specified purpose is no longer being served, unless retention is necessary for compliance with a law; processors are caused to erase it too (Section 8(7)).
  • For the classes of Data Fiduciary in the Third Schedule, the Rules fix the period after which the purpose is deemed no longer served, and require the Data Principal to be informed at least forty-eight hours before erasure (Rule 8(1) and 8(2)).
  • Personal data, associated traffic data and other logs of processing are retained for a minimum of one year from the date of processing, for the purposes in the Seventh Schedule (Rule 8(3)).
  • The business contact information of the Data Protection Officer, if applicable, or of a person who can answer questions about processing, is published prominently on the website or app and mentioned in every response to a rights communication (Section 8(9) and Rule 9).

Recommended practice

  • Name an owner and a reviewer for each obligation, with a review date.
  • Hold evidence against the obligation it supports, and rate how good that evidence is.
  • Keep a register of processors with the contract clause that covers security safeguards.

Related: How ControlMap maps Rule 6 · Processor Oversight

Sections 2(u) and 8(6)Rule 7

Personal data breach

A personal data breach is any unauthorised processing of personal data, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to it, that compromises its confidentiality, integrity or availability (Section 2(u)).

The Act and the Rules

  • In the event of a personal data breach, the Data Fiduciary gives the Board and each affected Data Principal intimation of the breach (Section 8(6)).
  • Each affected Data Principal is told without delay, in a concise, clear and plain manner, through her user account or a registered mode of communication: a description of the breach, the consequences likely to arise for her, the measures taken to mitigate risk, the safety measures she may take, and a contact who can respond to her queries (Rule 7(1)).
  • The Board is told without delay of the breach, including its nature, extent, timing, location and likely impact (Rule 7(2)(a)).
  • Within seventy-two hours of becoming aware of the breach, or a longer period the Board allows on a written request, the Board is given updated and detailed information: the facts and circumstances, mitigation measures, findings regarding the person who caused the breach, remedial measures to prevent recurrence, and a report on the intimations given to Data Principals (Rule 7(2)(b)).

Recommended practice

  • Decide in advance who declares a breach and who signs each intimation.
  • Keep templates for the intimations and the contact details needed to send them.
  • Agree with each processor how quickly it will tell you of an incident.
  • Keep a log of incidents with the time you became aware and the time each intimation was made.

Related: Breach Management · Guide: breach intimation

Section 9Rules 10, 11 and 12

Children's data

A child is an individual who has not completed the age of eighteen years (Section 2(f)). Section 9 adds duties for children's data and for the data of a person with disability who has a lawful guardian.

The Act and the Rules

  • Before processing the personal data of a child, the Data Fiduciary obtains the verifiable consent of the parent; for a person with disability who has a lawful guardian, that of the guardian (Section 9(1)).
  • The Data Fiduciary adopts technical and organisational measures to ensure verifiable consent is obtained, and observes due diligence to check that the person identifying as the parent is an identifiable adult, by reference to reliable identity and age details it holds or details voluntarily provided, including through a virtual token issued by an authorised entity (Rule 10).
  • Processing that is likely to cause any detrimental effect on the well-being of a child is not to be undertaken (Section 9(2)).
  • Tracking or behavioural monitoring of children, and targeted advertising directed at children, are not to be undertaken (Section 9(3)).
  • Sections 9(1) and 9(3) do not apply to the classes of Data Fiduciary in Part A of the Fourth Schedule, or for the purposes in Part B, subject to the conditions stated there (Section 9(4) and Rule 12). Part A covers clinical and mental health establishments, healthcare professionals, educational institutions, crèches and child day care, and transport engaged by them, each within stated limits.

Recommended practice

  • Identify which datasets and services involve children, and record how age is established.
  • Document the method used to verify the parent, and keep the record of each verification.
  • Where you rely on the Fourth Schedule, record which entry applies and how its conditions are met.

Related: ControlMap for education · Consent Management

Section 10Rule 13

Significant Data Fiduciary obligations

The Central Government may notify any Data Fiduciary or class of Data Fiduciaries as a Significant Data Fiduciary. An organisation does not become one by its own assessment.

The Act and the Rules

  • The factors the Central Government may assess include the volume and sensitivity of personal data processed, risk to the rights of Data Principals, potential impact on the sovereignty and integrity of India, risk to electoral democracy, security of the State and public order (Section 10(1)).
  • A Significant Data Fiduciary appoints a Data Protection Officer who is based in India, is responsible to its board of directors or similar governing body, and is the point of contact for grievance redressal (Section 10(2)(a)).
  • It appoints an independent data auditor to carry out data audit (Section 10(2)(b)).
  • It undertakes a Data Protection Impact Assessment and an audit once in every period of twelve months from the date it is notified, and causes the person carrying them out to furnish a report of significant observations to the Board (Rule 13(1) and 13(2)).
  • It observes due diligence to verify that technical measures it adopts, including algorithmic software, are not likely to pose a risk to the rights of Data Principals (Rule 13(3)).
  • It ensures that personal data specified by the Central Government on the recommendation of a committee, and the traffic data pertaining to its flow, is not transferred outside India (Rule 13(4)).

Recommended practice

  • Record whether you have been notified. If you have not, record the date you last checked.
  • Assess your readiness against these duties before any notification, so that the work is understood in advance.

Related: DPIA

Sections 11 to 15Rule 14

Rights of Data Principals

Chapter III gives Data Principals rights against the Data Fiduciary and sets out their duties. The rights to information, correction and erasure apply where the Data Principal has previously given consent, including under Section 7(a).

The Act and the Rules

  • The right to obtain a summary of the personal data being processed and the processing activities, the identities of all other Data Fiduciaries and Data Processors with whom it has been shared, and a description of what was shared (Section 11).
  • The right to correction, completion, updating and erasure of personal data. Erasure is to follow unless retention is necessary for the specified purpose or for compliance with a law (Section 12).
  • The right to readily available means of grievance redressal (Section 13).
  • The right to nominate another individual to exercise her rights in the event of death or incapacity (Section 14).
  • The Data Fiduciary publishes on its website or app the means by which a request may be made and the particulars, such as a username or other identifier, required to identify the Data Principal (Rule 14(1)).
  • Data Principals also have duties, including not to impersonate another person and not to register a false or frivolous grievance or complaint (Section 15).

Recommended practice

  • Keep one register of requests, with the type, the stage reached, the owner and the due date.
  • Record how identity was confirmed before data was disclosed or changed.
  • Use the inventory to find every system that holds the person's data.

Related: Data Principal Rights

Sections 8(10) and 13Rule 14(3)

Grievance redressal

A Data Principal has to use the Data Fiduciary's grievance mechanism before approaching the Board. The mechanism therefore has to exist and to work.

The Act and the Rules

  • A Data Fiduciary establishes an effective mechanism to redress the grievances of Data Principals (Section 8(10)).
  • The Data Fiduciary or Consent Manager responds to a grievance within the period prescribed (Section 13(2)).
  • Every Data Fiduciary and Consent Manager publishes on its website or app the period within which it responds to grievances under its grievance redressal system, which is to be reasonable and not to exceed ninety days, and implements technical and organisational measures to respond within it (Rule 14(3)).
  • The Data Principal exhausts this opportunity before approaching the Board (Section 13(3)).

Recommended practice

  • Publish one clear route for grievances and name who is responsible for it.
  • Track each grievance against the period you have published, and report overdue items to management.

Related: Data Principal Rights

Sections 16 and 17Rules 15 and 16

Transfers outside India, and exemptions

The Act does not prohibit transfers of personal data outside India by default. It allows the Central Government to restrict them, and it sets out a list of exemptions from parts of the Act.

The Act and the Rules

  • The Central Government may, by notification, restrict the transfer of personal data to a notified country or territory outside India (Section 16(1)).
  • Personal data may be transferred outside India subject to requirements the Central Government may specify for making it available to a foreign State or to persons or entities under its control (Rule 15).
  • Any other law that provides a higher degree of protection for, or restriction on, transfer continues to apply (Section 16(2)).
  • Chapter II (other than Sections 8(1) and 8(5)), Chapter III and Section 16 do not apply in the cases listed in Section 17(1), which include processing necessary to enforce a legal right or claim, and the prevention, detection, investigation or prosecution of an offence.
  • The Act does not apply to processing necessary for research, archiving or statistical purposes if the data is not used to take a decision specific to a Data Principal and the standards in the Second Schedule are followed (Section 17(2)(b) and Rule 16).
  • The Central Government may notify certain Data Fiduciaries or classes of them, including startups, to whom Section 5, Sections 8(3) and 8(7), and Sections 10 and 11 do not apply (Section 17(3)).

Recommended practice

  • Record the country of each system and each processor, and review flows that cross a border.
  • Check for notifications under Sections 16 and 17 as part of your review cycle. Do not assume an exemption applies.

Related: Data Flow Management

Enforcement

Enforcement and penalties

The Schedule to the Act sets the maximum monetary penalty for each kind of breach. The amounts are ceilings, not fixed sums.

BreachProvisionPenalty
Failure to take reasonable security safeguards to prevent a personal data breachSection 8(5)Up to ₹250 crore
Failure to give the Board or affected Data Principals notice of a personal data breachSection 8(6)Up to ₹200 crore
Breach of the additional obligations in relation to childrenSection 9Up to ₹200 crore
Breach of the additional obligations of a Significant Data FiduciarySection 10Up to ₹150 crore
Breach of the duties of a Data PrincipalSection 15Up to ₹10,000
Breach of a term of a voluntary undertaking accepted by the BoardSection 32Up to the amount applicable to the breach the proceedings concerned
Breach of any other provision of the Act or the RulesSchedule, item 7Up to ₹50 crore

How the amount is decided

In determining a penalty, the Board is to have regard to (Section 33(2)):

  • the nature, gravity and duration of the breach
  • the type and nature of the personal data affected
  • whether the breach is repetitive
  • whether the person realised a gain or avoided a loss
  • whether the person acted to mitigate the effects, and how promptly and effectively
  • whether the penalty is proportionate and effective
  • the likely impact of the penalty on the person

Who decides

The Data Protection Board of India inquires into personal data breaches and complaints, and may impose the monetary penalties in the Schedule where it finds a breach to be significant, after giving the person an opportunity of being heard (Sections 27, 28 and 33).

An order or direction of the Board may be appealed to the Appellate Tribunal within sixty days (Section 29). The Appellate Tribunal is the Telecom Disputes Settlement and Appellate Tribunal (Section 2(a)).

The Board may accept a voluntary undertaking from a person at any stage of a proceeding (Section 32).

Official sources

Read the text itself

These are the documents this page was written from. Where this page and the official text differ, the official text is right.

How this page is maintained. It was last checked against these sources on 16 November 2026. Later notifications, amendments or directions of the Board may have changed the position. The Ministry's index page lists the notifications issued under the Act.

See how these provisions become assessed controls.

ControlMap organises the Act and the Rules into a catalogue of controls, each with its reference, an owner and its evidence.