This site has no accounts, no logins and nothing to sign up for. What it does have is a redirect layer that passes a tracking reference to an operator when you click through — which is how it is funded, and which almost no site of this kind explains. This page sets out what happens with your data here in plain terms, including the parts that are less flattering.
If you read nothing else on this page, read this.
Less than most sites, because there is less to collect.
| What | Why it exists | What it means for you |
|---|---|---|
| Server and network logs | Automatic. Any web request records an address, a timestamp, the page requested and the browser’s own description of itself. | Standard for every website in the world. Used to keep the site running and to see which pages are read, not to build a profile of you. |
| A content delivery and security layer | The site sits behind a network that filters malicious traffic and serves pages faster. | That provider necessarily sees requests as they pass through, under its own terms. This is how the large majority of the web works. |
| Analytics, if enabled | Aggregate page-level statistics: which pages are read, roughly from where, on what kind of device. | Aggregate rather than individual. If analytics are running on this site, the provider is named in this section — if no provider is named here, none is running. |
| Nothing else | There is no account system, no comment section, no form and no newsletter. | There is no database of readers here, because there is nothing that would create one. |
We do not sell it, rent it, or hand it to an operator. We do not build advertising audiences and there is no display advertising on this site to build them for. The commercial relationship runs entirely through the redirect layer described next, and it does not involve giving anybody a list of readers.
This is the part that funds the site, and the part that other guides describe as “we may earn a commission” without explaining the mechanism.
Every link from this site to an operator points at an address on this domain beginning /go/ rather than directly at the operator. Clicking it sends you to our server, which immediately forwards you to the operator with a tracking reference attached to the address. That reference is what tells the operator the visit came from here, and it is what causes a commission to be paid if you go on to register.
The address you click is on this site. Nothing about you is sent to the operator at this point.
The forward carries a reference identifying this site, and in some cases which page or placement the click came from.
From this moment you are on the operator’s site under the operator’s terms and privacy policy, not ours. The reference typically becomes a cookie set by the operator.
That attribution is the entire commercial model. It is also the limit of what we learn: we are told that registrations happened, not who made them.
Worth understanding, because it is a larger set of information than anything this site holds.
An operator’s site sees what any site sees when you visit it: your network address, your device and browser, the page you came from, and whatever its own cookies and scripts record. If you register, it then holds everything you give it — name, phone number, identity documents at verification, and a complete record of deposits, bets and withdrawals that it is required to keep for years.
That is not a criticism of any operator; identity and record-keeping obligations exist for good reasons and are covered on our verification page. It is a matter of proportion: reading this site is close to anonymous, and opening a betting account is emphatically not. The place to read carefully about data is the operator’s privacy policy, not ours.
Email is the only channel here, and it works the way email works.
Practical detail worth repeating from our contact page: if you would rather not use your main address, a throwaway one is fine for anything except a conversation that needs following up.
A short list, and it is absolute rather than aspirational.
We have no use for either and would not know what to do with one. No legitimate site or operator asks for a mobile money PIN; anything that does is fraud, and the patterns are on our payments page.
A code sent to your phone is the key to something. There is no circumstance in which sending it to us would help you.
Verification happens at the operator, not here. We never need to see an NRC, a passport or a selfie, and we would rather you did not send one.
There is nothing to pay for on this site. No card, no wallet number, no bank details, ever.
If anything presenting itself as this site ever asks you for any of the above, it is not us. Check the address in the browser bar, and note that look-alike domains are common enough around betting brands that the same warning appears on our apps page.
Written because the honest risk assessment points away from us.
Reading a guide leaves almost no trace. Betting leaves a durable one, and mostly not on any website: every deposit and withdrawal appears in your mobile money history with the counterparty and the date, and mobile money statements are routinely used as evidence of income and financial behaviour in contexts that have nothing to do with gambling.
The second exposure is the handset. A phone used by more than one person is a wallet and a betting account used by more than one person, regardless of who registered either. The identity consequences of that are on our verification page, and the practical ones are ordinary: lock the device, log out, and do not leave a session open on a shared phone.
That is a reasonable response and there is no downside to acting on it. Our page on staying in control covers the practical tools, including limits set at the operator rather than held as an intention.
Data protection rights depend on where you are, and the practical route here is the same either way.
Zambia has data protection legislation, and readers elsewhere have rights under their own. Rather than reciting a statute we would be paraphrasing, the useful thing to say is what we will actually do: if you ask what we hold about you, we will tell you; if you ask us to delete it, we will, unless something requires us to keep it; and if you think we have got something wrong, we will correct it.
In practice the answer to the first question is usually short, because the only thing we reliably hold about an individual is correspondence they sent us. There is no account, no profile and no purchase history here to disclose.
Requests go to the address on our contact page. Please do not send identity documents to prove who you are; if we cannot identify what you are asking about from the correspondence itself, we will ask, and the answer will not require a copy of your NRC.
And how you will know.
If what we do with data changes — if analytics are added, if a provider changes, if the redirect layer starts carrying something it does not carry today — this page is rewritten to say so, and the checked date at the top of the page moves. We do not append notices to the bottom of pages, here or anywhere else on this site.
The commitment behind that is on our method page: where a change alters what a page means, we rewrite the page so that the version a reader lands on is correct, rather than correct-with-an-addendum. The conditions on which the site itself is made available are in our terms of use.
General references used across this site.
These links leave our site. We control neither their content nor their availability; if one stops responding, tell us and we will pull it.