Breach response

72-hour breach notification under the DPDP Rules

Published 15 November 2026 · 7 min read · Complisarthi Editorial Team

A personal data breach is a bad day for any business. Under the DPDP Rules, 2025 it is also a legal clock. Rule 7 sets out what you must tell affected people and the Data Protection Board, and when. This article explains the duties in plain language and shows how to prepare so that the first hours of an incident are calm rather than chaotic.

What counts as a breach

The Act treats a personal data breach as an event that compromises the confidentiality, integrity or availability of personal data, such as unauthorised access, disclosure, loss or destruction. A stolen laptop with customer files, an email sent to the wrong list, a ransomware attack that locks your records, a vendor leaking your data or an employee copying a database all qualify. There is no minimum size or risk threshold in the Rules: a breach triggers the notification duties whatever its seriousness.

Two audiences, two sets of duties

You have to notify the people affected and the Board. The timelines differ.

Telling affected people

On becoming aware of a breach, you must tell each affected person, to the best of your knowledge, in a concise, clear and plain way and without delay. You send the notice through their user account or a communication channel they registered with you. The notice must include:

  • A description of the breach, including its nature, extent and when it happened.
  • The consequences relevant to them that are likely to arise.
  • The measures you have taken and are taking to reduce the risk.
  • Safety steps they can take to protect themselves, such as changing passwords or watching for fraud.
  • Business contact details of someone who can answer their questions.

Telling the Board: two stages

First, without delay, you intimate the Board with a description of the breach, including its nature, extent, timing and location and the likely impact. This is an early warning and can be brief.

Second, within 72 hours of becoming aware of the breach, or a longer period if the Board allows it on your written request, you send updated and detailed information:

  • A fuller description of the breach.
  • The broad facts, events, circumstances and reasons that led to it.
  • Measures implemented or proposed to reduce risk.
  • Any findings about the person who caused it.
  • Remedial measures taken to prevent recurrence.
  • A report on the notices given to affected people.

When does the 72 hours start?

The clock runs from when you become aware of the breach, not from when it happened. That makes early detection valuable: a breach you spot on day one gives you the full window, while one you ignore for a month does not stop the clock from being relevant to how a regulator sees your diligence. Log the time you became aware and the evidence for it.

Penalties for getting it wrong

Failing to notify the Board or affected people can attract a penalty of up to ₹200 crore, and failing to take reasonable security safeguards in the first place can attract up to ₹250 crore. The Board considers mitigation: whether you acted quickly and effectively to reduce harm counts in your favour.

Other timelines you may face

The DPDP Rules are not the only source of breach duties. CERT-In directions require certain cyber incidents to be reported within six hours, and sector regulators such as the RBI, SEBI or IRDAI may have their own rules. Your plan should list every recipient and deadline in one place.

A response plan you can write this week

  1. Name an incident lead and a deputy, with phone numbers.
  2. Decide who can approve notices to customers and to the Board.
  3. Write the first-hour steps: contain the incident, preserve logs, record the time you became aware.
  4. Prepare templates for the customer notice and the Board notice with the fields above.
  5. List your vendors and who to call at each if the breach involves them.
  6. Record every action and decision in an incident log with timestamps.
  7. Rehearse once. A 30-minute tabletop exercise reveals gaps quickly.

Security safeguards come first

Notification is the second line of defence. Rule 6 expects encryption or masking, access controls, logging and monitoring, backups, retention of logs for a year and security terms in processor contracts. These help you detect breaches sooner and show the Board that you took reasonable steps.

How Complisarthi helps

The Breach Response module keeps a 72-hour countdown visible, drafts the Board notice and customer notices from the facts you enter, and keeps a tamper-evident incident log. It also monitors public breach sources for signs that your domains or credentials have appeared. This article is general information, not legal advice; in a serious incident, involve a lawyer.

Frequently asked questions

Do I have to report a very small breach?

The Rules contain no minimum size or risk threshold, so you should assume any personal data breach triggers the notification duties and take advice if you are unsure.

Can I get more than 72 hours?

The Rules allow a longer period for the detailed report if the Board permits it on a written request, so ask early if you need more time.

Who is responsible if my vendor is breached?

You remain responsible for processing done on your behalf by a Data Processor, so you should ask your vendors to tell you quickly about any incident and be ready to notify.

Is your business ready for a breach?

Take the free compliance audit: about 10 minutes, no credit card, with a score and a ranked list of gaps.

Check Your Compliance Score — Free

This page is general information, not legal advice. Complisarthi is software, not a law firm.