How data works

Data is collected to run the account, move money, answer support messages and satisfy what the Anjouan licence obliges the operator to check. Nothing is gathered for its own sake, and nothing is sold on. The list below is all of it.

• Name, date of birth and address, which is what an account is opened against;
• Payment details and the record of transactions, so deposits and payouts can be traced;
• Login records, IP address and device, which is how a stolen account gets spotted;
• What you open and how often, which decides what the site shows you;
• Support conversations, kept so the next agent does not ask twice;
• Everything is encrypted in transit and where it sits at rest;
• Inside the company, only staff whose work requires the data can reach it;
• Security is reviewed rather than set up once and left;
• Data is deleted once the reason it was collected has gone away;
• Anything passed to a third party goes with a contract behind it;

You can ask to see what is held about you, ask for a correction, or ask for it to be deleted. Write to [email protected] from the address the account uses, and say which of the three you want.

Every processing activity is run to the standard the Anjouan licence sets, and to ordinary international practice besides. Each use of data has a reason behind it. If you want the reason for a particular one, ask for it.

Collected data has a small number of jobs. It opens the account and keeps it open, it clears payments, it answers you when something breaks, and it satisfies the checks the licence requires. Each of those is spelled out below.

• Creating the account and confirming that the person is you;
• Processing deposits, withdrawals, bets and the money that comes back from them;
• Answering support requests and finishing whatever started them;
• Working out which parts of the site get used and which do not;
• Sending offers and promotions, where you have agreed to them;
• Spotting fraud, stolen logins and accounts opened under false details;
• Meeting the obligations that come with the licence;
• Producing figures for the operator's own reporting, with names stripped out;
• Showing what happened when a bet or a payment is disputed;
• Deciding what to build next and what to leave alone;

Marketing consent is separate from the rest and can be pulled back without touching the account. The other uses cannot be switched off while the account is open, because they are what the account runs on.

Most of your details are editable inside the account. Open the settings and you can change the contact details, the address and the password yourself. Some fields lock once verification is finished, for a reason that should be obvious: an identity that changes after it has been checked is not an identity. Deletion goes through support, and the request is verified before anything happens, so that nobody can empty your account by pretending to be you in an email.

Nobody under 18 may hold an account. Age cannot be confirmed from a form, only from a document, which is why the identity check exists and why it stands in front of the first payout. What follows is what happens when an under-18 gets through anyway.

• Registration states the age limit, and the box is ticked before anything opens;
• An account that fails the age check is closed rather than suspended;
• Whoever is responsible for a child can demand that the data goes;
• Where a minor's data is found, it is deleted and the account goes;
• Stakes placed by a minor are voided and the deposit returned;
• Anything reported by a parent or guardian is dealt with first.

Registration sits in Costa Rica, the licence on Anjouan, so your data is processed outside Kenya from the moment the account opens. The payment providers and the game studios are elsewhere too. Using the site means agreeing to that, and the points below say on what terms.

• Transfers happen where there is a reason for them and not otherwise;
• Where a partner sits is checked before anything is sent to it;
• Contracts with partners carry the data protection terms in writing;
• Data in transit is encrypted, whatever border it happens to cross;
• You can ask which categories of partner hold data about you;
• Complaints about a transfer go to support and get answered in writing;

Some of what follows limits the operator's responsibility rather than extending it, which is the point of writing it down. It applies from the moment you accept this policy at registration, in the version current then.

• Where an outside party loses data, answering for it is theirs and not ours;
• Share a password, or reuse one from somewhere else, and what follows is yours;
• What an external site collects is governed by its policy, not this one;
• Data handed over because the law required it is not a breach;
• Where the service goes down for reasons outside it, liability is limited;
• None of this removes a right the law gives you anyway;

Cookies are small files the site leaves on your device. They keep you logged in between pages, remember what you set, count how the site gets used and carry the referral that brought you here. Your browser can refuse them, and the site mostly still works, though staying logged in stops being automatic. Clearing them from the browser removes them. No cookie here carries your name.

Using the account means accepting the version of this policy that is current at the time. The latest version replaces every earlier one. Changes that matter are announced before they take effect, by email or in the account, and carrying on using the site after that is how agreement to them gets recorded.

Data goes outside the operator in three situations: where the law demands it, where a dispute has to be resolved, and where somebody has to be paid or verified on the operator's behalf. Categories of recipient are below. Names of individual suppliers are not published.

• Sharing happens on a legal basis or on your consent, never otherwise;
• Every recipient is bound by contract to protect what it gets;
• Payment providers see what they need to move the money, and no more;
• The verification service sees the documents you upload and the result it returned;
• Regulators and law enforcement get what a lawful request obliges the operator to give;
• A recipient cannot reuse data for a purpose it was not given for;
• You can ask which categories have received data about you;
• Complaints about a disclosure go to support and are answered in writing;

The site links to places the operator does not run: payment providers, game studios, the affiliate programme. Those sites have their own policies, and what they collect is between them and you. It is worth a minute to read one before typing anything into it.

• External links are there for information, nothing more;
• What sits on an external site is not controlled from here;
• A leak on an external site is not the operator's to answer for;
• Read the policy of an external site before you use it;
• A transaction made on an external site is yours to manage;
• A link is not a recommendation of what it points to;
• Questions about a link on this site go to support;
• An external site can change its policy without telling anybody here;