platform-guideline checked

ICO: How should we obtain, record and manage consent?

Supports consent request design, keeping records, consent management, withdrawal, refresh, and proof that the user was presented with a clear consent request.

Open source

Pattern Decisions This Source Supports

Pattern Supported decision Required contract Claim note
Consent prompt Choose consent prompt when the user must actively opt in to a specific optional data use, communication, study, sharing arrangement, personalization feature, AI training use, or sensitive-data processing purpose. The prompt appears before optional processing begins and states exactly what agreeing enables. Supports consent record, management, withdrawal, refresh, and proof requirements.
Dark-pattern consent Flag this anti-pattern when accepting optional consent is one click but declining, customizing, or withdrawing requires extra pages, hidden links, confusing labels, or repeated confirmation. Acceptance, rejection, customization, and withdrawal must be reachable with comparable effort for optional purposes. Supports consent records, consent management, withdrawal, refresh, and evidence requirements.

Evidence Role

This source is treated as platform-guideline evidence. Use it to validate the decision rules above, not as a visual style reference.

Publisher: Information Commissioner's Office. Last checked: .