Consent Tracking
Every consent decision — accepting, declining, or changing a previous choice — is recorded with a timestamp and kept permanently in the user's history. Nothing is overwritten. If you're ever asked to demonstrate that a user gave valid consent, or to show what they were shown when they gave it, that record is there.
What gets recorded for each choice
Each time a user accepts or declines a category, Propper creates an individual record for that choice:
| Field | What it captures |
|---|---|
| Category | Which consent purpose was acted on (e.g., "Analytics Tracking") |
| Decision | Whether the user accepted or declined |
| Timestamp | The exact date and time of the choice |
| Form version | Which version of the consent form the user saw |
When a user changes a previous choice, a new record is added — the old record is never removed. This gives you a complete, chronological history of every consent decision.
Screenshot: click-consent-choice-record, a single consent choice entry in the dashboard showing the category name, accepted/declined decision, timestamp, and form version — making the fields in the table above concrete
Screenshot: click-consent-history-changes, the consent history for one user showing the same category appearing twice — first as "Accepted" on an earlier date, then as "Declined" on a later date — illustrating that changes are appended, not overwritten
The evidence bundle
Each consent session also generates an evidence bundle — a tamper-proof package that captures not just what the user chose, but the exact form they were shown: the wording, layout, and version. This is what you'd produce if a regulator or legal team asked for proof of consent.
For details on what's inside an evidence bundle and how to download one, see Evidence Bundle.
How long records are kept
Consent records are stored for a configurable period and permanently deleted at expiry. The default is 7 years (2,555 days). See Data Retention for how to configure this.
Consent versioning
Each consent record captures the version of the form the user saw. This matters when your consent form changes — you can look back and see exactly which version each user responded to, and whether they've ever been shown the current version.
When you publish an updated template, users who consented under an older version won't automatically be re-prompted. Coordinating that re-consent workflow is currently in development. See Version Management for the current approach.
Viewing consent records
To look up a user's consent history in the dashboard, see Viewing Evidence for full navigation steps. In brief:
- Go to Click → Evidence.
- Search by user ID, email, or date range.
- Select a session to see the individual category choices and the linked evidence bundle.
Screenshot: Click dashboard Evidence section with search filters open, and an expanded consent session showing per-category accepted/declined choices with timestamps
For programmatic access or bulk exports, use the Evidence API.
Troubleshooting
A user's consent preferences aren't being saved. Two things to check: (1) consent preferences are only tracked for Consent Management template deployments, not Static or Generated types; (2) a user ID must be passed when initializing the SDK — without it, preferences can't be persisted across sessions.
A user's consent preferences look wrong. Click stores the user's current preferences and a full history of every change separately. If a user updated their preferences, the current state reflects their latest choice — older choices are preserved in history but are no longer active. To review the full history, filter session records by user ID in Click → Evidence.
Next steps
- User Preferences — how users update their consent and what gets recorded when they do
- Evidence Bundle — full breakdown of what's in each compliance record
- Compliance — how these records satisfy GDPR, CCPA, and other regulatory requirements