Privacy Policy

When you load a page on this site, our hosting provider automatically logs your IP address, the user-agent string of your browser, the URL you requested, and the timestamp of the request. These logs are standard web-server access logs; we do not add our own tracking to them. In addition, if you fill in the contact form, we receive whatever you type into the form — typically your email address, the URL of the page you have a question about, and your message. We do not use cookies for analytics or advertising. The only cookies this site sets are a session cookie used by the comment form to remember your name across page reloads (expires when you close the browser) and a one-year consent cookie that records whether you accepted the age-gate on first visit.

We deliberately do not deploy third-party analytics such as Google Analytics or any Meta pixel. The decision is not driven by legal necessity — those tools can be configured to be lawful under GDPR with the right contractual plumbing — but by a simple cost/benefit view: the editorial team does not need the data granular enough to justify what it would cost readers in extra round-trips to third-party domains. The hosting provider's aggregated request counts give us enough signal to see which pages are being read and which are returning errors.

This site is hosted on Cloudflare's edge network. Cloudflare routes requests to whichever data centre is physically closest to your IP address, which may be inside or outside the European Economic Area. Where personal data is transferred outside the EEA, we rely on the European Commission's Standard Contractual Clauses as the transfer mechanism, as published and updated by Cloudflare in its Data Processing Addendum. Email sent to the contact address passes through our mailbox provider, which also operates servers in both the EU and the United States under the same contractual safeguards.

We use access logs only for two purposes: debugging (if a page returns an error, we need to be able to reproduce the request) and security (we block IP ranges that repeatedly hit non-existent pages, which is almost always a bot scan rather than a real reader). Logs are rotated after thirty days and are not analysed to profile individual readers. Contact-form submissions are used solely to reply to your question and to keep a record of corrections we have made to the site. We do not add your email address to any newsletter list unless you explicitly ask us to.

We share data with three categories of third party. First, our infrastructure providers (Cloudflare for the CDN, the hosting company that runs the mail server) see request data as a necessary condition of delivering the service. Second, when you click an outbound CTA that takes you to EarnBet via the /claim/ redirector, EarnBet's own analytics will see the referring URL and the timestamp — the standard affiliate attribution signal. Third, if we are compelled by a lawful court order to disclose logs or correspondence, we comply with the narrowest scope the order allows. We do not sell personal data to anyone, and we do not share it with advertising networks.

This site is not for anyone under 18. We do not knowingly collect data from readers under 18, and we age-gate the first page you load with a consent prompt. If you are a parent or guardian and you believe your child has somehow submitted their email address to our contact form, write to `editor@earn-bet.com` and we will delete the record immediately. Gambling itself is restricted to adults in every jurisdiction where EarnBet operates; the operator applies its own identity checks before any withdrawal, and no affiliate referral can bypass those.