Cookies, explained without the jargon
In technical terms a cookie is nothing more than a tiny plain-text file that a website drops onto your device when you land on it. That file lets the site keep a few small facts in mind as you move from page to page or come back another day: things like whether you've already ticked away a banner, or which referring link brought you across. Cookies aren't executable code and they can't smuggle malware, and each one only stores a short line of text that on its own means nothing personal about you. Websites also lean on close cousins such as browser local storage and tiny tracking pixels, and for readability we'll bundle all of those together as "cookies" for the rest of this page.
- Cookies, explained without the jargon
- Why we set cookies at all
- The four categories in use here
- The analytics tools we actually run
- Cookies dropped by third parties
- Controlling cookies inside your browser
- Your choice, your consent
- How to get in touch
- Updates to this policy
Why we set cookies at all
Remember: CasinoClaude is a review outlet, not a casino. Nobody registers a player account through this site and no bets are placed here, so the amount of data we need is a fraction of what an operator would ever collect. The cookies that remain do three straightforward things: they keep the site functioning as you jump between pages, they hold on to small preferences so your visit stays consistent, and they let us measure, in aggregate only, which guides visitors are actually reading. That final data point drives our decisions about what to update, what to expand, and what to retire, and at no point are we attempting to identify you personally.
The four categories in use here
The table below places every cookie we touch into one of four industry-standard groups. Essential cookies always fire because without them the site simply cannot behave properly. The remaining three categories are optional and never load until you've given explicit consent.
| Category | Purpose | Examples |
|---|---|---|
| Essential | Handles security and lets the pages render correctly as you click around. These cannot be disabled. | Session identifier, stored consent preference, load-balancer token |
| Preferences | Holds on to little UI choices so the site is arranged the way you left it last time. | Selected country or market, colour theme, banners you've already closed |
| Analytics | Counts visits in aggregate to show us what's landing well and what needs a rewrite. | Microsoft Clarity, Matomo |
| Marketing | Attributes a click-through to us when you visit a casino via our links, which is where our commissions come from. | Affiliate tracking set by the destination casino or its network |
The analytics tools we actually run
Only two analytics platforms are wired into casinoclaude.fyi, and neither is loaded until after you have opted in. Microsoft Clarity records aggregated, anonymised behaviour, things like scroll depth and click points, which helps us spot layouts that confuse people or sections that seem to break. Matomo tallies page views, rough geographical region and device category so that we can read long-term traffic trends. Neither service is building an advertising profile against you, and both report back to us as pooled numbers rather than anything traceable to one person. Would rather not count? Turning down analytics cookies switches both off, and the rest of the site continues to work exactly as intended.
Cookies dropped by third parties
A few of the cookies you may pick up while browsing here are placed by other companies rather than us. The most common example: click one of our outbound casino links and the destination operator, or the affiliate network handling that link, may set its own cookie so it can log that the visit originated with CasinoClaude. That mechanism is how we get paid a referral, it costs you nothing on top of your usual spend, and it never nudges our rating. From the moment you land on someone else's site their own cookie and privacy rules take over, and those are outside our control. Affiliate cookies of this variety typically stick around for somewhere in the region of 30 to 90 days.
Controlling cookies inside your browser
In addition to whatever choice you make in our consent banner, every mainstream browser gives you direct control over cookies, from reviewing which ones exist to deleting them or blocking new ones. Menu labels shift slightly between versions, but these are the usual starting points:
- Chrome: Settings → Privacy and security → Third-party cookies (or Cookies and site data).
- Firefox: Settings → Privacy & Security → Cookies and Site Data.
- Safari: Settings → Safari → Advanced → Website Data on iPhone or iPad (on macOS, Safari → Settings → Privacy).
- Edge: Settings → Cookies and site permissions → Manage and delete cookies and site data.
Another option is browsing in a private or incognito window, which usually clears most cookies as soon as you close it. One thing to keep in mind: blocking cookies flagged as essential may prevent parts of the site, such as the consent banner itself or your saved theme, from behaving normally.
Your choice, your consent
The first time you visit we ask whether you're willing to accept cookies that aren't strictly required. Nothing optional runs until you say yes, and if you change your mind later you can reset the whole thing by clearing this site's cookies or tweaking your browser preferences. Essential cookies remain switched on because the site genuinely stops working without them, but preferences, analytics and marketing are entirely down to you.
How to get in touch
If any part of this page leaves you with questions, or you'd like to know what data we currently hold about you, drop us a note via the contact page and we'll happily walk you through it. Broader personal-data topics that go beyond cookies live in our privacy policy.
Updates to this policy
We may need to revisit this text as our own tooling changes, or as the surrounding regulations evolve. When that happens, the last-updated date will move and the revised wording will replace what's here. The version you're currently reading was last refreshed in July 2026.