Regulations
GDPR cookie consent for your website
In the EU and the wider EEA, optional cookies and trackers need consent before they run. Velo starts every visitor there with everything denied, and keeps proof of each choice.
State laws at a glance
General information, checked September 2026. Not legal advice.
The rule
- Applies to. Websites with visitors in the EU and the EEA, wherever the business is based.
- The rules. Article 5(3) of the ePrivacy Directive for cookies, as each country applies it, and the GDPR for what consent means.
- Consent model. Opt in, so nothing optional runs until the visitor chooses.
In practice
- Enforced by. Data protection authorities, such as the CNIL in France or the AEPD in Spain. In some countries a telecoms or consumer regulator handles cookies.
- Maximum fine. Under the GDPR, 20 million euros or 4% of worldwide annual turnover, whichever is higher. Cookie fines are often issued under national ePrivacy laws instead.
- Velo default. Every Consent Mode v2 signal starts denied in the EU, the EEA and Switzerland.
What the GDPR asks for, and how Velo handles it
Two pieces of European law meet on your cookie banner. The ePrivacy Directive says a site may store or read information on a visitor's device only with consent, unless it is strictly necessary for a service the visitor asked for. The GDPR then sets the standard for that consent: freely given, specific, informed and unambiguous, and given by a clear action.
Consent before anything optional
The ePrivacy rules require consent before a site stores or reads non essential cookies. For visitors in the EU, EEA and Switzerland, Velo starts with every Consent Mode v2 signal denied until they choose.
Clear choices by category
Consent has to be specific and informed. Visitors pick analytics, ads, functional and personalisation separately, and your tags follow what they chose.
Velo handles the banner, the regional defaults and the records. These parts are still up to you.
What the law actually says
In practice that means no analytics or advertising tags before a choice, a reject option as easy to find as accept, no boxes ticked in advance, and a simple way to change the decision later. Design counts too. In its 2023 report, the European Data Protection Board’s cookie banner taskforce flags banners that offer accept on the first layer with no way to reject there, and reject buttons whose text is too faint to read.
The banner is only part of it. Your privacy notice has to explain the purposes and name the third parties, and you need to be able to show what each visitor agreed to.
Proof you can show. Article 7 says you must be able to demonstrate consent. Each decision is stored as an unchangeable record with a receipt id, the region and the banner version it answered.
As easy to withdraw as to give. Withdrawing has to be as easy as consenting. A small floating button stays on the page so visitors can reopen their choices at any time.
Up and running in four steps
From the first script tag to the first recorded choice.
Pick your platformAdd Velo to your site
Install it with the Google Tag Manager template or paste one script tag. Guides cover WordPress, Shopify, Webflow and other platforms.
Scan and sort your cookies
Velo scans your pages, lists the cookies and scripts it finds and suggests a category for each one. You confirm or change them.
Design the banner
Pick colours, wording and languages. Reject sits next to accept on the first layer.
Publish and check
Visitors in the EU and EEA get opt in defaults, with every consent signal denied until they choose. Each choice lands in your consent log with its receipt id.
Before you go live
Velo handles the banner, the regional defaults and the records. These parts are still up to you.
These parts stay with you
- Your privacy or cookie notice names each purpose and each third party that sets cookies.
- Tags in Google Tag Manager wait for the matching consent signal before they fire.
- You tested from the region itself and saw that nothing optional loads before a visitor chooses.
- Someone on the team reviews new scripts when a scan finds them.
- Your agreements with tag vendors match their role: processor contracts under Article 28, or joint controller terms where a vendor uses the data for its own purposes.
In every plan, from €0
- Consent Mode v2 advanced, with defaults set before your other tags run
- Regional defaults by country, and Global Privacy Control honoured
- A receipt for every choice, kept in the consent log
- Reject as easy as accept, and a floating preferences button
- Cookie and tracker scan, with choices by category
Start with a scan
See what your homepage already loads before you install anything. The free scanner reads the page and your public Tag Manager container.
A first pass, not a verdict. Four checks on your homepage, and we open your container.
Free for one site and 1,500 monthly sessions. Pro from €7 a month, plus VAT, for unlimited sites.
Step by step installs for WordPress, Shopify, Webflow, Wix and more.
Questions people often ask
Is the GDPR the law that requires a cookie banner?
The duty to ask before placing non essential cookies comes from the ePrivacy Directive, as each EU country applies it. The GDPR sets the standard that consent must meet: freely given, specific, informed, unambiguous and as easy to withdraw as to give.
Are ticked boxes or scrolling valid consent?
No. The Court of Justice ruled in Planet49 (2019) that boxes ticked in advance do not give valid consent, and European regulators treat scrolling or continued browsing the same way. Velo asks for an active choice.
What can happen if consent is wrong?
Supervisory authorities can order changes and issue fines. The GDPR allows fines of up to 20 million euros or 4% of worldwide annual turnover, whichever is higher, and cookie banners are a regular enforcement topic.
Does Velo make my site GDPR compliant?
Velo handles the consent layer: defaults, choices, records and withdrawal. Compliance also depends on your privacy notice, your vendors and how your tags are set up. This page is general information, not legal advice.
Do I still need Google Consent Mode v2?
If you use Google advertising products with visitors in the EEA, Google requires consent signals, which you can pass through Consent Mode v2. Velo sends them for you, starting denied in the EU.
Free for one site
Banner, scan and consent records for one site, free. Pro from €7 a month, plus VAT, for unlimited sites.