Evidence tied to the original wording
Approval creates an immutable version with snapshot and checksum. Every declaration refers to it, per purpose, including refusals.
Data Protection & GDPR
Consent Management
Collect consent, prove it by version and let people withdraw it with one click
Article 7 GDPR puts the burden of proving consent on the controller. A tick box with a date is not enough: what must be shown is how and when consent was given and which text the person saw. The module therefore treats consent texts as approved versions and links every declaration to exactly the wording the person agreed to. When the text changes substantially, it is immediately clear whose consent needs renewing.
DSGVO Art. 7DSGVO Art. 8EDSA-Leitlinien 05/2020TDDDG § 25
Features
Your benefits
Tamper-evident chain
A person's evidence events are hash-chained. Any later change in the database breaks the chain, and verification shows where.
Withdrawal as easy as giving consent
Preference centre via link, "My consents" for employees and withdrawal from a data subject request. The person responsible is notified.
Capabilities
All capabilities at a glance
- Templates with granular purposes per processing activity
- Versioning with approval, optionally under the four-eyes principle
- Renewal after a substantial change
- Public collection with double opt-in
- Paper and oral declarations with evidence note
- Preference centre and "My consents"
- Withdrawal from data subject requests
- Cross-check with the record of processing activities
- Cross-check of website templates with the cookie scan
- CSV import of existing consents, REST API and MCP
Result
For every consent you can show which text the person agreed to, and after every change you know whom to ask again.
Background
Articles on Consent Management
Experience Consent Management live
Schedule a no-obligation demo – we will show you the module with your own use cases.