Skip to content

ISO 27001, SOC 2, the DPDP Act and manual VAPT. Book a Free Scoping Call

DPDP Act17 min read

DPDP Act Penalties: What Each Breach Can Cost

DPDP Act penalties under the Schedule: seven tiers from ₹10,000 to ₹250 crore, how the Board sets the amount, and the control that keeps each tier away.

17 min readBy , Director

Reviewed by Pragya Dwivedi, Associate Director, CISM (ISACA), eWPTX (INE Security)

DPDP Act penalties are set out in the Schedule to the Digital Personal Data Protection Act, 2023, in seven tiers. The highest, up to ₹250 crore, applies to a failure to take reasonable security safeguards against a personal data breach. The lowest, up to ₹10,000, applies to individuals who breach their own duties. Every figure is a ceiling. The Data Protection Board decides the actual amount after an inquiry, weighing factors the Act lists in section 33.

At a Glance

  • Where the numbers live: the Schedule to the Digital Personal Data Protection Act, 2023, which section 33(1) points to.
  • Seven tiers: ₹250 crore, ₹200 crore, ₹200 crore, ₹150 crore, ₹10,000, a tier tied to a broken voluntary undertaking, and ₹50 crore for everything else.
  • Maximums, not tariffs: each entry says the penalty "may extend to" the figure. The Board sets the amount case by case.
  • Only after an inquiry: the Board must find the breach significant and give the person a hearing before imposing anything.
  • Seven factors: section 33(2) lists what the Board must weigh, including gravity, duration, the data affected and how quickly you mitigated.
  • Where the money goes: under section 34, penalties are credited to the Consolidated Fund of India, not paid to the people affected.
  • The ceiling can move: under section 42, the Central Government may amend the Schedule, but not to more than twice the figures originally enacted.

How a Penalty Is Imposed

The penalty clause is short, and its conditions matter as much as its numbers. Under section 33(1) of the Act, if the Board determines on conclusion of an inquiry that a breach of the Act or the Rules by a person is significant, it may, after giving that person an opportunity of being heard, impose a monetary penalty specified in the Schedule.

Flow of the steps before a DPDP Act penalty: an inquiry under section 28, a finding that the breach is significant, a hearing, weighing the section 33(2) factors, then a penalty up to the Schedule maximum.

Three things follow from that wording. First, there is an inquiry before there is a penalty; the Board's procedure is in section 28. Second, the breach has to be significant in the Board's judgment, so a minor lapse is not automatically a crore-level event. Third, the word "may" means the Board has discretion over whether to impose a penalty at all, and the Schedule's "may extend to" means it has discretion over the amount.

The seven factors in section 33(2)

When the Board fixes the amount, the Act tells it what to consider:

  1. the nature, gravity and duration of the breach;
  2. the type and nature of the personal data affected;
  3. whether the breach is repetitive;
  4. whether the person realised a gain or avoided a loss as a result;
  5. whether the person took action to mitigate the effects, and how timely and effective that action was;
  6. whether the penalty is proportionate and effective, given the need to secure observance of the Act and deter breaches; and
  7. the likely impact of the penalty on the person.

Read as a compliance brief, factors 1, 3 and 5 are the ones an organisation can influence before anything goes wrong. A short-lived breach that was detected quickly, contained and reported in time sits very differently against these factors from one that ran for months unnoticed. That is why logging, monitoring and a rehearsed incident response are penalty controls as much as security controls.

The Schedule, Tier by Tier

The table below sets out every entry in the Schedule as enacted, the provision each one refers to, and who it lands on.

Bar chart of the DPDP Act Schedule maximums in rupees crore: security safeguards 250, breach intimation 200, children's data 200, Significant Data Fiduciary duties 150, any other breach 50.

Sl. No. Breach Provision Maximum penalty Who it applies to
1 Failing to take reasonable security safeguards to prevent a personal data breach Section 8(5) ₹250 crore Data Fiduciary
2 Failing to notify the Board or affected Data Principals of a personal data breach Section 8(6) ₹200 crore Data Fiduciary
3 Breaching the additional obligations for children's data Section 9 ₹200 crore Data Fiduciary
4 Breaching the additional obligations of a Significant Data Fiduciary Section 10 ₹150 crore Significant Data Fiduciary
5 Breaching the duties of a Data Principal Section 15 ₹10,000 Data Principal
6 Breaching a term of a voluntary undertaking accepted by the Board Section 32 Up to the extent applicable to the original breach Whoever gave the undertaking
7 Breaching any other provision of the Act or the Rules Residual ₹50 crore Anyone with a duty under the Act

Tier 1: security safeguards, up to ₹250 crore

Section 8(5) requires a Data Fiduciary to protect personal data in its possession or under its control, including processing done on its behalf by a Data Processor, by taking reasonable security safeguards to prevent a personal data breach. This is the highest tier in the Schedule.

Two words in that section deserve attention. "Reasonable" means the Act does not demand perfection; it demands safeguards a Board could accept as proportionate to the data and the risk. And "on its behalf by a Data Processor" means a breach at your vendor is still your exposure. Rule 6 of the DPDP Rules, 2025 describes the minimum measures, including encryption or similar measures, access control, logging and monitoring, and backups, and it comes into force eighteen months after the Rules were published on 13 November 2025.

The control that keeps it away: a security programme you can evidence. That means encryption and access control on every store of personal data, logs that would reveal unauthorised access, tested backups, processor contracts with security terms, and periodic testing that finds weaknesses before an attacker does. Our web application VAPT and cloud security testing are where the testing half of that usually starts.

Tier 2: breach intimation, up to ₹200 crore

Section 8(6) requires a Data Fiduciary, in the event of a personal data breach, to give the Board and each affected Data Principal intimation of the breach in the form and manner prescribed. Rule 7 prescribes it: a description to the Board without delay, then a detailed report within seventy-two hours of becoming aware of the breach, or a longer period the Board allows on a written request, plus a notice to each affected person describing the breach, its likely consequences and what they can do.

This tier is separate from Tier 1, and that matters. A company can take reasonable safeguards, still suffer a breach, and then face exposure under this tier purely for reporting late or not at all. Failing at both is two entries in the Schedule, not one.

The control that keeps it away: an incident response plan that names the Board and affected individuals as recipients, a decision owner who can say "this is a personal data breach" quickly, and pre-drafted notices. Our guide to DPDP Act breach notification covers who must be told and when, and incident response readiness is how we rehearse it.

Tier 3: children's data, up to ₹200 crore

Section 9 requires a Data Fiduciary to obtain verifiable consent of the parent or lawful guardian before processing the personal data of a child, or of a person with a disability who has a lawful guardian. It also bars processing likely to have a detrimental effect on a child's well-being, and tracking, behavioural monitoring or targeted advertising directed at children, subject to exemptions the Rules prescribe. Rule 10 sets out how verifiable consent is to be obtained.

The control that keeps it away: know whether children use your service at all. If they do, build an age gate and a parental consent flow that meets Rule 10, and switch off tracking and targeted advertising for those users. If they should not be using it, document why and how you would detect it.

Tier 4: Significant Data Fiduciary duties, up to ₹150 crore

Section 10 lets the Central Government notify a Data Fiduciary or class of Data Fiduciaries as significant, based on factors such as the volume and sensitivity of the data, risk to Data Principals and wider public-interest grounds. A Significant Data Fiduciary must appoint a Data Protection Officer based in India, appoint an independent data auditor, and carry out periodic Data Protection Impact Assessments and audits. Rule 13 adds detail, including an annual impact assessment and audit.

The control that keeps it away: if you could plausibly be notified, plan for these roles before the notification rather than after. Our vDPO service provides a named data protection officer function for organisations that need one. Whether you need to appoint a DPO as an individual on your own staff is a question for your counsel and the notification itself.

Tier 5: duties of Data Principals, up to ₹10,000

Section 15 places duties on individuals: comply with applicable laws when exercising rights, do not impersonate anyone, do not suppress material information when providing data for identity documents, do not file false or frivolous grievances, and furnish only verifiably authentic information when asking for correction or erasure. The ceiling here is ₹10,000, the only figure in the Schedule measured in thousands rather than crores.

Tier 6: a broken voluntary undertaking

Section 32 lets the Board accept a voluntary undertaking from any person at any stage of an inquiry under section 28. The undertaking can include taking or refraining from an action within a time the Board sets, and publicising the undertaking. Acceptance bars further proceedings on the matters it covers.

The catch is in section 32(5): if the person fails to keep any term, the failure is deemed a breach of the Act, and the Board may proceed under section 33. The Schedule caps the penalty at the extent applicable to the breach for which the inquiry was originally started. In other words, an undertaking you do not honour puts the original penalty back on the table.

The control that keeps it away: only commit to terms you can deliver on the timeline, assign each term an owner, and keep evidence that it was done.

Tier 7: everything else, up to ₹50 crore

Any breach of the Act or the Rules that the first six entries do not cover falls here. That includes the duties a typical security programme does not reach: giving a proper notice, holding valid consent, erasing data when the purpose is served, honouring the rights of Data Principals, publishing a grievance contact and responding within the prescribed period, and engaging processors under a valid contract.

This is the tier most often underestimated, because it has no single subject.

The control that keeps it away: a privacy operations layer alongside your security controls: itemised notices, consent records with easy withdrawal, retention schedules tied to purpose, a rights request workflow with an owner, and a grievance channel. A DPDP gap analysis is the usual way to find which of these are missing.

Ceilings Can Stack, and Can Change

Each entry is a separate ceiling for a separate duty. One incident can engage more than one: inadequate safeguards that led to a breach (Tier 1) followed by late reporting (Tier 2) are two failures under two provisions. How the Board will treat overlapping breaches arising from the same facts is not spelled out in the Schedule, and until the Board publishes decisions, nobody can say how it will approach that in practice.

The figures themselves are not fixed forever. Section 42 lets the Central Government amend the Schedule by notification, subject to one restriction: no amendment may raise a penalty to more than twice what was specified when the Act was enacted. So the ₹250 crore entry could in principle rise to ₹500 crore, and no higher, without Parliament amending the Act.

There is also a consequence beyond money. Under section 37, where the Board has imposed monetary penalties on a Data Fiduciary in two or more instances and advises it in the public interest, the Central Government may, after a hearing, direct that public access to the information enabling that fiduciary's services in India be blocked.

Mapping Each Tier to a Control

A practical order of work:

Table mapping five DPDP Act penalty tiers to the duty behind each one and the control that addresses it, from security safeguards to privacy operations.

  1. Inventory personal data. You cannot take reasonable safeguards over data you have not found, or erase data you do not know you hold.
  2. Close the security gaps first. They carry the highest ceiling, and Rule 6 lists the minimum measures.
  3. Rehearse the breach procedure. Seventy-two hours is short when nobody has decided who calls it.
  4. Build the privacy operations layer. Notices, consent, rights requests, grievance handling, retention.
  5. Check whether section 9 or section 10 applies to you. Children's data and significant fiduciary status each bring their own tier.
  6. Keep evidence. Factor 5 in section 33(2) rewards timely, effective mitigation, and only records can show it.

When the Duties Apply

The penalty tiers attach to duties, and most of the detail behind those duties is in the Rules. Rule 1 of the DPDP Rules, 2025 brings rules 3 and 5 to 16 into force eighteen months after publication, which is 13 May 2027. That covers notice (rule 3), security safeguards (rule 6), breach intimation (rule 7), children's data (rule 10), Significant Data Fiduciary obligations (rule 13) and the rights of Data Principals (rule 14). Our DPDP Act compliance service sets out what to do before that date.

What SecureRoot Does, and Does Not Do

SecureRoot runs DPDP Act readiness in six phases. Startups and mid-size companies usually complete it in 13 to 23 weeks, at guide ranges from ₹1.5 lakh; large enterprises with complex data flows are quoted by phase, at a guide range of ₹15 lakh to ₹60 lakh. The work covers data mapping, gap assessment, notices and consent design, rights workflows, security safeguards and breach procedures, described on our DPDP Act compliance service page.

Three limits. There is no DPDP certificate in Indian law, so no firm, SecureRoot included, can certify that you comply with the Act. We are not a law firm, and how the Board will interpret a provision is a question for your counsel. And no programme can guarantee that a penalty will never be imposed; what it can do is put you on the right side of each duty and give you the evidence to show it.

Frequently Asked Questions

What is the maximum penalty under the DPDP Act?

The highest figure in the Schedule is ₹250 crore, for a Data Fiduciary's failure to take reasonable security safeguards to prevent a personal data breach under section 8(5). It is a ceiling, not a standard fine: the Schedule says the penalty may extend to that amount, and the Board decides the actual figure after an inquiry and a hearing. The next tiers are ₹200 crore for failing to notify the Board or affected individuals of a breach, ₹200 crore for breaching the obligations on children's data, ₹150 crore for breaching the additional obligations of a Significant Data Fiduciary, and ₹50 crore for any other breach of the Act or the Rules. Separate entries can apply to separate failures arising from one incident, so a poorly protected system that is breached and then reported late engages two tiers. The Central Government can raise the figures by notification, but never beyond twice the amounts originally enacted.

Will the Board always impose the maximum?

No. The figures are maximums, and section 33 builds in discretion at every step. The Board must first conclude an inquiry, then find that the breach is significant, then give the person an opportunity of being heard, and only then may it impose a penalty. When it sets the amount, section 33(2) requires it to weigh seven matters: the nature, gravity and duration of the breach; the type of personal data affected; whether the breach is repetitive; any gain made or loss avoided; the timeliness and effectiveness of mitigation; whether the penalty is proportionate and effective as a deterrent; and its likely impact on the person. Several of these are within an organisation's control before anything goes wrong. Fast detection shortens duration, a rehearsed response improves mitigation, and a clean record avoids the repetition factor. None of this guarantees a particular outcome, but it shapes the facts the Board will weigh.

Do DPDP penalties go to the people whose data was breached?

No. Section 34 of the Act says that all sums realised by way of penalties imposed by the Board are credited to the Consolidated Fund of India. The penalty is a payment to the State, not compensation to individuals, and the Act's penalty provisions do not set up a fund or a payout for affected Data Principals. This is a notable difference from how many people assume data protection fines work. It also means the penalty is not the whole cost of a breach. An organisation still bears the cost of investigating and containing the incident, notifying the Board and every affected person under rule 7, handling the complaints and rights requests that follow, and dealing with contractual claims from customers whose data it processed. Whether individuals have other legal remedies outside the Act is a question for counsel. For budgeting purposes, treat the Schedule as one line in the cost of a breach, not the total.

Can a Data Processor be penalised directly under the DPDP Act?

The heaviest tiers are written around the Data Fiduciary. Section 8(5) makes the fiduciary responsible for safeguards over personal data, expressly including processing done on its behalf by a Data Processor, and section 8(6) puts breach intimation on the fiduciary too. So when a processor is breached, the fiduciary that engaged it carries the Tier 1 and Tier 2 exposure. Tier 7, however, covers a breach of any other provision of the Act or the Rules by a person, which is broader than fiduciaries alone, and how far it reaches processors will depend on the duties the Act and Rules place on them and on how the Board reads them. In practice, a processor's exposure arrives mostly through its contracts. Fiduciaries will push security, breach reporting and deletion terms down to their vendors and ask for evidence, so a processor that cannot show those controls loses business long before any penalty question arises.

Has the Data Protection Board imposed any penalties yet?

We are not aware of any published penalty order from the Data Protection Board, and we do not cite any. The provisions setting up the Board came into force when the DPDP Rules were published on 13 November 2025, and most of the operational Rules, including those on security safeguards, breach intimation, children's data and Significant Data Fiduciary duties, come into force on 13 May 2027. Until the Board publishes decisions, there is no body of practice showing how it applies the section 33(2) factors, how it treats overlapping breaches, or where in each range its penalties tend to fall. Be cautious with any article that claims to calculate a likely DPDP fine for your company, because there is no enforcement record to calibrate it against. The sound planning assumption is the Schedule itself: know which tiers your processing engages, and put the controls behind each one in place before the duties apply.

Where to Start

Take the seven rows of the Schedule and write next to each one whether it applies to you and which control answers it. Where the answer is blank, that is your gap list. If you want it done against your own systems, request an assessment and we will map your processing to each tier.

Free Checklist

Get the DPDP Act Checklist

Our DPDP Act checklist: the controls, evidence and decisions the programme turns on, marked up for your scope. Tell us where to send it.

One form, the same notice as every enquiry on this site.

Have a Question About This?

If this raised something specific to your environment, a scoping call is the fastest way to get a direct answer.

We reply within one business day.

See Every Published Price Band
All Articles
  • DPDP Act17 min read

    DPDPA vs GDPR: Key Differences Explained

    A GDPR programme gives you a head start on India's DPDP Act, but not a finished one. Here is where the two laws line up, where they part ways, and what a company already running GDPR has to add for India.

    Read Article
  • DPDP Act15 min read

    Who Is a Significant Data Fiduciary? A Plain Answer

    A Significant Data Fiduciary is a company the central government names by notification, not one that qualifies by crossing a threshold. Here is how designation works, the six factors in Section 10, the extra duties in the Act and Rule 13, and what to do before any list appears.

    Read Article
  • DPDP Act14 min read

    DPDP Compliance Deadline 13 May 2027: What to Do Now

    Most Data Fiduciary duties under the DPDP Rules, 2025 come into force on 13 May 2027. Here is where the date comes from, what starts that day, and how to work backwards from it to the week your programme has to begin.

    Read Article