EU, EEA and United Kingdom

GDPR and ePrivacy: consent before the first cookie

In the EU, the EEA and the UK, anything that is not strictly necessary waits for the visitor’s yes. ConnectWiz holds every tag back until then, puts Reject all beside Accept all, and records each choice.

Denied until the visitor chooses Reject all on the first layer Every choice recorded

Not legal advice

This page describes the law as we understand it on 5 November 2026 and how ConnectWiz behaves. It is not legal advice, and using ConnectWiz does not by itself make a website compliant. When in doubt, ask a lawyer who knows your market.

What the law asks

Consent first, and consent that counts

Consent before storing anything

Under Article 5(3) of the ePrivacy Directive, storing or reading anything on a visitor’s device — cookies, local storage, pixels — needs consent unless it is strictly necessary for a service the visitor asked for. EU law has no analytics exemption today.

A clear, free choice

Consent must be freely given, specific, informed and unambiguous. Pre-ticked boxes do not count, carrying on browsing is not consent, and access to the site cannot depend on accepting.

Reject on the first layer

Most authorities treat a first layer with an accept button but no reject option as an infringement (EDPB cookie banner taskforce, January 2023). Withdrawing must be as easy as consenting.

Proof

You must be able to show that consent was given (GDPR Article 7(1)).

The UK from 5 February 2026

The Data (Use and Access) Act 2025 added exceptions for statistics used to improve a site and for adapting it to the visitor, each with a simple, free way to object. The ICO says none of them covers advertising.

Enforced

On 1 September 2025 the French CNIL fined Google €325 million and Shein €150 million over cookies set without valid consent.

What may change: the European Commission’s Digital Omnibus proposal (November 2025) would add consent-free purposes such as aggregated audience measurement. The Council agreed its position on 21 October 2026; the European Parliament has not, and the law has not changed yet.

In ConnectWiz

Every tag waits for the visitor’s choice

The EU and EEA, the UK and Switzerland are locked to consent first: no region rule can open them.

Denied before the first tag

Every signal is set to denied in the first lines of your page, before any tag can run.

Three buttons, drawn alike

Accept all, Reject all and Preferences look exactly the same on the first layer, whatever the appearance template. Every box starts empty, and the banner never blocks the page.

Withdrawal from any page

The cookie button stays on every page. Withdrawing deletes the known cookies of that category.

A record of every choice

Each choice is recorded and kept for 13 months by default, adjustable from 12 to 120.

Specific and informed

One row per category, with its purpose, its providers, the countries data may go to and each cookie.

A refusal is not asked away

After a yes the banner returns in 1 to 12 months, after Reject all in 6 to 12 — never sooner.

The UK’s new statistics and appearance exceptions are not used: analytics stays off in the UK until the visitor accepts it, which is stricter than the law now requires.

Still yours

What you still need to do

ConnectWiz runs the banner and keeps the records. These steps sit with you.

  • List every cookie your site sets, your own included: run a scan and put the live cookie declaration on your cookie policy page.
  • Write your privacy notice and cookie policy, and link the policy from the banner.
  • Load tags only through consent. A tag that starts before the consent code ignores it.
  • Name ConnectWiz as a processor in your privacy notice and sign the data processing agreement.

The details, with sources

The guide explains each rule in more depth, with the settings that apply it and links to the texts themselves.