Core Concepts
Consent receipts
Append-only records of subject choices tied to a published consent version.
Consent receipts
What it is
An append-only record of what a subject chose, tied to a consent version (and related hashes/ids as stored by the product).
Why it exists
Without receipts, "they clicked Accept" is not reconstructible. Receipts make choices durable, listable, and exportable for operators.
How Erasure uses it
| Behaviour | Detail |
|---|---|
| Create | SDK posts consent after a choice (or preference update) |
| Immutability | Preference changes create a new receipt, not an in-place edit |
| Console | Project Receipts explorer |
| Privacy design | Core path does not require IP / email / fingerprint on the receipt |
| Identity (v1) | Browser installation id for correlation, not full subject accounts |
| Evidence | Publish evidence can include receipt counts for a version |
What a receipt is not
- Not a cookie inventory
- Not a substitute for legal counsel
- Not multi-device "same user" identity across phones and laptops (v1)
Related
For a schema design that captures all three of these properties, see Consent database schema and the consent management hub.