Dekimu · anchored receipts docs
ANR — Anchored Notice Receipts
Cryptographic proof of a transparency notice — what was disclosed to a data subject, under which profile, and when.
Purpose
An ANR records that a transparency notice was presented to a data subject: what was said, in which language, via which channel, and whether the subject acknowledged receipt. Re-presentation events capture when an updated notice was shown following a material change to processing activities.
The joint-controller essence event (notice.joint_controller_essence) specifically anchors the GDPR Art. 26 essence disclosure — the summary of responsibilities between joint controllers that must be made available to data subjects.
Event types
| Kind | Label | Description |
|---|---|---|
notice.presented | Presented | Notice shown to data subject. |
notice.re_presented | Re-presented | Updated notice shown. |
notice.acknowledged | Acknowledged | Data subject confirmed receipt. |
notice.withdrawn | Withdrawn | Notice retracted. |
notice.translated | Translated | Notice provided in another language. |
notice.joint_controller_essence | Joint-controller essence | Art. 26 essence disclosed. |
Key fields
notice_content — hash of the notice text presented, with the content version identifier and language code. Allows re-verification of the exact wording shown.
profile — regulatory profile applied (e.g. gdpr-art13, gdpr-art14, gdpr-art26). Determines required field set.
delivery_channel— how the notice was delivered: in-app, email, paper, verbal, or other. Relevant to demonstrating the Art. 12 "concise, transparent, intelligible" requirement.
Regulatory context
ANR receipts provide evidence for the transparency obligations in GDPR Art. 13 (data collected directly from subjects) and Art. 14 (data obtained from other sources). Art. 12 requires that information be provided in a concise, transparent, intelligible, and easily accessible form; the delivery_channel and acknowledgement events help demonstrate compliance with this standard.