Cookies Policy

Our current audit position

As things stand, this site does not intentionally set analytics, advertising or personalisation cookies. Where a category below currently has nothing active, we say so directly rather than listing a cookie that doesn't exist. This matters in the Canada context when considering licensing context and dispute routes.

Essential technical function

Any storage strictly needed for the site to function, such as basic security or load-balancing mechanisms handled at the infrastructure level, may apply regardless of preference, since the site couldn't operate reliably without it. For Canada readers, the practical frame remains licensing context and dispute routes.

Locale handling through the URL

Locale is controlled through the page URL structure rather than a stored cookie preference, so visiting the appropriate address determines the language and regional presentation you see. The Canada comparison keeps licensing context and dispute routes in view.

In-page sorting and comparison tables

Where you reorder or filter a comparison table on a page, that arrangement is held only in the page's temporary state and resets when you reload or revisit, rather than being saved anywhere. This matters in the Canada context when considering licensing context and dispute routes.

Preferences

We don't currently set cookies to remember display preferences across visits. If that changes in future, this page will be updated to describe the specific preference stored and its purpose. For the Canada audience, that distinction supports licensing context and dispute routes.

Analytics

No analytics cookies are intentionally set by this site at present. We haven't deployed a measurement or tracking script that stores an identifier in your browser for analytics purposes. In the Canada context, that point is read alongside licensing context and dispute routes.

Advertising and affiliate cookies

No advertising or personalisation cookies are intentionally set here. Our internal /go/ redirect path, used to organise links to casino operators, does not itself require or set a marketing cookie to function. It's a routing mechanism, not a tracking mechanism. The local reading for Canada gives priority to licensing context and dispute routes.

Browser-only forms don't upload

Contact and correction forms on this site run locally in your browser as static demonstrations. They don't upload files or silently transmit data in the background, and they don't rely on cookies to function. For Canada comparison purposes, the reference point is licensing context and dispute routes.

Embedded third-party content

If a page embeds third-party content, such as a video player, that provider may set its own cookies once the embed is actively loaded or interacted with, under its own separate policy. We aim to keep such embeds to a minimum. The local reading for Canada gives priority to licensing context and dispute routes.

Local and session storage

Beyond cookies, a browser's own local or session storage may be used for short-lived, functional purposes like remembering a form draft during your current visit. This data typically stays on your device and isn't transmitted to us. The Canada page weighs that detail against licensing context and dispute routes.

Destination sites have their own policies

Once you follow a link through to a casino operator's own website, whatever cookies or tracking that operator uses are governed entirely by their own cookie and privacy policies, not this one. The editorial context for Canada places this detail beside licensing context and dispute routes.

Consent before any future optional category

If we introduce analytics, advertising or personalisation cookies in future, we intend to seek appropriate consent before those categories are set, and to update this page to describe them accurately rather than folding them in silently. For the Canada audience, that distinction supports licensing context and dispute routes.

Equal choice to accept or decline

Where any optional cookie category is introduced, our intention is to offer an equally accessible way to decline it as to accept it, rather than making rejection harder to find or use than acceptance. Its relevance to Canada is considered through licensing context and dispute routes.

Withdrawing consent later

If an optional category is ever introduced with a consent mechanism, you'll be able to withdraw that consent afterwards through the same or an equivalent control, and doing so will be honoured going forward. The Canada comparison keeps licensing context and dispute routes in view.

Controlling cookies through your browser

Independently of anything this site does, your browser lets you view, block or delete cookies from any site, including this one, through its own settings. Blocking cookies broadly may affect how some third-party embeds or destination sites behave. For Canada comparison purposes, the reference point is licensing context and dispute routes.

How this policy is reviewed and updated

This page is reviewed as part of routine site audits and updated whenever what's actually deployed on the site changes, so the categories described here should reflect current practice rather than a static assumption made at launch. For Canada comparison purposes, the reference point is licensing context and dispute routes.

Questions about cookies here

The table below this page lists the specific categories currently in scope for this site. If anything here is unclear, you can reach the editorial team through the contact page. The practical emphasis for Canada stays on licensing context and dispute routes.

Current category audit