Privacy Policy
What we collect
When you load kaleo.bet we store the usual web-analytics signals: a trimmed IP address, approximate country (down to state in the US), browser build, screen size, referring link and the pages you opened. We do not ask for your name, your Kaleo username, your email or any payment information — none of those ever leave your device for us. The analytics endpoint is cookieless; the fingerprint it computes is a one-way hash of a handful of browser attributes, which is enough to tell visits apart for 24 hours but not enough to recognise a single person across sessions on different days. We keep the raw log for 30 days and then drop everything that could be joined back to an individual visit. Aggregate counts — total page views per URL per week — stay longer because they tell us which parts of the review library are worth keeping updated. If you contact us by email, we obviously have the email address you wrote from until the thread is resolved; we delete that trail 90 days after the last reply unless you're a regular contributor who has asked us to keep the context.
Third parties
Three services sit behind this site: a privacy-first analytics endpoint (Plausible-style, no cookies), a CDN that handles asset delivery and a fraud-screening service that counts referral clicks on Kaleo links. None of them receive personal identifiers from us; they see hashed session fingerprints and country codes only. The CDN sees your IP address because it has to in order to route the request — the same way any website on the open internet works — but we don't ingest that IP into our own storage. The fraud screen is there to stop a certain class of affiliate click fraud; it compares a click to known bot signatures and either allows or declines the outbound redirect. Nothing in that pipeline is sold, licensed or shared with Kaleo beyond the aggregate click volume the operator sees in its affiliate dashboard.
How we use data
The analytics signal tells us which review sections readers finish, which bonus tables confuse people and which pages trigger a bounce in under five seconds. That shapes editorial priorities — nothing we store is sold, licensed or forwarded to Kaleo. Referral click counts are aggregate: Kaleo sees volume, not individuals. If a reader emails us about a specific review and we need to reproduce their experience, we may ask for the browser and country they were on — but we don't go spelunking in the log file to pull that out of thin air. Legal process is the one exception: a valid subpoena would get what the log contains at the moment of service, which is deliberately little, and we would notify the subject of the subpoena where law allows.
Changes to this policy
If we change what we collect or add a new third-party service, we update this page and surface the change in a short notice at the top for 30 days. The current version is dated at the end of the page. Historic versions sit in our git repository; email editor@kaleo.bet if you want a specific prior version mailed to you as a PDF. Material changes — anything that would add a new category of data or a new third-party recipient — require an editor-level signoff, not just a developer commit, and the signoff is logged in the same git history so a reader can audit it.