Regulators in Belgium, France and Germany expect a cookie banner to obtain consent before non-essential cookies and trackers are set, to offer a refuse option as easy to use as accept, to explain each purpose clearly, and to store and honour the visitor's choice. The EU rules behind this are the same in all three countries, but national authorities differ in their guidance and enforcement focus.
Key takeaways
- Non-essential cookies and trackers need prior, informed consent in all three countries.
- Refusing must be as simple as accepting, and regulators check the interface, not only the policy text.
- Pre-ticked boxes, hidden refusal options and consent walls that block content are common failure points.
- The same banner can be compliant in one country and questioned in another, so the configuration should be tested per market.
- Technical consent controls only work if the website's tags and scripts actually respect the stored choice.
What do regulators expect from a cookie banner?
Regulators expect the banner to act as a real choice, not a notice. The starting point is the EU ePrivacy Directive, whose cookie rule requires consent for storing or reading information on a user's device unless the storage is strictly necessary for a service the user asked for. The ePrivacy Directive 2002/58/EC sets that rule, and the General Data Protection Regulation (EU) 2016/679 defines what valid consent means: freely given, specific, informed and unambiguous.
This article is general information and not legal or tax advice.
In practice, four elements recur in regulator guidance. The banner must appear before non-essential tracking starts, it must describe the purposes in plain language, it must offer a refusal as prominent as acceptance, and it must allow the visitor to change the choice later. Consent given through scrolling or continued browsing is generally not treated as valid.
How do Belgium, France and Germany differ?
The core rules are shared, but the national authorities emphasise different things. Belgium, France and Germany each implement the EU framework through their own supervisory bodies and national law, so the practical expectations vary at the margins.
Belgium
The Belgian data protection authority, the Autorité de protection des données (Gegevensbeschermingsautoriteit), has published decisions and guidance on consent collection, including on consent frameworks used for advertising. Businesses in Belgium should treat consent frameworks as part of their own responsibility, not as a vendor setting they can leave unchecked.
France
The French authority, the CNIL, has long stated in its guidance that refusing cookies must be as simple as accepting them. Its guidance also expects a clear way to refuse on the first layer of the banner, not only inside a settings menu.
Germany
Germany implements the storage and access rule of the ePrivacy framework in its national telecommunications and telemedia data protection law, and the federal data protection authority, the BfDI, is one of the bodies that publishes guidance on it. Businesses operating there should check the German wording of the rules and the guidance of the authority responsible for their location, since the supervisory landscape is split between federal and state authorities.
Which cookies need consent?
Only cookies that are strictly necessary for a function the visitor requested can be set without consent. Session management for a login, a shopping cart the visitor filled, or a security token usually qualifies. Analytics, advertising, social embeds and personalisation generally do not.
The classification has to match what the code does. A tag manager that loads a marketing pixel on every page fails the test even if the policy says otherwise. A useful exercise is to list every script, pixel and embedded third-party resource, then mark each one as necessary or non-necessary with a short reason.
What does a compliant banner look like?
A compliant banner presents accept and refuse choices at the same level, with equal visual weight and no pre-selected options. Each category of non-essential cookies is named, explained in one or two sentences, and can be switched on or off individually. A link to the full cookie policy sits in the banner and stays available in the footer afterwards.
- Accept and refuse buttons have equal size, contrast and position.
- Non-essential categories are unchecked by default.
- Purposes and third-party recipients are named in plain language.
- A visible way to change or withdraw consent exists on every page.
- The choice is stored, and the stored choice blocks the relevant scripts.
Technical implementation of this kind of logic is part of the work covered by our web development services, although that is implementation support, not legal or compliance advice.
Where do cookie banners fail?
Most failures are not in the wording. They appear where the interface and the technical setup disagree with what the policy says. Three patterns cause most problems: the refuse option is hidden behind several clicks, the consent state is stored but ignored by a script loaded from a tag manager, or a third-party embed sets cookies before the visitor has chosen.
Consent walls, where access to content depends on accepting tracking, are a further trade-off. Regulators treat them with caution, and a visitor who has a real alternative is in a stronger position to give valid consent. Teams that rely on a consent wall should document why the content is not otherwise available.
A single banner also fails when it is copied between sites. Each site has different scripts, languages and vendors, so the configuration needs to be rebuilt rather than duplicated.
Hypothetical examples of cookie banner setups
Here are two hypothetical scenarios:
- Scenario one: an online shop uses a banner with a large accept button and a small link labelled settings. The refuse path needs three clicks, and the analytics script fires before the visitor chooses. A fix would add an equal refuse button on the first layer and move the analytics tag behind the consent state.
- Scenario two: a services company embeds a video player that sets cookies on load. The banner covers the cookie policy but not the embed. A fix would load the player only after consent, with a placeholder that explains what happens when the visitor accepts.
In both cases the problem is observable in a browser test, which is why checking the live site matters more than reviewing the policy alone. Projects of this kind often sit alongside wider work on system integration, where tag managers, forms and data pipelines all need the same consent state.
Frequently Asked Questions
Do all three countries require a cookie banner?
Not every website needs a banner, but any site that sets non-essential cookies or trackers needs a way to obtain consent before doing so. The obligation comes from the EU ePrivacy framework, which all three countries apply. Whether a banner is the right mechanism depends on what the site actually stores on the visitor's device.
Is a refuse button required on the first layer?
Yes, in practice regulators expect refusal to be available on the first layer of the banner with the same prominence as acceptance. The CNIL guidance in France is the clearest public statement of this expectation. Burying refusal inside a settings menu is a common reason for complaints.
Can consent be assumed if a visitor keeps browsing?
No, continued browsing is generally not treated as a valid expression of consent. Consent should be an active, informed choice that the visitor can withdraw. A banner that disappears after a scroll does not meet that standard.
Does a consent management platform solve the problem?
A consent management platform can help store choices and block scripts, but it does not decide which cookies are non-essential or whether the site's configuration is correct. The website owner remains responsible for testing and maintaining the setup. Regular checks after each change to tags or embeds are the most reliable safeguard.
Who should review the banner before launch?
The review should involve the people who own the website, the people who manage tags and marketing scripts, and someone responsible for legal questions. Technical testing in a clean browser profile should confirm that refusal blocks non-essential requests. Legal conclusions should come from qualified counsel, not from a development team alone.
Request a project consultation at the Rui Codex contact page, or email info@ruicodex.com to discuss how your site's consent setup can be tested and maintained.
Sources
- Directive 2002/58/EC (ePrivacy Directive) - EUR-Lex, Publications Office of the European Union
- Regulation (EU) 2016/679 (General Data Protection Regulation) - EUR-Lex, Publications Office of the European Union
- Autorité de protection des données - Belgian data protection authority
- CNIL - French data protection authority
- BfDI - German federal data protection authority