Consent Receipt Generator
Generate a structured consent receipt recording who consented, to what processing, when and on what legal basis, as evidence of GDPR consent.
Last reviewed by the Radiatus Cloud team
Generate a structured consent receipt as evidence of consent.
Going for ISO 27001, SOC 2, HIPAA or GDPR?
Radiatus runs end-to-end compliance & GRC programs.
Generate a consent receipt
Under the GDPR, a controller relying on consent must be able to demonstrate that the individual consented, which means keeping a record of each consent. This generator produces a structured consent receipt in JSON, capturing the essential details: a unique receipt identifier, a timestamp, the data subject, the controller, the purpose of processing, the legal basis, and how consent can be withdrawn. This provides an auditable record you can store with your consent logs.
A consent receipt is the practical evidence that satisfies the accountability principle for consent.
Proving consent
Regulators expect controllers to show not just that consent was obtained but what the person consented to, when, and how. A consent receipt records these facts in a consistent, machine-readable form that can be stored and retrieved if challenged. Including the withdrawal method reinforces that consent must be as easy to withdraw as to give, a core requirement of valid consent.
This template captures common fields; a complete consent management process also needs secure storage, timestamping and the ability to honour withdrawals. It is general guidance, not legal advice. All generation happens locally in your browser.
Related tools
- SOC 2 Evidence Readiness — Interactive checklist to gauge your SOC 2 evidence readiness.
- Privacy Policy Checker — Check if your policy covers standard requirements (GDPR/CCPA basics).
- Compliance Req Finder — Find which standards (ISO, SOC2, HIPAA) apply to your industry/region.
- Audit Readiness Planner — Plan your compliance audit timeline (SOC2, ISO) backwards from deadline.
Frequently Asked Questions
What is a consent receipt?
It is a structured record of a consent event, capturing who consented, to what, when, on what basis, and how to withdraw, as evidence of consent.
Why keep consent records?
The GDPR requires controllers relying on consent to demonstrate that it was given, so an auditable record supports the accountability principle.
Why record the withdrawal method?
Consent must be as easy to withdraw as to give, so documenting how individuals can withdraw reinforces that their consent remains valid and revocable.
Is a receipt enough on its own?
No. A full process also needs secure storage, reliable timestamping and the ability to act on withdrawals. The receipt is the record of each event.
Privacy & Security
Everything runs in your browser; nothing is uploaded.
How to Use
Enter the consent details to generate a receipt record.
Disclaimer: This tool is provided "as is" without warranty of any kind. Results are for educational and utility purposes.
Related Tools
SOC 2 Evidence Readiness
ComplianceInteractive checklist to gauge your SOC 2 evidence readiness.
Privacy Policy Checker
ComplianceCheck if your policy covers standard requirements (GDPR/CCPA basics).
Compliance Req Finder
ComplianceFind which standards (ISO, SOC2, HIPAA) apply to your industry/region.