Blast-radius query
Given an affected system, return the data categories and principal count in minutes.
Section 8(6)·Response·9/12
Breach Response
The clock starts before you are ready
A personal data breach must be reported to the Data Protection Board and to affected people. The hard part is not the form — it is knowing within hours whose data was in the blast radius. This module answers that from your existing map.
- Blast radius
- MinutesBlast radius
- Notices generated
- 2Notices generated
- Drill cadence
- QuarterlyDrill cadence
console / breach-responseLive
Breach Response
Section 8(6) · Response
- Blast-radius query
- Guided reporting
- Response playbooks
- Drill mode
MinutesBlast radius
2Notices generated
QuarterlyDrill cadence
What Breach Response does
Four capabilities that together close this obligation — and feed the same audit log every other module writes to.
Book a walkthroughGuided reporting
Structured intake that produces the Board notification and the individual notice together.
Response playbooks
Named roles, comms drafts and escalation paths agreed before an incident, not during.
Drill mode
Run a tabletop exercise against real data without triggering real notifications.
Severity classification
Structured triage that separates a reportable breach from an incident, with the reasoning recorded.
Notification tracking
Who was notified, when, through which channel, and what the message said.
From zero to live breach response
- 11 day
Define the playbook
Named roles, escalation path and comms owners agreed while nothing is on fire.
- 2Instant
Connect the map
Blast-radius queries run against your existing inventory and data map.
- 32 hours
Run a drill
Tabletop exercise against real data, with no real notifications sent.
What changes on day one
Without Breach Response
- Blast radius takes days of engineering queries
- The notification is drafted under time pressure
- Nobody has rehearsed the process
With Breach Response
- Affected categories and counts in minutes
- Board and individual notices generated together
- Quarterly drills against real data
Common questions
Every personal data breach must be reported to the Data Protection Board and to affected data principals. There is no severity threshold below which you may stay silent.
Other modules
11 moreConsent Management
Capture, version and honour every consent
Cookie Consent
A banner that does not quietly break the law
Data Inventory
Know what personal data you hold, and why
Data Map
See where personal data travels
Rights Portal
Every data principal request in one queue
Compliance Dashboard
One number your board will actually ask for
Risk Register & DPIA
Assess before you launch, not after
Vendor Risk
Your processors are your liability
Data Retention
Delete on schedule, and prove it
Cloud Security Posture
Reasonable safeguards, continuously checked
Compliance AI
Ask your compliance posture a question
Get the DPDP readiness checklist, free
42 questions covering every operative section of the Act. No account needed — tell us where to send it.
30 minutes·one real data flow
Ready to Simplify DPDP Compliance?
Most vendors open a deck. We open the product, map one of your real data flows, and tell you honestly how far you are from compliant.
- No slides
- No obligation
- Data stays in India
What the 30 minutes looks like
- 0–5Your stack, in your wordsWhere data lands today, and who already owns it.
- 5–15One real flow, mapped liveWe connect a sample source and build the map on the call.
- 15–25Where you are exposedThe gaps we can see, ranked — including the ones you already knew.
- 25–30Effort and costWhat closing them takes, and whether we are the right answer.
If we are not the right fit, we will say so on the call rather than three follow-ups later.