DPDP Act 2023Updated 22 November 202610 min read

DPDP Penalties Explained: What a Data Breach Costs

The 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.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Maximum penalty
Up to ₹250 crore per instance (security safeguards)
Breach notification failure
Up to ₹200 crore
Children's data obligations
Up to ₹200 crore
Significant Data Fiduciary obligations
Up to ₹150 crore
Residual breaches
Up to ₹50 crore
Data Principal duties
Up to ₹10,000
Penalty provisions apply from
13 May 2027
Appeal
To TDSAT within 60 days (s.29)

Quick answer

Under the DPDP Act's Schedule, a Data Fiduciary can be fined up to ₹250 crore per instance for failing to take reasonable security safeguards, and up to ₹200 crore for failing to notify a breach. Children's data breaches carry up to ₹200 crore, SDF failures up to ₹150 crore, and any other breach up to ₹50 crore. The Board imposes penalties after an inquiry, and they apply from 13 May 2027.

  • The highest DPDP penalty is up to ₹250 crore per instance, for failing to take reasonable security safeguards under section 8(5).
  • A badly handled breach can engage both the security and the notification entries, which are separate heads of up to ₹250 crore and ₹200 crore.
  • Amounts are maximums; the Board fixes the actual figure using the section 33(2) factors, including mitigation and proportionality.
  • Penalties go to the Consolidated Fund of India, not to affected individuals.
  • The penalty provisions take effect on 13 May 2027, along with the core fiduciary obligations.

Who this is for: Founders and boards assessing data protection risk, CISOs and security leaders, Compliance and legal teams, Insurers and risk managers underwriting cyber cover, Significant Data Fiduciaries, once notified

What is the full DPDP penalty schedule?

The Schedule to the Digital Personal Data Protection Act, 2023 sets out a maximum penalty for each type of breach. Each figure is the amount a penalty may extend to, not a fixed fine.

#BreachProvisionMaximum penalty
1Failure to take reasonable security safeguards to prevent a personal data breachs.8(5)₹250 crore
2Failure to give the Board or affected Data Principals intimation of a personal data breachs.8(6)₹200 crore
3Non-fulfilment of additional obligations for childrens.9₹200 crore
4Non-fulfilment of additional obligations of a Significant Data Fiduciarys.10₹150 crore
5Breach of duties of a Data Principals.15₹10,000
6Breach of a voluntary undertaking accepted by the Boards.32Up to the amount applicable to the breach the proceedings concerned
7Breach of any other provision of the Act or RulesResidual₹50 crore

Three features matter in practice:

  • Per instance. The Board assesses each breach it finds. One incident can engage more than one row.
  • No turnover link. Unlike GDPR, the caps do not scale with revenue. A ₹250 crore cap is the same for a startup and a conglomerate.
  • Rules count too. Breaching a rule, such as Rule 3 notice content or Rule 14 grievance timelines, falls under row 7 unless a more specific row applies. Rule 6 security failures fall under row 1, and Rule 7 notification failures under row 2.

How does the Board decide the amount? The section 33(2) factors

Under section 33(1), the Board may impose a penalty if, after an inquiry and a hearing, it concludes that a breach is significant. Section 33(2) then lists the factors it must consider in fixing the amount:

  1. Nature, gravity and duration of the breach.
  2. Type and nature of the personal data affected.
  3. Repetitive nature of the breach.
  4. Whether the person, as a result of the breach, has realised a gain or avoided a loss.
  5. Whether the person took action to mitigate the effects and consequences, and how timely and effective that action was.
  6. Whether the penalty is proportionate and effective, given the need to secure compliance and deter breaches.
  7. The likely impact of the penalty on the person.

What this means for engineering teams

Most of these factors can be evidenced or improved before an incident:

  • Duration is a function of detection. Rule 6(1)(c) logs and monitoring shorten the window.
  • Type of data rewards minimisation and masking. Exposed tokens count for less than exposed identity documents.
  • Repetition means a second breach from the same root cause is treated worse. Close findings and keep evidence that you did.
  • Mitigation is assessed on timeliness. Timestamps in your incident tracker and the Rule 7 report are your record.
  • Gain or loss avoided covers cases like skipping security spend or monetising data without consent.

Keep a dated evidence pack: policies, controls, test results and incident timelines. It is the most direct way to influence these factors.

What a single data breach can cost under DPDP

A personal data breach can expose a fiduciary under several Schedule rows at once. The Board treats each as a separate instance.

Scenario mapping (illustrative, not a prediction)

What went wrongLikely Schedule rowCap
Unencrypted database, weak access control or no loggingRow 1: s.8(5), Rule 6₹250 crore
Users or Board not told, told late, or told without the Rule 7 contentRow 2: s.8(6), Rule 7₹200 crore
The breached system profiled children or lacked parental consentRow 3: s.9₹200 crore
An SDF skipped its annual DPIA or auditRow 4: s.10, Rule 13₹150 crore
Data kept beyond its purpose, or not erased on withdrawalRow 7: s.8(7)₹50 crore

The table shows exposure ceilings, not expected outcomes. No penalties have been imposed under the Act, and the provisions only commence on 13 May 2027. Avoid quoting combined totals as a forecast. The Board must apply the section 33(2) proportionality test to each.

Costs outside the Schedule

  • Incident response: forensics, notification logistics and customer support.
  • Parallel reporting: CERT-In requires reporting of specified cyber incidents within 6 hours, and sector regulators such as RBI or SEBI may have their own rules. Check the latest circular.
  • Blocking risk: under section 37, after penalties in two or more instances, the Board may advise the Government to block public access to a fiduciary's platform.
  • Contract and reputation: enterprise customers commonly carry breach indemnities in their data processing agreements.

How penalties are imposed: from complaint to order

Penalties are imposed by the Data Protection Board of India through a structured process.

  1. Trigger. A breach intimation from the fiduciary, a complaint by a Data Principal, a government reference, or a court direction.
  2. Preliminary view. The Board decides whether there are sufficient grounds to inquire.
  3. Inquiry (section 28). The Board inquires while following principles of natural justice. Rule 19(9) requires it to finish within six months of receiving the intimation, complaint, reference or direction. It may extend this by up to three months at a time, for reasons recorded in writing.
  4. Hearing. The fiduciary is given an opportunity to be heard. The Board works as a digital office (Rule 20), so hearings can be remote.
  5. Order. If the breach is significant, the Board imposes a penalty using the section 33(2) factors.
  6. Appeal. Any aggrieved person may appeal to TDSAT within 60 days (section 29). Under Rule 22 the appeal is filed in digital form and the fee is paid digitally.

The Board inquiry process and the TDSAT appeal guide cover these steps in detail.

Voluntary undertakings

Under section 32, the Board may accept a voluntary undertaking from a fiduciary at any stage of proceedings. This can be a commitment to take specified action, stop a practice or publish information. Acceptance bars further proceedings on the contents of the undertaking. Breaching the undertaking is penalised under row 6 of the Schedule.

Penalties on individuals: the ₹10,000 Data Principal duty

The Act also places duties on individuals. Section 15 requires a Data Principal to:

  • comply with applicable law when exercising rights;
  • not impersonate another person when providing personal data;
  • not suppress material information when providing data for any document, unique identifier, proof of identity or proof of address issued by the State;
  • not register a false or frivolous grievance or complaint with a Data Fiduciary or the Board;
  • furnish only verifiably authentic information when exercising the right to correction or erasure.

Breach can lead to a penalty of up to ₹10,000. See duties of Data Principals.

Why fiduciaries should care

This duty does not reduce a fiduciary's own obligations. It is not a defence to a breach of security safeguards. It does, however, give fiduciaries a legitimate basis to:

  • verify identity before acting on rights requests, using the identifiers published under Rule 14(1)(b);
  • reject or flag requests that look like impersonation or abuse;
  • record evidence when frivolous complaints are made, in case the matter reaches the Board.

Do not use this provision to discourage genuine requests. Making rights hard to exercise can itself breach the Act.

How to reduce DPDP penalty exposure before 13 May 2027

Penalty exposure is concentrated in three rows: security, breach notification and children. Prioritise them in that order.

Security (row 1, up to ₹250 crore)

  • Implement every Rule 6 minimum: encryption, masking or tokenisation; access control; logs, monitoring and review; backups; one-year log retention; processor contract clauses; and organisational measures. See reasonable security safeguards.
  • Keep test evidence such as pen tests, access reviews and restore drills. "Reasonable" will be judged on what you can show.

Breach notification (row 2, up to ₹200 crore)

  • Build Rule 7 templates for both individual and Board notices.
  • Define "becoming aware" internally, and record the timestamp when it happens.
  • Rehearse the 72-hour detailed report alongside the CERT-In 6-hour report.

Children (row 3, up to ₹200 crore)

  • Age-gate for under-18s and implement Rule 10 verifiable parental consent.
  • Switch off behavioural monitoring and targeted advertising directed at children, unless a Fourth Schedule exemption applies.

Everything else (row 7, up to ₹50 crore)

  • Rule 3 notices, consent withdrawal, Rule 8 retention, Rule 9 contact publication and Rule 14 rights operations are each separately penalisable.

Finally, assign an owner to each Schedule row and review readiness quarterly until commencement.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Map controls to Schedule rows

    Create a register linking each Schedule entry to the controls, owners and evidence that address it.

    DPDP Act Schedule

  2. Close Rule 6 security gaps first

    Encryption, access control, logging, backups and processor clauses sit under the ₹250 crore row and are the highest priority.

    Rule 6(1)

  3. Template Rule 7 breach notices

    Prepare individual and Board notice templates with all required fields, and a 72-hour detailed report outline.

    Rule 7(1), 7(2)

  4. Record awareness and mitigation timestamps

    Mitigation timeliness is a section 33(2) factor, so log when the breach was detected, contained and notified.

    s.33(2)(e)

  5. Audit children's data flows

    Confirm verifiable parental consent and the absence of tracking or targeted ads for users under 18.

    s.9; Rule 10

  6. Prepare a Board response playbook

    Name who handles notices, hearings and voluntary undertaking discussions, and who briefs counsel.

    s.28, s.32

  7. Track the TDSAT appeal window

    Diarise the 60-day appeal period from receipt of any Board order.

    s.29; Rule 22

Key dates

  1. Board provisions (ss.18–26) and Rules 17–21 in force

  2. Penalty provisions, the Schedule and core obligations apply

Answers

Frequently asked questions

What is the maximum penalty under the DPDP Act?

The highest entry in the Schedule is up to ₹250 crore per instance, for failing to take reasonable security safeguards to prevent a personal data breach under section 8(5). Separate entries cover breach notification and children's obligations, at up to ₹200 crore each.

Is the ₹250 crore DPDP penalty per breach or per year?

The Schedule sets a maximum per instance of breach that the Board finds after an inquiry. There is no annual aggregate cap. One incident can engage several entries, such as security failure and late notification, each assessed separately and subject to the section 33(2) proportionality factors.

When do DPDP penalties start applying?

The penalty provisions and the Schedule are among the sections commencing on 13 May 2027, together with Rules 3, 5 to 16, 22 and 23. The Board's constitution provisions have been in force since 13 November 2025, but it cannot impose DPDP penalties for conduct before the obligations commence.

Do affected individuals get compensation from DPDP penalties?

No. Penalties imposed by the Board are credited to the Consolidated Fund of India. The DPDP Act's penalty mechanism is not a compensation scheme for affected Data Principals. Individuals should take legal advice on any other remedies that may be available.

What factors does the Data Protection Board consider when setting a penalty?

Section 33(2) lists seven factors: the nature, gravity and duration of the breach; the type of personal data affected; repetition; any gain made or loss avoided; the timeliness and effectiveness of mitigation; whether the penalty is proportionate and effective; and its likely impact on the person.

Can a company avoid a DPDP penalty by offering a voluntary undertaking?

Section 32 lets the Board accept a voluntary undertaking at any stage of proceedings, for example to take specified action or stop a practice. Acceptance bars further proceedings on its contents. Breaching the undertaking can attract a penalty up to the amount applicable to the original breach. Involve counsel before offering one.

Can a DPDP penalty be appealed?

Yes. Any person aggrieved by a Board order may appeal to the Telecom Disputes Settlement and Appellate Tribunal within 60 days under section 29. Rule 22 requires the appeal to be filed digitally, with a fee equal to that for TRAI Act appeals, unless reduced or waived.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Section 33 and the Schedule (official text)
  • Digital Personal Data Protection Act, 2023 — Sections 28, 29, 32 and 37 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rules 6, 7, 19(9) and 22 (official text)

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

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.