GDPR5 min read
GDPR cookie consent requirements explained
What GDPR and the ePrivacy Directive require before you set cookies: prior opt-in consent, an equal reject option, easy withdrawal and proof of consent.
GDPR + ePrivacy
Cookiesh blocks every non-essential cookie until EU and UK visitors opt in, gives them a reject button as prominent as accept, and keeps proof of each choice that holds up in an audit.
Requirements
Analytics, advertising and other non-essential cookies may not be set or read until the visitor has actively agreed. Loading tags first and asking afterwards is not consent.
How Cookiesh handles it: Known trackers are blocked automatically, your own scripts wait behind data-cookiesh, and Google tags start with every Consent Mode signal set to denied.
Regulators expect a reject option on the first layer, as visible and as easy to use as accept. Pre-ticked boxes and "by continuing to browse" banners do not produce valid consent.
How Cookiesh handles it: EU opt-in banners always show Reject all next to Accept all, with the same size and weight. This cannot be turned off.
Visitors must be able to agree to some purposes and refuse others. One blanket "accept" for every purpose is not specific consent.
How Cookiesh handles it: Four clear categories, with per-category toggles and a full cookie declaration in the preference center.
Before choosing, visitors need to know who sets the cookies, what for and for how long.
How Cookiesh handles it: The cookie scanner fills in each cookie's provider, purpose and lifetime, and keeps the declaration up to date on every scan.
Withdrawing consent must be as easy as giving it, and must stop the processing it covered.
How Cookiesh handles it: A footer link or floating button reopens the preference center. Withdrawing a category deletes the first-party cookies Cookiesh knows belong to it.
Article 7(1) puts the burden of proof on you: you must be able to show that each visitor consented, and to what.
How Cookiesh handles it: Every choice is stored with its timestamp, region and banner version in an append-only, hash-chained log you can export at any time.
Setup
Enter your domain. Cookiesh finds every cookie, storage key and third-party script, and classifies them into categories.
The opt-in rule for the EU, EEA, UK and Switzerland is on by default. Adjust the banner copy and match it to your brand.
Add one script tag, then open your site in a private window and run Cookiesh.debug() to confirm nothing runs before consent.
In depth
Two laws work together. Article 5(3) of the ePrivacy Directive decides when you need consent: for storing or reading any information on a visitor’s device, unless it is strictly necessary for a service the visitor asked for. The GDPR decides what valid consent looks like: freely given, specific, informed and unambiguous, given by a clear affirmative action.
Each EU country implements the ePrivacy Directive in its own law, and its data protection authority enforces it. That is why guidance differs in the details, such as whether some audience measurement is exempt, while the core rule is the same everywhere: no non-essential cookies before opt-in.
In Planet49 (2019), the EU Court of Justice ruled that a pre-ticked checkbox is not valid consent, and that the rule covers all information stored on a device, whether it is personal data or not. The European Data Protection Board’s consent guidelines add that scrolling or continuing to browse is not consent, and that withdrawing consent must be as easy as giving it.
Regulators have since focused on banner design. Several have fined companies for hiding the reject option behind a second click, which is why Cookiesh’s opt-in banners always put Reject all on the first layer.
The UK applies the same model through the UK GDPR and the Privacy and Electronic Communications Regulations (PECR). The Data (Use and Access) Act 2025 relaxes consent for some low-risk purposes, such as certain analytics, as long as visitors are told and can object. Switzerland’s revised data protection act does not require opt-in for every cookie, but many Swiss sites follow EU practice because they also serve EU visitors. Cookiesh’s default rules treat both countries like the EU, and you can change that per region.
This page is general information, not legal advice. Laws and regulator guidance change, so review your setup with your legal team.
FAQ
It can. The GDPR applies to organizations outside the EU that offer goods or services to people in the EU or monitor their behavior, and tracking visitors with cookies is a common form of monitoring.
In most EU countries, yes: the ePrivacy rules require consent for any cookie that is not strictly necessary, wherever it comes from. Some regulators, such as the CNIL, exempt narrowly configured audience measurement, so check your national authority's guidance.
Blocking access unless the visitor accepts tracking is generally not considered freely given consent. Some authorities accept a genuine alternative, such as a paid option without tracking, but the rules vary by country and are under review.
Cookiesh gives you the technical controls the GDPR and ePrivacy rules expect for cookies. Compliance also depends on your privacy policy, your contracts with vendors and how you use the data, so review your setup with your legal team.
GDPR5 min read
What GDPR and the ePrivacy Directive require before you set cookies: prior opt-in consent, an equal reject option, easy withdrawal and proof of consent.
GDPR5 min read
The ePrivacy Directive decides when cookies need consent; the GDPR defines what valid consent means. Here is how the two EU laws fit together in practice.
GDPR5 min read
A practical checklist of the GDPR conditions for valid cookie consent: freely given, specific, informed, unambiguous, provable and easy to withdraw.
Start free on one domain. Upgrade when you need more domains, geo-targeting or custom branding.
No credit card required · Cancel anytime