Cookie Policy — Captainsbet
The only third-party cookie set on this site is the Cloudflare `__cf_bm` token, which lives for 30 minutes and whose only job is to tell the edge network that a human and not a scraper is reading the page. It carries no advertising identifier, it is not shared with any analytics vendor and it cannot be used to reach back into a Captainsbet account. We do not embed Facebook Pixel, Google Ads tags, TikTok pixel, Meta Conversions API or any retargeting script of that family — a sports-betting review does not need them and they would make the page slower on a Nairobi 4G connection. If you clear site data in your browser, this cookie disappears and the next page view simply re-issues it.
A cookie is a short text file — usually a few dozen characters — that a website asks your browser to remember and return on the next request. On this site cookies do the small plumbing that keeps the pages working: remembering that you have dismissed the cookie banner at the bottom, preserving the position of the mobile menu while you scroll a review, and giving each visit a short-lived identifier so we can tell a reload apart from a fresh view. None of those files carry your name, your email address, your IP in clear form or any identifier a Captainsbet login screen would recognise. You can view and delete cookies on this site with the browser's own developer tools, or clear them wholesale from Settings → Privacy.
Three files, no more. `cookie-consent` — one year, strict-necessary — remembers that you have accepted or declined the banner so it does not pop on every page. `nav-state` — one browsing session only, strict-necessary — stores whether the mobile menu is open or closed as you move between the review and the FAQ. `visit-id` — 24 hours, analytics — a random string that lets us distinguish an accidental page reload from a fresh visit when we look at traffic logs in aggregate. There is no advertising cookie, no social-sharing cookie and no cross-site tracker. When you click through to Captainsbet the operator's own cookies take over on that domain — their list is published on captainsbet.com and is outside our control. If a reader from Nairobi or Lusaka wants to see every cookie that this site has set on their phone, the quickest route is to open Chrome, tap the three-dot menu, pick Site settings and then Cookies and site data; the entries for this domain are listed by name and can be removed one by one or all at once. On an iPhone, Safari does the same thing under Settings → Safari → Advanced → Website data. Clearing the files does not break any paid feature on this site — we do not have any — but it will reset the banner and the mobile-menu state the next time you visit. We also do not store cookies that persist across Captainsbet-brand domains: the `visit-id` is specific to this review site, so if you also visit the operator's own help centre or a different reviewer's site, the identifier you see there is a different random string set by that property. A final note on retention: traffic logs from `visit-id` are aggregated daily into page-view totals and the raw file is discarded after seven days. That is shorter than most sites and we keep it that way on purpose — the longer the raw log sits around, the bigger the attack surface if anything goes wrong on the hosting side, and the review does not need deeper history to stay honest.