Consent Audit Trail

The frontend capture mechanism that presents notices and records user choices. A CMP is the primary data source for the audit trail, generating the initial consent receipt with a timestamp, purpose list, and proof of notice. Without a properly configured CMP, the audit trail has no origin event to log. Modern CMPs integrate with the IAB Transparency and Consent Framework (TCF) to propagate signals downstream.

The backend process of resolving conflicting consent states for a single identity across devices, browsers, and systems. A user may consent on mobile but withdraw on desktop. Reconciliation algorithms must determine the authoritative state—typically the most recent valid interaction—and propagate it to all downstream processors. This resolution event itself must be logged in the audit trail with a clear rationale.

A privacy design pattern where users provide separate opt-in choices for distinct processing purposes rather than a single bundled agreement. Granularity directly impacts audit trail complexity: each purpose becomes a discrete consent signal that must be independently logged, timestamped, and linked to the specific notice text shown at the moment of collection. Bundled consent produces a single record; granular consent produces a matrix.

The immutable recording of AI-driven decisions and their inputs for auditability. While consent audit trails capture human choices, automated decision logs capture model inferences. The two intersect when a user exercises their Right to Explanation under GDPR Article 22: the audit trail must prove what consent was in effect when an automated decision was made, linking the human choice to the algorithmic outcome.

A browser-level signal that communicates a universal opt-out preference to every site visited. Legally recognized under CCPA/CPRA, GPC complicates audit trails because the consent signal originates outside the CMP. The trail must record: the raw GPC header received, the timestamp of detection, and the system's interpretation of that signal against existing per-site preferences. This creates a machine-originated consent event.

The automated mapping of personally identifiable information's origin, movement, and storage locations. Consent audit trails depend on data lineage to answer the question: 'Where did data collected under this consent go?' When a user withdraws consent, lineage tools trace every system that received the data, enabling complete erasure. The audit trail records the withdrawal; lineage proves the downstream propagation was executed.