Engineering consent records for GDPR

A consent record must establish what a person agreed to, when, through which wording and how that choice can be withdrawn. A boolean column cannot carry that evidence alone.

Version the proposition

Store an immutable identifier for the purpose and wording shown at the point of choice. Link translations and interface variants to the same reviewed version without retaining unnecessary page content or device fingerprinting.

Record change as events

Keep grant, withdrawal and replacement events with timestamps and the responsible channel. Derive current state from the valid sequence while retaining enough history to demonstrate that processing stopped after withdrawal.

Connect evidence to suppression

Propagate withdrawal to mailing, profiling and export systems through monitored jobs. Reconcile downstream suppression state and provide a path for subject-access and deletion requests that does not reactivate consent.