πŸ“˜ Guide

DPDPA Breach Response

Guides Β· DPDPA

Under the DPDPA, a personal-data breach must be notified to the Data Protection Board and to each affected data principal. Speed and preparation decide whether you meet your obligations.

Know your clocks

Indian organisations often face stacked deadlines: CERT-In directions require reporting certain cyber incidents within 6 hours; the DPDPA requires breach intimation to the Board and affected principals. If you also fall under the GDPR, that’s a 72-hour authority clock too. Every clock starts from when you become aware.

Build the playbook before the breach

  1. Detect & log the “aware” time precisely.
  2. Contain and preserve evidence.
  3. Assess scope: whose data, what categories, how many.
  4. Notify the regulator(s) and affected principals using pre-drafted templates.
  5. Remediate and record lessons learned.

What to tell people

Give affected principals a clear, plain-language notice: what happened, what data was involved, what you’re doing, and what they should do.

Multi-clock, one click

PrivacyOS’s breach register runs CERT-In, DPDPA and GDPR clocks from your “aware” time and sends templated regulator and principal notifications in one click.

Related guides

Operationalize this with PrivacyOS

Turn guidance into a live, audit-ready program β€” discovery, obligations, evidence and reporting in one platform.

Book a demo Free assessment
Binar3 PrivacyOS Β· Privacy compliance, operationalized.
This guide is general information, not legal advice.