Privacy Policy

This policy explains what information CasinoFinder (“we”, “us”) collects when you use casinofinderonline.com, how we use it and the choices you have. It is written to match how the site is built, so the short version is accurate:

• No accounts. You cannot register, log in or store anything with us on a server. Your preferences live in your own browser.
• No advertising cookies. We do not run ad networks or sell data.
• Third-party analytics only with consent. Where Google Analytics 4 or Microsoft Clarity is enabled, it loads only after you accept it in the consent prompt.
• A minimal first-party event log. We record a fixed list of product events (for example “affiliate link clicked from the review sidebar”) without cookies, identifiers, IP addresses or browser details.

The data controller is Not yet provided — legal entity name. Contact details are at the end of this page.

We collect information in four ways, described in detail in the sections that follow:

1. Stored in your browser — preferences such as your compare list, saved casinos and Finder answers, kept in local storage and one cookie. This data never leaves your device unless you take an action that sends it (for example opening a shareable Finder results link).
2. Sent by your browser automatically — the technical information every web server receives with a request: IP address, browser and device type (user agent), the page you came from (referrer). Our application does not store the IP address or the user agent, and keeps at most the path of the page on our own site a request came from — never a full referring URL. The IP address is used, in reduced form, only for rate limiting (see Security). Whether the hosting platform keeps its own access logs is covered under Sharing.
3. Product events — cookie-less events sent to our own endpoint (/api/track) from a fixed allowlist, such as filters applied, comparisons opened or affiliate links clicked.
4. Information you give us — your name, email address, subject and message when you use the contact form.

We do not collect payment details, government identifiers, precise location or any data about your gambling activity on other sites.

The site uses your browser's local storage for preferences. Local storage is not sent to our servers with requests, cannot be read by other websites, and can be cleared at any time from your browser settings (usually under “site data”). The keys we use:

First-party product events (no consent required)

To understand which tools people find useful we record product events from our own pages to our own endpoint. Only events on a fixed allowlist are accepted, and only with the parameters the allowlist names; anything else is discarded before it is recorded. A recorded event contains:

• the event name (for example affiliate_click, filter_applied, finder_complete);
• its allowed parameters — identifiers such as a casino slug, short labels such as a placement name, counts, true/false values, or (when you change your location) the two-letter country code you chose. Free text is never accepted;
• the path of the page the event came from, with any query string removed;
• a timestamp; and
• a two-letter country code taken from the country header our hosting platform supplies, or nothing if it is absent.

What is not recorded: your IP address, your user agent, the referring URL, any cookie or persistent identifier, and anything you type. Casino Finder events are deliberately coarse — they record how many steps were completed and how many results were shown, never your answers. Search events record the number of results and the length of the query, not the query itself.

These events cannot be used to build a profile of you across visits. You can stop your browser sending them by blocking requests to /api/track with a content blocker.

Google Analytics 4 and Microsoft Clarity (consent required)

Where enabled, and only with your consent, we use Google Analytics 4 to measure traffic and Microsoft Clarity to understand how pages are used (aggregated click and scroll behaviour). Google Analytics is configured with IP anonymisation. Both providers act as our processors and are governed by their own privacy terms. You can change your mind at any time by clearing the cf:consent:v1 key from local storage, after which the consent prompt appears again.

Outbound casino links go through /go/<casino>. When you click one we record an affiliate_click event containing the casino, the page and placement the click came from, an optional campaign label, the offer it relates to (if any), the path of the page on our site you clicked from, and the two-letter country code described above. As with every event, no IP address, user agent, referring URL or destination URL is stored.

Where an operator's affiliate network supports it, the redirect passes a placement label (for example “review page, sidebar”) to the operator so the referral can be attributed to a page — never an identifier for you. The redirect sets no cookies. Once you arrive at the casino, that site's privacy policy applies. See our affiliate disclosure for how commissions work.

When you submit the contact form we receive your name, email address, chosen subject and message. The message is delivered to our inbox as an email through a transactional email provider; your name, email address and message exist only in that email and in the request to the provider. They are not written to our logs — the only record our application keeps of a submission is the subject category, the time and whether delivery succeeded.

We use this information solely to respond to you and to act on corrections. The form includes a hidden anti-spam field; submissions that fill it are discarded without being sent. Submissions are rate-limited as described under Security. While no email provider is configured the form is disabled and shows a notice instead of accepting messages.

• To operate the site and remember your preferences on your device.
• To pre-fill your country for availability checks, which you can override.
• To measure which tools and placements are useful and improve them.
• To attribute referrals to casinos by placement so our commercial reporting is accurate.
• To protect the site from abuse, including rate limiting and spam filtering.
• To respond to messages, corrections and legal requests.

We do not use your data for advertising, profiling, automated decision-making with legal effects, or sale to third parties.

We share data only with providers needed to run the site, each acting on our instructions:

• Hosting — the platform that serves the site and receives our event log as application output. It may keep its own access logs for security and operations under its own terms.
• Google Analytics 4 and Microsoft Clarity — only where enabled and only after consent, as described above.
• Transactional email provider — to deliver contact form messages to our inbox.

We may also disclose information where required by law or to protect our rights, and in connection with a merger or sale of the business, subject to this policy. Casinos you visit through our links are independent controllers; we do not share your contact form data with them.

Where data protection law requires a legal basis (for example in the EU/EEA and the UK), we rely on:

• Consent for third-party analytics cookies and scripts.
• Legitimate interests for first-party product events, rate limiting and affiliate attribution — interests we consider proportionate because the data is minimal, cookie-less, contains no IP address or identifier and is not used to profile you.
• Performance of a contract or steps at your request for responding to your messages.
• Legal obligation where we must retain or disclose information.

Depending on where you live you may have the right to access, correct, delete or export your personal data, to object to or restrict processing, and to withdraw consent. In practice:

• Preferences — clear the site's local storage and cookies in your browser; everything we hold on your device is gone.
• Analytics consent — clear cf:consent:v1 to be asked again, or use your browser or a content blocker to block the analytics domains.
• Contact messages — email us at Not yet provided — privacy contact address with enough detail to identify the records (for example the email address you wrote from). Because the event log contains no identifiers, there is nothing in it we can link to you.

You also have the right to complain to your local data protection authority. We would appreciate the chance to address your concern first.

CasinoFinder is intended for adults of legal gambling age in their jurisdiction (18+ at minimum, higher in some countries). We do not knowingly collect information from anyone under that age. If you believe a minor has sent us information, contact us and we will delete it.

The site is served over HTTPS with security headers that restrict framing and content sniffing. Endpoints that accept input validate and size-limit every request. To limit abuse, each request to those endpoints is counted against a salted hash of the client address: the address itself is never stored, the salt is either derived from our rate-limiter credentials or generated afresh each time the application starts, and the counters live only as long as the limiting window needs them. The hash is not written to the event log. Outbound redirects resolve their destination from our own content, never from user input.

No system is perfectly secure, and we cannot guarantee the security of information transmitted over the internet, but we take reasonable measures appropriate to the small amount of data we hold.

We will update this page when our practices change and update the effective date at the top. Material changes will be highlighted on this page for a reasonable period. Continued use of the site after a change means you accept the updated policy.

Privacy questions and requests: Not yet provided — privacy contact address, or use the contact form.

Postal address: Not yet provided — legal entity name, Not yet provided — registered address.