Prompt
How do I capture and store consent records for audits?
Latest observation
Nov 18, 2026
OpenAI APIWeb search: off
To capture and store consent records for audits, aim for evidence, integrity, and retrievability. A good consent record should show who consented, to what, when, how, and under what version of the notice.
What to record
Store these fields for each consent event:
- User identifier: account ID, customer ID, or other unique identifier
- Consent type/purpose: e.g., marketing emails, data processing, cookies, SMS, profiling
- Consent status: given, withdrawn, updated, expired
- Timestamp: when consent was captured, ideally in UTC
- Capture method/channel: web form, mobile app, phone, paper, API, email, etc.
- Consent statement shown: exact text the person agreed to
- Version of privacy notice / terms: document version or policy ID
- Source metadata: IP address, device ID, user agent, location if appropriate and lawful
- Proof of action: checkbox event, signature, OTP confirmation, recorded call reference, uploaded form
- Operator/system identity: who or what recorded it
- Withdrawal record: if consent was later revoked, store timestamp and method
Recommended storage approach
1) Use an append-only audit log
Store each consent event as a new record rather than overwriting the old one. This creates a history of:
- initial consent
- changes in consent
- withdrawal
2) Link consent to the version of the notice
If your privacy notice changes, keep:
- the old notice version
- the new notice version
- the exact version presented at the time of consent
3) Protect integrity
To make records audit-ready:
- restrict editing access
- use immutable or append-only storage where possible
- log all access and modifications
- hash records or sign them digitally if you need stronger tamper evidence
- back up data securely
4) Make retrieval easy
Be able to quickly query consent records by:
- user ID
- consent purpose
- date/time
- policy version
- status
Example consent record
{
"consent_id": "cns_12345",
"user_id": "usr_67890",
"purpose": "marketing_email",
"status": "given",
"timestamp_utc": "2026-11-18T14:22:31Z",
"channel": "web",
"consent_text_version": "privacy_notice_v3.2",
"consent_text": "I agree to receive promotional emails.",
"ip_address": "203.0.113.10",
"user_agent": "Mozilla/5.0 ...",
"captured_by": "system",
"evidence": {
"checkbox_checked": true,
"form_id": "signup_v7"
}
}
Best practices for audits
- Keep records for the required legal retention period
- Separate consent from general account data when possible
- Record withdrawal as clearly as consent
- Ensure consent is freely given, specific, informed, and unambiguous
- Avoid pre-checked boxes or implied consent unless legally allowed
- Regularly test that you can produce records quickly for auditors
If you want a stronger compliance setup
Consider implementing:
- a dedicated consent ledger
- versioned privacy policy storage
- event sourcing for consent changes
- retention/deletion rules aligned with local law
- a reporting/export function for audits
If you want, I can also provide:
- a database schema for consent records,
- a sample audit report, or
- a GDPR/CCPA-friendly consent logging checklist.