Skip to content
Talk to us

Cookies before consent: what Irish law actually requires

What Irish law requires before a cookie is set, how to check your own site in a minute, and why the penalty everyone quotes belongs to a different regulation.

Jack O'Connor· 8 min read· ·Updated

The rule in Ireland is Regulation 5(3) of S.I. No. 336 of 2011. You may not store information, or gain access to information already stored, on someone’s device unless they have consented and you have given them clear and comprehensive information about what you are doing and why.

That covers analytics cookies, advertising cookies and most of what a tag manager loads. It does not cover storage that is strictly necessary to provide the service the visitor actually asked for.

The penalties are widely misreported. Regulation 5 contains no offence clause, so setting a cookie without consent is not in itself a criminal offence in Ireland. The enforcement route is that the Data Protection Commission serves an enforcement notice, and ignoring that notice is the offence. Separately, where the cookie processes personal data, GDPR applies in its own right.

The practical test takes about a minute. Open your site in a private window, do not touch the banner, and look at what is already in storage.

What does Irish law actually require?

Two things, together, before anything is written to or read from the device.

Consent from the subscriber or user. Regulation 5(3)(a).

Clear and comprehensive information, prominently displayed and easily accessible, that includes the purposes of the processing. Regulation 5(3)(b).

Regulation 5(4) adds that the methods of giving information and obtaining consent should be as user-friendly as possible. The standard for what counts as consent comes from data protection law, which means it has to be freely given, specific, informed and unambiguous. A pre-ticked box is not consent. Continuing to scroll is not consent.

Which cookies need consent, and which do not?

Regulation 5(5) is the exemption, and it is narrow. Storage or access is allowed without consent where it is for the sole purpose of carrying out the transmission of a communication, or where it is strictly necessary to provide a service that the subscriber or user has explicitly requested.

A session cookie that keeps someone logged in is strictly necessary. A basket cookie on a shop is strictly necessary. A cookie that remembers a language choice the visitor made is a reasonable case.

Analytics is not strictly necessary. It is useful to you and invisible to the visitor, which is precisely the distinction the exemption draws. The same goes for advertising pixels, heat mapping and session recording.

Embedded content counts as well. A YouTube or Vimeo player, a live chat widget, a social feed or a booking tool usually sets or reads storage of its own as soon as the page loads, so each one needs consent first, or has to be held back until the visitor gives it.

The honest position is that most sites need consent for most of what they load, and the exemption covers less than people hope.

How do I check whether my site sets cookies before consent?

You do not need a tool for this.

Open your site in a private browsing window so nothing is carried over. Do not click the banner. Open the browser developer tools, go to the storage or application tab, and read the cookie list.

If the only thing there is your consent platform’s own record of the fact that you have not answered yet, the site is behaving. If you see names beginning with _ga, _gid, _fbp, _hj, sbjs_, _pk_ or anything from an advertising network, the site is setting cookies it should not be setting.

Check the network tab too. Requests going out to analytics or advertising endpoints before you consent are the same problem in a different form.

Do this on a page a stranger would actually land on, not just the homepage. Landing pages and blog posts often load scripts that the homepage does not.

How do I fix it?

There are two approaches and they are not equivalent.

Blocking the script until consent is the blunt version. The tag does not load at all, so nothing is written and nothing is sent. It is compliant and it means you measure nobody who declines.

Google Consent Mode is the better version for anything in the Google stack. The tag loads, but it is told before it runs that storage is denied. It then sends a cookieless ping that carries no identifier and writes nothing to the device. When the visitor consents, a second signal upgrades it to full measurement.

The detail that matters is ordering. The default consent state has to be set before the tag loads, not after. A consent banner that only announces the visitor’s choice once the analytics script has already run is too late, and it is the most common way this is got wrong. The default has to be the first thing in the page, and the tag comes after it.

You can verify it the same way you found the problem. With consent denied there should be no analytics cookie on the device, and any request to Google should carry a consent signal showing storage denied.

What does the banner itself have to do?

The Data Protection Commission’s guidance note on cookies and other tracking technologies, published in April 2020, is specific about the banner as well as the storage behind it.

The banner must not nudge the visitor towards accepting. If there is an accept button, the option to reject, or to manage cookies by type and purpose, has to be given equal prominence. A grey text link beside a bright accept button fails that test.

Consent cannot be bundled. The guidance says consent may not be bundled for multiple purposes, so a visitor has to be able to accept analytics without also accepting advertising.

Pre-ticked boxes, and sliders that start in the on position, are not consent either. The Court of Justice of the European Union settled that in Planet49 (C-673/17) on 1 October 2019, holding that a box the user has to untick in order to refuse does not produce valid consent.

These are not theoretical failings. When the DPC examined websites across media, retail, insurance, sport and the public sector between August and December 2019, about two thirds of the 38 organisations that responded relied on implied consent, and 10 of them (26%) used pre-ticked boxes. Its report, dated 6 April 2020, also found cookies set as soon as a page loaded, no option to reject all cookies, and consent bundled across purposes.

How do I keep it compliant, and prove it?

A consent setup describes the site on the day it was configured. Plugin updates, theme changes and new integrations change what the site loads without touching the banner, so a site that passed the private window test in spring can fail it by autumn.

The answer is a routine rather than a project. Re-run the test after any significant change to the site, and at least once a quarter, and give one named person the job of doing it.

Keep a record as you go. Where processing relies on consent, Article 7(1) of the GDPR requires the controller to be able to demonstrate that consent was given. In practice that means consent logs showing what each visitor was shown and what they chose, a dated history of the banner’s wording and settings, and a note of each check and anything it found. A complaint may concern a visit from months earlier, and a banner you cannot reconstruct is a banner you cannot defend.

What are the penalties in Ireland?

This is where most published guidance is wrong, usually by quoting a number that belongs to a different regulation.

Regulation 5 contains no offence clause. Breaching the cookie rule is not itself a criminal offence under the ePrivacy Regulations.

The figures people cite come from elsewhere in the same instrument. The fine of up to €250,000 on indictment belongs to Regulation 4, which is about security breach notification by undertakings. The per-message penalties belong to Regulation 13, which is about unsolicited direct marketing. Neither is about cookies.

What actually happens is that the Data Protection Commission engages, and can serve an enforcement notice requiring you to fix it. Failing without reasonable excuse to comply with that notice is an offence, and Regulation 27(1) makes it liable on summary conviction to a class A fine.

Running alongside that, the cookie is usually processing personal data, and the GDPR applies to that processing on its own terms. That is the exposure worth taking seriously, and it does not depend on the ePrivacy Regulations at all.

Who is liable?

Regulation 25 deals with officers. Where an offence under the Regulations is committed by a body corporate and is proved to have been committed with the consent or connivance of, or attributable to neglect on the part of, an officer of that body, that officer commits a separate offence and can be proceeded against as if they had committed the original one.

Where a company is managed by its members, the same applies to a member acting in a management capacity.

Where to start

Run the private window test today. It costs a minute and it tells you whether you have a problem.

If cookies are being set before consent, find out which script is responsible before changing anything, because the fix depends on whether it is a plugin, a tag manager container or something hard-coded into the theme.

Then fix the ordering rather than the banner. A perfect banner in front of a tag that has already fired changes nothing.

We ran the same check on 100 Irish charity websites, and the results are in our study of how charity websites handle cookie consent.

If you would rather this was somebody’s job, our GDPR and cookie compliance service covers the audit and the ongoing checks.

This article sets out how we read the Regulations and it is not legal advice. Where the position matters, take your own.

Share this article

See exactly how your WordPress site is performing

Get a free HostLogic site audit covering Core Web Vitals, security posture, infrastructure and a maintenance gap analysis. Written report within 3 working days. No obligation, no sales pitch.