Breach ManagementSection 8(6)

Personal Data Breach Response

Triage, classify, notify the Data Protection Board within 72 hours, and document the post-incident review.

The problem

The 72-hour breach notification clock under Section 8(6) starts the moment your team becomes aware of facts that suggest a breach may have occurred — not the moment you have certainty. Most Indian organisations have no incident-response runbook tailored to that clock, no template for the Board notification, and no forensic chain-of-custody. When the first real incident lands, they spend 48 of the 72 hours figuring out who decides what.

What you get

Capabilities, not feature toggles

Every capability below is a working part of the AutoCops application — not a roadmap promise.

Incident intake + war room

One link to start an incident. AutoCops creates a dedicated channel, pages the on-call team, and starts the 72-hour clock from your declared time of awareness.

Severity classifier

Walk through a structured questionnaire and AutoCops scores the incident on five dimensions: scale, sensitivity, impact, recoverability, and notification triggers. The output tells you whether the Board notification is mandatory and whether affected Data Principals must be informed.

Board notification template

Pre-written, lawyer-reviewed Board notification that auto-fills the incident facts. You edit, your DPO signs, you submit. The clock stops when the submission is acknowledged.

Affected-principal notification

Bulk email or SMS notification to affected Data Principals, in their language, with a personalised explanation of what happened, what data was affected, what the organisation is doing, and what they can do.

Forensic timeline

Every action taken during the incident — every decision, every comm, every file uploaded — is timestamped and chained to the incident record. Your post-incident review writes itself.

Drill mode

Run a tabletop exercise without polluting the production audit trail. Practice the 72-hour scramble before it's real.

How it works

From zero to live in days, not months

1
Declare
Anyone with access can declare an incident. The clock starts at the declared moment of awareness.
2
Classify
The structured triage produces a severity score and tells you which notifications are mandatory.
3
Notify
Send the Board notification within 72 hours and (where required) the affected-principal notification.
4
Remediate
Track containment, eradication, and recovery actions in the incident timeline.
5
Review
Post-incident review with timeline, decisions, lessons, and corrective actions — exported as a PDF for the audit committee.

Common questions

Things buyers ask in the demo

What if we're not sure it's actually a breach?+

Declare it anyway. Section 8(6) awareness is a legal concept, not a forensic one. Declaring early and downgrading later is much safer than declaring late.

Can we use this for incidents that aren't breaches?+

Yes — many teams use AutoCops for any privacy-relevant incident, even when notification isn't required. The platform handles the workflow regardless of whether the incident becomes a notification event.

Ready to see it on your data?

Book a 30-minute walkthrough

Our compliance engineering team will show you personal data breach response live on your environment, with your data, in your timezone.

Book a demo →Take the free assessment

Personal Data Breach Response

Capabilities, not feature toggles

Incident intake + war room

Severity classifier

Board notification template

Affected-principal notification

Forensic timeline

Drill mode

From zero to live in days, not months

Declare

Classify

Notify

Remediate

Review

Things buyers ask in the demo

Book a 30-minute walkthrough

Related capabilities

Consent Management Platform

Cookie Consent & Banner

DSR & Rights Fulfilment