Skip to content
Privacy tools

Cookie consent your visitors can control

Policy generation is paused. Check your existing policy against your website.

Inventory cookies and requests, prepare a cookie-policy draft, and check whether the installed consent controls match the choices visitors make.

Updated 1 Oct 2026 against official EU and CNIL guidance

Start with your website

I have the link to my privacy policy

Optional. If you paste the direct link, we read that page instead of looking for it, so the check is more exact.

By scanning, you confirm that you own this website or are authorized to test it, and you agree to our Terms.

No account needed.

What to account for

  1. Consent before non-exempt storage

    The EDPB taskforce says cookies requiring consent must wait for an affirmative choice. Preselected opt-in boxes do not create valid consent.

  2. Withdrawal and an understandable explanation

    GDPR Article 7 requires withdrawal to be as easy as giving consent. Article 13 covers information including purposes, recipients, retention and rights.

  3. Classify purpose, not just the name

    CNIL describes conditional exemptions for audience measurement. “Analytics” is not a universal exemption: check configuration and the rules of the relevant jurisdiction.

Common mistakes to check

  1. Accept is obvious; reject is hidden

    The EDPB report records broad regulatory opposition to consent layers without a rejection option. It also documents differences between authorities; avoid claiming a single universal button design.

  2. Treating scrolling as consent

    CNIL rejects scrolling or swiping as consent and requires operators to demonstrate consent. A disappearing banner is not evidence of an affirmative decision.

Your review checklist

Our suggested review process. The linked requirements above explain the platform or legal basis.

  1. Record what loads

    Scan the site and review cookies separately from scripts and requests. Confirm vendor purposes; leave unknown uses unresolved rather than guessing.

  2. Connect choices to loading

    Configure categories and the consent snippet. Wire each non-essential integration to the choice; merely installing the snippet does not retroactively stop scripts already running.

  3. Test four states

    Inspect network and storage before any choice, after rejection, after selective acceptance and after withdrawal. Repeat for important regions and logged-in areas outside the public scan.

Example

  1. Fictional site: Harbor Journal

    Assume a preference cookie and an advertising pixel. The owner confirms their purposes. The proposed setup starts with advertising off and offers accept, reject and purpose settings.

  2. The test that matters

    In a fresh browser, the reviewer sees the ad request only after acceptance. After withdrawal, a reload must respect the new choice. Record failures as implementation work, not as a policy wording fix.

Questions before publishing

  1. Is every cookie subject to consent?

    No. Exemptions exist, including narrowly conditioned audience measurement in CNIL guidance. Establish the actual purpose and applicable rules before marking a cookie exempt.

  2. Can visitors change their mind?

    Yes. GDPR consent can be withdrawn at any time. Explain this before consent and provide a withdrawal method as easy as the original choice.

  3. What should I test before publishing?

    Review vendor purposes, regional behavior and private flows. Check that the installed controls honor each choice and that the policy matches those results.

Source review and changes

First edition: platform requirements, implementation checks and fictional worked example. Sources reviewed on the date above; verify changes before relying on them.