Storage is browser-managed. Private browsing may provide session-only storage even when this capability check succeeds; export important records before closing that session.

← DPDP workspacePhase 4 · local only

Breach playbook & timer

Prepare locally for two separate Rule 7 milestones. This workspace does not notify the Data Protection Board (DPB), affected Data Principals, email, SMS, WhatsApp, or any messaging API.

Legal timing boundary: Rule 7(1) calls for notification to the Data Protection Board (DPB) and affected Data Principals without delay. Rule 7(2) sets the detailed report to the Board at within 72 hours of becoming aware.

This prepares for an obligation taking effect 13 May 2027; Rule 7 is not presented here as currently enforceable. Source: Digital Personal Data Protection Rules, 2025, notified 13 November 2025.

Incident preparation

Editable, user-authored filing fields

Use categories and approximate counts. Do not enter raw Aadhaar/PAN values, customer records, credentials, or secrets.

Rule policy v1

Incident title *Severity

StatusAwareness time *

Timer timezone: local device time. The calculation is pause-free and uses the device clock; manual clock changes can affect the displayed result.

Affected data categoriesSystems involvedApproximate affected Data PrincipalsNotification status

Incident descriptionContainment actionsRisk assessmentMitigation

Contact nameContact emailContact phone

Reference numberInitial notice preparation — Rule 7(1)Detailed report preparation — Rule 7(2)Notes

Preparation checklist

Export boundary: JSON and PDF are generated in-browser and downloaded only when you choose. They are preparation artifacts, not filings, notifications, acknowledgements, or regulator-approved evidence.

Stored in dedicated IndexedDB. DPDP records are not included in peer-sync in v1.

Editable, user-authored filing fields

Preparation checklist

34-Control Compliance Checklist PDF

Peer-to-Peer Browser Sync