Dekimu · anchored receipts docs
ACR — Anchored Consent Receipts
Cryptographic proof of a consent decision — what was consented to, by whom, and against which policy.
Purpose
An ACR provides a tamper-evident record of a consent lifecycle event. Each receipt is cryptographically bound to the consent policy in effect at the time of the event, enabling verifiers to confirm that consent was valid, what scope it covered, and whether it has since been modified or withdrawn.
Event types
| Kind | Label | Description |
|---|---|---|
ar.consent.v1 | Consent given | Initial consent recorded. |
ar.modification.v1 | Consent modified | Scope or conditions changed. |
ar.withdrawal.v1 | Consent withdrawn | Consent revoked by data subject. |
Key fields
commitments — ordered list of commitments the data subject accepted. Each entry is a hash of the commitment text at the time of consent.
signing_ceremony — metadata about how the consent was expressed: channel, mechanism (checkbox, signature, verbal, etc.), and timestamp.
profiles — array of applicable regulatory profiles (e.g. gdpr-eu, ccpa-us). Drives which fields are required by the issuer.
Regulatory context
ACR receipts address the requirement under GDPR Art. 7 that controllers demonstrate consent was freely given, specific, informed, and unambiguous. Art. 8 provisions for child consent are supported via the signing_ceremony.parental_consent field. The withdrawal receipt (ar.withdrawal.v1) provides evidence that the Art. 7(3) right to withdraw was honoured.