Privacy Policy

How we use the little data we hold

The data this site collects is used for three purposes and nothing else. First, basic traffic logs — page URL, country, device type — help us notice when a Kenyan reader cannot load the Captainsbet review on an older Android build so we can fix it. Second, if you write to the editorial desk, we keep the thread long enough to reply and run the usual fact-check that led to the edit on the page. Third, when a visitor clicks through to the operator we record the click against the page so we can tell which review actually helps readers find what they came for. That is the full list — nothing here is traded, rented or re-used for retargeting.

Visitors who are under 18

Captainsbet is an 18+ product in Kenya and this site is not intended for anyone below that age. We do not knowingly collect personal information from under-18s, and no part of the site is designed as marketing to minors. If a parent or guardian believes a child has written to us by mistake, please let the editorial desk know and the message will be deleted within one working day along with any traffic log line associated with it. The responsible-gaming page in the footer also carries links to support services that work with young players or their families.

Where our data physically sits

Hosting for this site is provided by Cloudflare's global edge network, which means the HTML and images may be served from a point of presence outside Kenya — most Kenyan readers are answered from Nairobi or Johannesburg, but a fallback in Europe is possible during an incident. Email sent to the editorial inbox is read on the same provider's platform and backed up in encrypted form. We do not sell data to third-country buyers, and we do not use advertising networks that aggregate reader profiles across sites.

What we actually collect

On a normal page view we see the following and nothing else: the URL you opened, a very rough location (usually at the country level — Kenya, Zambia, sometimes a city), the model of device as reported by the browser and a timestamp. We do not see your Captainsbet login, your M-Pesa PIN, your account balance, your bet history or any identifier the operator holds on their side. When you fill in the contact form we see the text you submit and the email address you volunteer; that pair is enough to reply and is deleted once the thread is closed.

A note on cookies

The only cookies this site drops are the strict-necessary ones — a session id so the mobile menu remembers whether it is open, a preference flag for the cookie banner itself and a short-lived identifier that helps us dedupe pageviews. There are no advertising cookies, no third-party trackers for retargeting and no fingerprinting scripts. A separate page at /cookie-notice/ lists the exact cookies we set, how long each one lives and how to clear them inside the three browsers Kenyan readers use most (Chrome on Android, Safari on iOS, Chrome on desktop).

Who else sees your data

A short list, because it is short on purpose: Cloudflare for hosting and attack mitigation; a single email provider for the editorial inbox; the operator we are reviewing, but only when you click through — at that point the usual affiliate parameters pass across so Captainsbet knows which review the lead came from. No advertising platform, no data broker and no SEO vendor reads what you type into the contact form. If any of that ever changes we will say so on this page and date the change, and the version history is kept in the editorial-policy section of the footer.