Cookie consent in Ireland: what the DPC expects in 2026

Hephaestus Technology7 min read

Cookie consent in Ireland means you must get a user's clear, affirmative consent before setting any cookie or similar tracker that is not strictly necessary, and the Data Protection Commission (DPC) expects banners that do not nudge, offer an equally prominent way to reject, and are refreshed at least every six months. These rules come from Regulation 5 of the Irish ePrivacy Regulations (S.I. No. 336 of 2011) read with the GDPR. Proposed EU changes under the Digital Omnibus are still being negotiated, so the current rules apply today.

Key takeaways

  • Cookie consent in Ireland is governed by Regulation 5 of S.I. No. 336 of 2011, enforced by the DPC, with the consent standard taken from the GDPR.
  • Consent is needed for any non-essential storage or access on a device, including pixels, SDKs and fingerprinting, whether or not personal data is involved.
  • The DPC rejects implied consent, pre-checked boxes and nudging banners, and expects reject or manage options with equal prominence to accept.
  • Analytics cookies need consent, though the DPC says first-party analytics are unlikely to be an enforcement priority.
  • The Digital Omnibus may simplify banners, but the Council only adopted its position in October 2026 and the rules are not expected to change before 2027.

The law is Regulation 5 of the European Communities (Electronic Communications Networks and Services) (Privacy and Electronic Communications) Regulations 2011, the ePrivacy Regulations. Regulation 5(3) says you must not store information on, or access information already stored on, a user's device unless the user has given consent and has been given clear and comprehensive information about the purposes.

The DPC's guidance note on cookies and other tracking technologies, last updated in April 2020, explains that the ePrivacy rules apply first, and the GDPR applies as well where cookies involve personal data. Crucially, consent is required whether or not the information stored is personal data. Consent must meet the GDPR standard in Article 4(11): freely given, specific, informed and unambiguous, given by a clear affirmative action.

Every cookie needs consent unless it fits one of two narrow exemptions in Regulation 5(5).

Type Consent needed? DPC example
Communications exemption No A load-balancing cookie that only identifies a server endpoint
Strictly necessary for a service the user requested No Session cookies for a shopping basket; language or country preference
Analytics (first or third party) Yes Visitor counts and page views
Advertising, conversion tracking, retargeting Yes Marketing pixels
Chat widget cookies Yes, until the user opens the chat Cookies loaded before the person asks to use a chatbot
Long-lived preference cookies Usually yes A two-year cookie remembering journey preferences

The rules apply to more than browser cookies. The DPC's guidance names local storage, SDKs, pixel trackers, social "like" buttons and device fingerprinting as covered. If you build a mobile app or connected device, the same consent logic applies to identifiers stored on the device.

On analytics, the DPC is direct: analytics cookies require consent. It adds that first-party analytics used only for aggregated statistics, with clear information and an easy opt-out, are "unlikely" to be a priority for enforcement. That is an enforcement signal, not an exemption. If you want to reduce consent friction, look at our guide to GDPR-friendly product analytics without cookies.

The DPC expects a banner that asks for specific, separate consent and makes refusing as easy as accepting. Based on its guidance note, a compliant banner:

  1. Sets nothing non-essential before consent. Analytics and marketing tags fire only after the user agrees.
  2. Gives equal prominence to refusing. If there is an "Accept" button, there must be an equally prominent button to reject, or to manage cookies by type and purpose on a second layer.
  3. Does not nudge. No bright accept button next to a faint text link for reject.
  4. Does not rely on implied consent. "By continuing to browse you accept cookies" is not permissible, nor are banners that disappear when the user scrolls.
  5. Has no pre-checked boxes or sliders set to on. This follows the CJEU's Planet49 judgment.
  6. Does not bundle purposes. Consent is asked for each purpose, not as part of your terms and conditions.
  7. Links to clear information. Users must be able to see the third parties involved and, per the DPC's FAQ, the names and duration of cookies.
  8. Makes withdrawal as easy as giving consent. A persistent "cookie settings" link in the footer or app menu is the usual approach.

Note the Irish nuance: the DPC requires a reject option or a manage option with equal prominence, so it does not strictly mandate a "Reject all" button on the first layer. Many organisations add one anyway, because it is the clearest way to show refusing is as easy as accepting, and the EDPB's cookie banner taskforce report of January 2023 listed "no reject button on the first layer" as the first of the practices regulators examined.

The DPC says you should ask users to reaffirm their consent no later than six months after storing their consent state. The legislation does not set a period; the DPC reached six months through its own analysis, and a longer period would need to be objectively justified. If you use a consent management platform, keep a record of consent as part of your Article 30 records of processing, and make sure the tool does what it claims.

The cookies themselves should also have proportionate lifespans: a session cookie for a basket should expire when it has served its purpose, not years later.

What changes are coming with the Digital Omnibus?

Changes are proposed but not yet law. On 19 November 2025 the European Commission proposed a digital omnibus that would reduce how often cookie banners appear, allow one-click consent and let users save preferences through browser settings.

According to a Heuking update of 23 October 2026, the Council adopted its position on 21 October 2026, the European Parliament had not yet adopted its own, and entry into force is not expected before 2027. The Council's text reportedly drops the browser-signal obligation, adds exemptions for aggregated audience measurement and contextual advertising, and shortens the wait before re-asking after a refusal from six to four months. These details could still change in negotiations, so do not redesign your banner around them yet.

The main risks are DPC enforcement, complaints and knock-on GDPR issues. The DPC examined the websites of 40 controllers across media, retail, food ordering, insurance, sport and the public sector between August and December 2019, and published its current guidance alongside the results. Where tracking data is personal data, the processing that follows is also subject to the GDPR, including its fines. Marketing tags that send data to third countries also raise transfer questions. Cookies are one item on a broader list; our GDPR checklist for a new SaaS product covers the rest.

This article is general information, not legal advice. If your business model depends heavily on tracking or advertising, get specialist advice.

Frequently asked questions

Do I need a cookie banner if I only use Google Analytics?

Yes. The DPC states that analytics cookies require consent, including first-party analytics. It considers first-party, aggregated analytics a low enforcement priority, but that does not remove the legal requirement.

Must the "Reject all" button be on the first layer in Ireland?

The DPC requires equal prominence for an option to reject or to manage cookies, so a first-layer "Reject all" is not strictly mandated by its guidance. A first-layer reject button is the safest design and is what many regulators across the EU look for.

Can I use a cookie wall that blocks access unless users accept?

The DPC's guidance requires consent to be freely given and not bundled with terms and conditions, which makes a blanket cookie wall hard to justify. If you are considering one, for example with a paid alternative, take legal advice first.

How often should I ask users for cookie consent again?

The DPC recommends asking users to reaffirm consent no later than six months after storing their choice. A longer period would need an objective, case-by-case justification.

Do cookie rules apply to mobile apps?

Yes. The ePrivacy rules apply to storing or accessing information on any terminal equipment, and the DPC lists SDKs and device identifiers among covered technologies. Apps need the same prior consent for non-essential tracking.

Need a cookie setup or analytics approach that respects the DPC's expectations? Book a free 30-minute call.

Cover photo by Marcial Comeron on Pexels.

Hephaestus Technology

We help founders and businesses validate, build and launch products across software, AI and hardware, from offices in Ho Chi Minh City, Dublin and Delaware. See how we work.

Tell us what
you're building.

A free 30-minute call. You'll get an honest view of the idea, the risks we see and what we'd do first, whether or not we end up working together.