Consent receipts & evidence
Prove consent for any visitor and date.
Stored rows are not the same as provable evidence. When an auditor asks you to prove a specific visitor consented on a specific date, most teams cannot. ConsentX issues a receipt for every consent and binds records into a SHA-256 hash chain you can verify with one command.
Each consent gets a hashed receipt; records are chained so any tampering is detectable.
The problem
When an auditor asks you to prove a specific visitor consented on a specific date, most teams cannot. Stored rows are not the same as provable, tamper-evident evidence.
With ConsentX
Every consent carries a receipt and a hash, chained so tampering is detectable. You resolve a per-visitor receipt and export audit evidence in minutes, not weeks.
How it works
Snapshot the notice
ConsentX versions and hashes the policy text the visitor actually saw.
Issue a receipt
Each consent gets a Kantara-style receipt with the policy version and hash.
Verify the chain
A SHA-256 hash chain binds records so tampering is detectable on demand.
A closer look
A receipt for every decision
ConsentX versions and hashes the exact notice the visitor saw, then issues a Kantara-style consent receipt carrying the policy version, the policy hash, the categories chosen and a receipt ID. The receipt captures what was agreed to, not just that something was.
You can resolve a per-visitor receipt on demand, showing precisely what a given person agreed to and when, which is what vendor-risk reviews and regulators actually ask for.
Tamper-evident by design
Records are bound into a per-record SHA-256 hash chain, so altering any historical consent breaks the chain and is detectable. A reports:verify command checks integrity, turning your consent log into evidence rather than a list of rows that could have been edited.
Audit evidence exports in minutes, with monthly compliance reports (PDF and CSV) and a per-record hash chain that makes the export defensible.
Capabilities
What you get
- Kantara-style consent receipts
- Policy version and hash on every consent
- Per-record SHA-256 hash chain
- Audit evidence exported in minutes
Built for enterprise
Answer vendor-risk and audit questions in minutes
Tamper-evident, not merely stored
Per-visitor proof for any date
Defensible monthly compliance reporting
Try Consent receipts & evidence free
Install in minutes. Free plan, no credit card.
Frequently asked questions
What does tamper-evident mean?+
Records are chained with SHA-256 so any change breaks the chain and is detectable. It is provable, not just stored.
Can I prove consent for one visitor?+
Yes. You can resolve a per-visitor receipt showing exactly what they agreed to and when.
What is a consent receipt?+
A Kantara-style record of what the visitor was shown and agreed to, including the policy version and hash.