DPDP glossary

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 (DPDP Act 2023, section 2(u)).

Reviewed November 2026 by an advocate (LLB, LLM, 10+ years' practice) and a Chartered Accountant · Our review process

What counts as a breach?

Far more than hacking. Real examples from Indian companies include a spreadsheet of customer phone numbers emailed to the wrong vendor, a laptop with unencrypted HR files left in a cab, ransomware that locks a clinic's patient records for two days, an S3 bucket left public during a migration, and a support agent looking up a celebrity's account out of curiosity. Loss of availability counts too, which surprises many teams.

What must you do after a breach?

  1. Inform each affected Data Principal without delay, in plain language: what happened, when, the likely consequences, what you are doing about it, what they can do to protect themselves, and who to contact (Rule 7(1)).
  2. Inform the Board without delay with a description of the breach, its nature, extent, timing, location and likely impact.
  3. Within 72 hours of becoming aware, send the Board a detailed report: updated facts, circumstances and reasons, mitigation measures, any findings about the person responsible, remedial steps to prevent recurrence and a report on the notices given to affected people. The Board can allow more time on request.

How is this different from the GDPR and CERT-In?

Under the GDPR, you notify the regulator only if the breach is likely to risk people's rights. The DPDP Act has no such threshold: every personal data breach is reportable. Separately, CERT-In's 2022 directions require certain cyber incidents to be reported to CERT-In within six hours. One incident can trigger both, on different clocks, so your response plan needs both timelines.

What is the penalty for not reporting?

Up to ₹200 crore for failing to notify the Board or affected people, and up to ₹250 crore if the breach also reflects a failure to take reasonable security safeguards.

How to be ready

  • A written breach response plan with named owners and both the six-hour and 72-hour clocks
  • Template notices for people and for the Board
  • A breach register, including incidents you decided were not breaches, with reasons
  • At least one tabletop drill a year

DPDP compliance software in AuditIQ GRC includes a breach register and a 72-hour workflow.

Source: DPDP Act 2023, sections 2(u) and 8(6), Schedule; DPDP Rules 2025, Rule 7; CERT-In Directions of 28 April 2022. Last reviewed November 2026.

Make Trust Provable

See AuditIQ GRC run your frameworks

Book a 30-minute live demo. We map DPDP, ISO and SOC 2 onto one control set using your scope, not a slide deck.

  • 30 minutes
  • No obligation
  • DPIIT Registered
  • 50% off at launch
Book a demo