comparechoicelab.com

Last reviewed: April 2026 · Applies to users in Ireland & the EU
This page explains how cookies are used on this platform, why they are needed, and what they do while you browse.
It focuses on the essentials — no unnecessary detail, just a clear view of how things work and what you can control.

A quick word on what cookies actually are

A cookie is a small text file that a platform places on your device when you visit. It doesn’t do anything on its own — it just stores a modest amount of information that can be read back when you return or navigate around. Depending on the type, it either disappears when you close your browser or persists for a defined period.
Beyond cookies themselves, similar technologies exist — things like local storage, session tokens, or small tracking pixels — that work in comparable ways. Where any of these are used here, they fall under the same principles described on this page.

Why these technologies are present at all

CompareChoiceLab.com is a read-only editorial environment. There are no accounts, no checkout flows, and nothing requiring a user to identify themselves. That limits significantly the reasons cookies would be needed in the first place.
The ones that do exist serve three purposes: keeping pages stable and functional as you navigate, holding onto lightweight preferences so the platform behaves consistently, and gathering aggregate data about how content is being used overall. That last one helps inform decisions about what’s working and what isn’t — not to profile individuals, but to understand general patterns across the platform as a whole.
Nothing here is in place to follow you around the web, serve targeted content, or build any kind of profile tied to you as a person.

The categories in use — and what each one does

There are three types of cookies or similar technologies that may be active when you visit. Each has a specific, limited purpose. Essential
Core functionality
These are the ones the platform genuinely cannot operate without. They handle things like maintaining a consistent session as you move between pages, enabling the cookie consent mechanism itself, and ensuring the basic structure of the environment loads correctly. Because they’re tied to fundamental operation, they can’t be switched off while still using the platform.
Functional
Lightweight preferences
Where applicable, functional cookies may remember small choices — such as a dismissed notice or a display preference — so you don’t encounter the same prompts repeatedly. They’re session-level in most cases, and none of them are connected to any personal identifier.
Analytics
Usage patterns
Analytics tools may be used to understand which content is being read, how long visitors generally stay, what devices are most common, and where people typically navigate from. The data involved is aggregated — meaning it reflects trends across many visitors rather than the behaviour of any one individual. No names, email addresses, or persistent identifiers are collected through this process.
The comparison model relies on affiliate arrangements with third-party platforms — not on behavioural ad targeting.

No personal profiles — and no intention to build any

Even where cookies are active, they aren’t being used to piece together a picture of who you are. The analytics data collected here is the kind that tells you “most visitors arrive from mobile” or “this comparison page is read more than that one” — not the kind that identifies or follows individuals.
There is no cross-device tracking, no fingerprinting, and no mechanism connecting your behaviour here to anything you do elsewhere online. The platform doesn’t need that information to function, and collecting it would serve no genuine editorial purpose.

Third-party tools and where they come in

Some of the technology used here — analytics in particular — may be provided by third-party services rather than built entirely in-house. When that’s the case, those providers operate under their own terms and privacy policies, which are separate from this one.
Any third-party tool used in this context has been chosen with data minimisation in mind. That said, once data reaches an external provider’s systems, the practices governing it there are theirs, not ours. If you’d like to understand how a specific tool handles information, their documentation is the authoritative source.

Your options and how to use them

If a cookie consent banner is shown when you first arrive, it will give you the opportunity to accept or decline non-essential cookies before they’re set. Essential cookies don’t require consent — they’re active regardless, because the platform couldn’t function without them.
Beyond that, every major browser includes built-in controls for managing cookies. Depending on which one you use, you can typically:

View and delete cookies that have already been stored on your device
Block all cookies from loading, or only block those from third-party sources
Set exceptions for specific platforms you trust
Clear everything automatically when the browser session ends

These settings are usually found under Privacy, Security, or a similar heading within your browser’s preferences. Making changes there will take effect across all the platforms you visit, not just this one — so it’s worth considering the broader implications before adjusting anything significant.
Declining analytics cookies won’t affect what you can read or access here. The content remains fully available regardless of what you choose.

The bigger picture on data handling

Cookies are one part of a broader conversation about how data flows through any digital platform. The full account of what CompareChoiceLab.com collects (and what it doesn’t), how technical data is processed, how outbound links work, and what rights apply under Irish and EU law is covered separately.