ANCHORED NOTICE RECEIPTS

Anchored Notice Receipts

Records the delivery and acknowledgement of a transparency notice. Bridges the gap between 'we published it' and 'the subject saw it' — the cryptographic foundation required before a valid ACR consent can be issued.

ANR · Shipped6 wire typesApache-2.0 · CC0 spec
← All familiesVerify a receipt →

WIRE TYPES

ar.notice.v1 (notice.presented)

Records that a privacy notice was presented. Carries the policy_uri, policy_hash, and version — the subject chain starts here.

ar.notice.v1 (notice.re_presented)

Records a material-change re-presentation. The supersedes_anr_id field points at the prior notice receipt, and the predecessor's Status List bit flips to superseded.

ar.notice.v1 (notice.acknowledged)

Records a per-subject acknowledgement of a presented notice. The subject is a sha256 commit; the verifier confirms prev resolves to a presented receipt on the same chain.

ar.notice.v1 (notice.withdrawn)

Records that the controller has deprecated a notice. XOR body — either supersedes_anr_id (replacement exists) or cessation_reason (processing ceased, no successor).

ar.notice.v1 (notice.translated)

Records a translated version of a base notice. Branches from the base receipt — envelope prev is forced null. May optionally reference an ALR receipt for translation provenance.

ar.notice.v1 (notice.joint_controller_essence)

Records the Art. 26(2) essence of a joint controller arrangement — the controller list, their respective responsibilities, and the contact point for data subjects.

WHAT IT PROVES

  • — A specific privacy notice was presented to subjects before a given UTC date (Merkle inclusion proof).
  • — The notice content matches a specific policy_hash (content integrity check).
  • — A subject acknowledged seeing the notice (per-subject chain link).
  • — The complete succession history of a notice — presentations, re-presentations, and withdrawals (chain walk).

WHAT IT DOESN'T PROVE

  • — The subject understood the notice content.
  • — The notice was written in clear and plain language (Art. 12(1) substance).
  • — The controller actually follows the policy described in the notice.
  • — The notice was presented in a timely manner relative to data collection.

COMPOSES WITH

ANR receipts reference other family members via body-level composition pointers — verifier-coordinated, not signature-mandated.

ACRAnchored Consent Receipts

ACR v1.2+ MUST reference an ANR receipt — consent is only informed if the subject saw the notice first.

ALRAnchored Lineage Receipts

Translated notice events may reference an ALR receipt for translation provenance.

AERAnchored Evaluation Receipts

AI Act Art. 50 transparency profile may cross-check the provider DID against an AER receipt.

ADRAnchored Delegation Receipts

Joint controller essence events may reference ADR grants for each controller in the arrangement.

Verify any
ANR receipt.

verify.dekimu.com ↗

Paste any claim ID to verify a receipt, check its anchor, and inspect the issuer signature.

REFERENCES

GDPR Arts. 12–14 — Transparency and information obligations (EUR-Lex) ↗
GDPR Art. 26 — Joint controllers (EUR-Lex) ↗
AI Act Art. 50 — Transparency obligations (EUR-Lex) ↗

Anchored Notice 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.