Cookie Policy
This page explains exactly which cookies and similar technologies are set on this website, who sets them, what each one does, and how long it stays in your browser. It is written to sit alongside the Privacy Policy, which describes the broader picture of how visitor information is handled. If you only want to know what is in your browser right now and how to remove it, the cookie table further down is the practical part of this page.
1. What cookies are
A cookie is a small text file that a website asks your browser to store on your device. The next time your browser sends a request to that website, it includes the cookie’s contents. That mechanism lets a site recognise repeat visitors, remember preferences (such as language), keep you logged in across pages, and measure traffic in aggregate. Cookies cannot read other files on your device, run programs, or access information that your browser does not explicitly send back. They are simple key-value records, not active code.
Two technical distinctions matter for the rest of this page. First, cookies can be first-party (set by the domain you are visiting) or third-party (set by another domain whose script the page loads). Second, cookies can be session cookies (deleted when you close the browser) or persistent cookies (kept for a set period). Beyond cookies, similar functions can be performed by local storage in your browser and by tracking pixels embedded in pages; where this site uses any of those, it is described below.
2. Categories of cookies used
Every cookie on this site falls into one of four categories. The categories are explained briefly below; the table that follows lists each cookie individually, so you can see exactly what is set and why.
2.1. Strictly necessary
These cookies are required for the site to load and behave correctly. They include the cookie that records your response to the cookie banner itself, the bot-management cookie used by the security layer in front of the site, and any cookie needed to keep navigation consistent across pages. They cannot be turned off through the cookie banner because turning them off would make the site fail to function. They do not collect information for marketing or profiling.
2.2. Analytics
These cookies help us understand how the site is used in aggregate — for example, which guides are read most, which pages have high bounce rates, and what proportion of visitors arrive on mobile devices. The information is aggregated. It does not allow the site to identify you personally. Where these cookies are configured, IP anonymisation is enabled so that the last octet of your IP address is removed before storage. You can decline analytics cookies through the cookie banner; if you do, no analytics record is created for your visit.
2.3. Functional
These remember choices you have made on the site, such as a preference for English language or any UI option that benefits from persistence. They are not strictly required for the site to load, but without them you would have to re-make each preference on each visit.
2.4. Marketing — affiliate attribution only
This site does not run a behavioural advertising programme, does not show banners and does not build profiles for retargeting. The only cookies in this category are affiliate-attribution cookies set when you click an outbound link to a casino operator. The cookie is set by the affiliate network used by that operator. It contains a click identifier that lets the operator know the click came from this site, so any commission owed for that referral can be paid. It does not contain your name, contact information or any data about your activity on other sites.
3. Detailed cookie list
The table below lists each cookie that may be set when you load a page on this domain. Some cookies are conditional: an analytics cookie is only set if you accept analytics through the banner; an affiliate cookie is only set if you click an outbound “Visit Casino” link. Conditional cookies are flagged in the “When set” column.
| Cookie | Category | Provider | Purpose | Lifetime | When set |
|---|---|---|---|---|---|
cookieconsent_status | Strictly necessary | This site | Records your selection in the cookie banner so it does not reappear on every page. | 12 months | On first visit, after you make a selection. |
session_id | Strictly necessary | This site | Maintains continuity across page requests within a single visit. | Until you close the browser | On every visit. |
cf_clearance | Strictly necessary | Cloudflare | Confirms that your request passed the bot-management check; protects against automated abuse. | 30 minutes | When the security layer challenges a request. |
__cf_bm | Strictly necessary | Cloudflare | Distinguishes legitimate visitors from automated scrapers, allowing the site to remain accessible to genuine traffic. | 30 minutes | On every visit. |
_ga | Analytics | Google Analytics 4 | Generates an anonymous identifier used to count unique visitors over time. | 2 years | Only if analytics are accepted. |
_ga_XXXXXXXX | Analytics | Google Analytics 4 | Stores GA4 session state for the property identifier shown in the suffix. | 2 years | Only if analytics are accepted. |
lang | Functional | This site | Records the chosen interface language so it persists between visits. | 12 months | If language is changed manually. |
btag | Marketing (attribution) | Affiliate network | Identifies the source of a click on an outbound “Visit Casino” button so any commission owed for the referral can be paid. | 30–90 days | Only when you click an outbound affiliate link. |
clickid | Marketing (attribution) | Affiliate network | Stores a unique identifier for the click, used by the operator to confirm a referral. | 30–60 days | Only when you click an outbound affiliate link. |
affid | Marketing (attribution) | Affiliate network | Identifies which affiliate site the click originated from. Does not contain personal data. | 30–90 days | Only when you click an outbound affiliate link. |
NID | Functional | Stores Google service preferences when Google-served resources (fonts, reCAPTCHA) load on the page. | 6 months | If a Google-served resource is requested. | |
1P_JAR | Functional | Used by Google to collect aggregate statistics about how its services are used; only present if a Google resource is loaded. | 30 days | If a Google-served resource is requested. |
4. Third-party services explained
The cookies above come from a small number of third-party services. Each of those services has its own privacy practices, summarised here.
4.1. Cloudflare
Cloudflare provides the content delivery network and bot-management layer for this site. Its cookies (cf_clearance and __cf_bm) are technical: they confirm that an incoming request comes from a legitimate browser rather than an automated scraper or attack tool. Without them the site would either be slower for everyone or open to abuse. Cloudflare’s privacy notice is available at cloudflare.com/privacypolicy/.
4.2. Google Analytics 4
Where analytics are configured, Google Analytics 4 receives aggregate visit information. IP anonymisation is enabled, which means the last octet of your IP address is dropped before any record is stored. Demographic information, where available, is exposed only as aggregated bands (age range, broad region) and is not connected to identifiable visitors. You can opt out of Google Analytics across all websites by installing the official browser add-on at tools.google.com/dlpage/gaoptout. Google’s privacy notice is at policies.google.com/privacy.
4.3. Affiliate networks
When you click an outbound link from a casino review on this site to the casino itself, the affiliate network used by that operator may set a tracking cookie on the operator’s domain. The cookie records that the click came from this site, the time of the click, and a numeric identifier. It does not contain your name, your email, your gambling history, or any other personal information. It exists so the operator can pay any commission owed for the referral. Each affiliate network publishes its own privacy notice on its own domain; the names of the networks are listed in the Affiliate Disclosure.
5. Managing cookies in your browser
You can change your cookie preferences at any time through the cookie banner on this site or by clearing cookies in your browser. Browser-level controls let you block cookies entirely, allow first-party only, or delete what is already stored. The links below are official documentation pages.
- Google Chrome. Settings → Privacy and security → Cookies and other site data. From there, choose to block third-party cookies, block all cookies, or allow specific sites only. Documentation: support.google.com/chrome/answer/95647.
- Mozilla Firefox. Settings → Privacy & Security → Cookies and Site Data. Firefox offers Standard, Strict and Custom modes; Strict blocks most third-party cookies by default. Documentation: support.mozilla.org.
- Apple Safari. Safari → Settings → Privacy. By default, Safari blocks cross-site tracking cookies. You can also use “Manage Website Data” to remove cookies for specific domains. Documentation: support.apple.com/guide/safari/manage-cookies-sfri11471.
- Microsoft Edge. Settings → Privacy, search and services → Tracking prevention & Cookies. Edge offers Basic, Balanced and Strict tracking prevention. Documentation: support.microsoft.com/microsoft-edge/manage-cookies.
- Mobile browsers. On iOS, open Settings → Safari → Privacy & Security to manage cross-site tracking and block all cookies. On Android, open the menu in Chrome → Settings → Site settings → Cookies.
6. What happens if you decline cookies
If strictly necessary cookies are blocked, the bot-management layer in front of the site may show a verification challenge or, in the case of repeated requests, throttle access; ordinary reading is usually still possible but the experience may degrade. If analytics cookies are declined, no analytics record is created for your visit; this has no practical effect on what you see. If functional cookies are declined, language and similar preferences are not remembered between visits. If marketing-attribution cookies are declined, you can still click outbound links to casinos, but no commission is recorded for the referral — your experience is not affected, only ours.
7. Updates to this policy
This page is updated whenever the set of cookies on the site changes. The date at the top of the page shows when the most recent update was made. Material changes are highlighted prominently. Minor changes (a renamed cookie, a corrected lifetime) are reflected in the table without a separate announcement. For broader information about how visitor data is handled on this site, see the Privacy Policy.