Consent Withdrawal Flow Checker

Assess whether your consent withdrawal is as easy as granting it (GDPR Art. 7.3).

Ad placeholder (leaderboard)

A core promise of the GDPR is that consent is freely given and revocable. Article 7(3) is explicit: a person can withdraw consent at any time, and withdrawing must be as easy as giving it. Many sites quietly violate this with a one-click “Accept all” banner but a withdrawal path buried three menus deep — a classic dark pattern. This checker walks you through a structured self-assessment of both flows and returns a symmetry score plus a written finding.

How it works

The tool compares your two flows across four dimensions and looks for asymmetry — places where withdrawal costs the user more effort than granting did:

  1. Steps / clicks: how many discrete actions each path takes. A grant of 1 click vs a withdrawal of 5 is a strong red flag.
  2. Interface location: whether withdrawal lives in the same surface as the consent prompt, or is relocated to a hidden settings page, an email request, or behind a login.
  3. Prominence: whether the original prompt offered an equally prominent reject/withdraw control, or only a prominent accept.
  4. Time to take effect: whether withdrawal is honoured immediately or lags behind, which weakens its effectiveness under Article 7(3).

Each dimension contributes to a 0–100 symmetry score. Larger gaps between the grant and withdrawal answers lower the score. The tool then renders a plain-language finding so you know exactly which dimension to fix first.

Tips and notes

  • “As easy as” is interpreted by regulators as roughly symmetric effort, not identical pixels. A withdrawal that takes one extra confirmation click is usually fine; one that requires contacting support usually is not.
  • The strongest fix is a persistent, always-reachable preference control (e.g. a footer “Cookie settings” link or an in-account toggle) that mirrors the original banner.
  • Remember that withdrawal must be effective: do not keep processing on the old consent after a user opts out. Treat the score as a prompt to verify your backend honours the change promptly.
  • This is a self-assessment aid, not legal advice. For high-risk processing, have your DPO confirm the finding.
Ad placeholder (rectangle)