ANCHORED BREACH RECEIPTS
Records the personal-data breach lifecycle — detection, assessment, DPA notification, subject notification, containment, and closure. Anchors the 72-hour Art. 33 reporting clock against an independently verifiable timestamp.
WIRE TYPES
ar.breach.v1 (breach.detected)
Records the moment a breach was detected. Carries a MANDATORY TSA timestamp — the 72-hour Art. 33 reporting clock starts here and is anchored to an independent time authority.
ar.breach.v1 (breach.assessed)
Records the risk assessment outcome — severity classification, categories of data affected, approximate number of data subjects, and likely consequences.
ar.breach.v1 (breach.dpa_notified)
Records that the supervisory authority was notified. References the DPA identifier and notification method.
ar.breach.v1 (breach.dpa_delayed)
Records a justified delay in DPA notification — the reason, legal basis, and expected notification date.
ar.breach.v1 (breach.subject_notified)
Records that affected data subjects were notified of the breach. Subject field carries the pseudonymous commit.
ar.breach.v1 (breach.subject_notification_exempted)
Records a justified exemption from subject notification — encrypted data, disproportionate effort, or public communication alternative per Art. 34(3).
ar.breach.v1 (breach.contained)
Records that containment measures have been applied. The breach chain remains open until closure.
ar.breach.v1 (breach.closed)
Records the formal closure of the breach lifecycle. Terminal event — the chain is complete.
WHAT IT PROVES
WHAT IT DOESN'T PROVE
COMPOSES WITH
ABR receipts reference other family members via body-level composition pointers — verifier-coordinated, not signature-mandated.
Breach receipts may reference ARR events documenting the retention status of affected data.
Cross-border breach notification may reference ATR receipts for the transfer mechanisms involved.
Post-breach evaluation of AI system involvement may reference AER conformity receipts.
Subject notification events may reference ANR receipts for the breach notice delivered.
DPA submissions requiring qualified e-signatures may reference AAR receipts for the QTSP issuance.
Verify any
ABR receipt.
Paste any claim ID to verify a receipt, check its anchor, and inspect the issuer signature.
REFERENCES
Anchored Breach Receipts are cryptographic provenance and privacy-lifecycle protocols. verify.dekimu.com is a reference implementation, not a qualified trust service under Regulation (EU) No 910/2014 (eIDAS) or successor.