Analytics & privacy

We use limited first-party analytics to understand whether this page is useful and which listed offers visitors choose to view.

What we record

• Page views and a random, short-lived session identifier.
• The casino offer clicked and whether the click came from the card background, its logo or its action button.
• A random click reference shared with the affiliate platform so a registration or first-deposit postback can be matched to the original click.
• The registration or deposit event, optional affiliate partner and event references, any player deposit amount reported by the affiliate platform, and any affiliate payout or revenue value reported with that event.
• A limited diagnostic record for each postback attempt, including when it arrived, its result and reason, request method and content type, recognized non-secret fields, country, Cloudflare request reference and a daily rotating source fingerprint.
• The referring website’s hostname, when the browser provides one.
• Campaign tags such as UTM source, medium, campaign, campaign ID and creative, when present.
• The advertising platform name and, for up to 30 days, the exact recognized advertising click tag when one is present.
• Coarse navigation context supplied by the browser, such as whether a visit was browser initiated or arrived from another site.
• The country and province or region code supplied by Cloudflare’s network.
• Broad device and browser categories derived from the user-agent, such as mobile and Safari.
• When exact-detail collection is enabled, an encrypted first-touch request detail kept for up to 30 days: the IP address supplied by Cloudflare, bounded full user-agent, accepted languages, safe browser client hints, Cloudflare request reference, landing path, recognized marketing URL parameters, and a sanitized referring origin and marketing query.

Data minimization

We do not collect cookie or authorization-header contents, URL fragments, city, postal code, precise location, casino-account details, or the underlying payment method or banking information in traffic analytics. URL parameters are bounded and allowlisted: unknown fields are stored only as redacted markers, and recognized marketing values receive pattern-based filtering for email addresses, international phone numbers, Luhn-valid card numbers, IBAN-like values, and labeled identity, credential or payment fields. Campaign operators must not place names, contact details, account data, credentials or other personal information in tracking URLs because arbitrary free text cannot be classified with certainty. Referrer pathnames and fragments, credentials and non-marketing query values are not retained. Postback diagnostics remain separate and do not retain submitted secrets, authorization headers, the complete request URL, query string or body, or arbitrary values from unrecognized fields. A postback may contain a reported deposit amount, affiliate payout, or provider event reference.

Session measurement

A first-party cookie containing a signed random identifier lasts for up to 30 minutes and is used to group activity into an estimated session. It is not an exact count of individual people and is not used for cross-site advertising.

Affiliate links

Offer links first pass through a route on this site so the click can be counted, then redirect to the relevant affiliate URL with a random click reference. The affiliate platform may later return that reference with a registration or first-deposit event. We may receive a commission if you proceed through one of those links. This does not change the offer displayed to you.

Storage and access

Coarse analytics events and normalized campaign fields are stored in a Cloudflare D1 database and are normally deleted once they are older than 13 months during daily maintenance. When exact-detail collection is enabled, exact request details are encrypted with a separate server-side key, restricted to the authenticated site administrator, bounded to 4 KiB before encryption, normally deleted after 30 days, and capped at 25,000 records. Details were not collected before this feature was enabled and cannot be added retroactively. Postback-attempt diagnostics are separately deleted after 30 days and capped at 50,000 records. During unusually high or abusive postback volume, additional attempts are represented by a limited aggregate record rather than storing each request separately. Coarse no-referrer combinations are displayed only after at least three sessions share the same group.