Cookies and browser storage, item by item
Until you answer the cookie box, nothing is written to your browser by this site itself; the Cloudflare security cookies below come from the layer in front of it. After you answer, one small note records the answer; anything from Google needs a yes from you first.
The note that remembers your answer
When you press “Allow both”, “Only what is needed” or “Keep this choice”, the site writes one entry to your browser’s local storage under the name fp-consent-kept. It holds four things: a version number, a yes or no for visit counting, a yes or no for advert measurement, and the time you answered. It stays in your browser rather than travelling to the server with each page, and it names nobody.
The entry lasts 365 days; after that the box asks again. There is no switch for it, because without it the site could not respect your answer. The UK’s Privacy and Electronic Communications Regulations let a site keep what is strictly necessary in this way; anything else waits for consent. In a private window that blocks storage, the answer holds for the page in front of you only and the box returns on the next one.
Everything that can be stored, in one table
The site sets no cookie of its own. Cloudflare, which protects the site, may set a security cookie when it checks for automated traffic. The Google cookies appear only after a yes, and only once the tags are switched on.
| Name | What it is | Placed by | How long it lasts | Kind |
|---|---|---|---|---|
| fp-consent-kept | Local storage entry: your answer to the cookie box | This site | 365 days | Needed |
| __cf_bm | Cookie: tells people from automated traffic | Cloudflare | up to 30 minutes | Needed |
| cf_clearance | Cookie: shows a security check was passed | Cloudflare, after a check | 30 minutes by default | Needed |
| _ga | Cookie: random identifier that lets visits be counted | Google Analytics 4 | up to 2 years | Visit counting |
| _ga_<ID> | Cookie: keeps the state of a visit; <ID> is the site’s measurement ID | Google Analytics 4 | up to 2 years | Visit counting |
| _gcl_au | Cookie: links an arrival to one of the site’s adverts | Google Ads | up to 90 days | Advert measurement |
While its tag runs, Google may also read or set cookies on its own domains; those follow Google’s rules. What Google receives, and why, is set out in the data notice.
When the Google tags would load
Google Analytics 4 and Google Ads are not connected today, so nothing from Google loads whatever you choose. If they are added later, they will start only after your yes, and only once the tags are switched on. Each page first tells Google Consent Mode v2 that all analytics and advert storage is “denied”; the Google tag is fetched only after you allow visit counting, advert measurement, or both.
If you answer no, or later take back a yes, the site deletes the _ga and _gcl cookies it can reach and tells Google that storage is denied again. With JavaScript turned off, the box never appears, nothing is stored and no Google tag can load.
Changing your answer later
Three steps are enough, on any page of the site:
- Select “Change cookie choice” in the footer. The box opens with the list of storage kinds and your current switches.
- Turn visit counting and advert measurement on or off, or use “Allow both” or “Only what is needed”.
- Press “Keep this choice” if you used the switches. The new answer takes effect at once and replaces the old note.
Without JavaScript, the same link brings you to this page. Clearing this site’s data in your browser removes the note as well, and the box will ask again on your next visit.
Cookies set by the casinos
A “Visit site” link on a clause sheet takes you to a casino’s own site, which sets its own cookies under its own notice. Nothing on this site can switch those on or off. The way the links are paid for is described under funding; this page was last updated on 14 November 2026.
Page revised