Cookies

When you click our outbound CTA to /visit/ a small identifier may be dropped by the destination operator so it can tell that the signup arrived from this site. That cookie belongs to the operator, not to us; its policy covers how long the identifier lives and what data it attaches to. Our editorial does not read it back from your browser. The lifetime of the operator cookie is usually thirty days from the click, during which a subsequent signup at the operator still gets credited to the referring site. After that window the cookie expires and future visits are treated as organic by the operator's own tracking. If you clear cookies before signing up, the attribution is lost and we receive nothing — which does not matter to you as a reader. For South African readers the practical difference is that the operator's privacy notice is the one that governs this attribution cookie, not ours. If you want the attribution removed, clear the SuperSportBet cookies in your browser between the click and the signup; the operator will then treat the signup as organic and we will not receive any attribution. This option is always open to you and does not change what you pay or what offers you see on the operator side.

On this editorial we use strictly necessary cookies for session continuity and preference storage (dark-mode toggle, language choice). We do not run advertising cookies and we do not sell cookie-derived data to brokers. The full list is maintained in our cookie register and reviewed each quarter. Session cookies for login state do not apply here because we do not have reader accounts. Preference cookies for dark mode and language choice live for ninety days unless you clear them. If we ever add a reader-poll feature it will drop a short-lived cookie with a clear name and we will add it to the register the same day. We also maintain an audit log that lists every cookie our content management system wanted to drop and whether we accepted or blocked it. The audit log is reviewed quarterly by the duty editor and the technical lead together. Any cookie added by a new theme, a new plugin or a new embed has to pass this review before it ships to readers, and the review decision is recorded in the register. Readers who want to inspect the audit log for a specific quarter are welcome to request it on e-mail.

A cookie is a small text file that a site asks your browser to store so it can remember you on the next visit. Some cookies live only until you close the tab; others sit on disk for a defined period. Modern browsers let you inspect, filter and delete them from the privacy settings. First-party cookies are set by the domain in the address bar; third-party cookies are set by other domains referenced from the page (fonts, embeds, analytics). Modern browsers block most third-party cookies by default and let you deny the rest. On this editorial there are no third-party cookies from the content; the only third-party cookie you may see is the operator attribution cookie after you click /visit/. For readers who want to go deeper, the Mozilla developer documentation at developer.mozilla.org has a clear reference on cookie semantics, HttpOnly and Secure flags, SameSite modes and the modern cookie expiry rules. The browser-level tools (right-click → Inspect → Application → Storage → Cookies in Chrome; Storage Inspector in Firefox) show you every cookie currently in play on a page, who dropped it, when it expires and what value is stored. Learning that pane is the fastest way to audit any site, not just ours.

If the cookie list changes we update the dated line under the heading and leave a sidebar notice for thirty days. Material changes (a new category of cookie, a longer retention period) trigger a fresh consent prompt the next time you load the site. We also publish an archive of previous cookie registers so a reader can see what was dropped in a given quarter. The archive is updated when a quarter closes and is kept for two years. If you are preparing a POPIA complaint, that archive is the easiest way to establish what was running on the day you visited. Our cookie register is also machine-readable: a JSON copy lives at /legal/cookie-policy/register.json and is updated the same day the human-readable text changes. The JSON copy is intended for automated privacy tools that scan sites for compliance, and for researchers who track cookie trends across the gambling vertical over time. Anyone building such a tool is welcome to point it at that endpoint without asking us first. We will not throttle legitimate audit traffic and we will fix any discrepancy between the JSON and the prose version within one working day of a report.