How We Handle Player Information

We treat privacy as part of a clear player relationship. Information can arise when a player registers, makes a transaction, contacts support or supplies material for an identity review. We use the details involved in those interactions to run the relevant account process and respond to the player who raised the matter.
This policy explains practical categories of information connected with our service and the routes a player can use to raise a privacy question. We use plain wording because a privacy choice should be understandable before it becomes urgent.

Keeping account information in context

Registration details for UK accounts

We may receive the email address, password, and basic details a player supplies during registration. UK account material names email, mobile number, date of birth, and UK address among the new-account fields.

Payment and verification details

We may handle transaction context when a player asks about a payment or withdrawal. Before a first withdrawal is approved, identity documents may be reviewed. The document categories named for that process are photo ID and proof of address dated within the previous three months.

Details supplied in contact requests

We use the information a player supplies in a contact request to understand and answer the question. Our contact route includes name, email, an optional phone field, project details and privacy-policy consent.

Keeping policy changes clear for readers

We review privacy wording when the way a player interacts with us changes. An update is an opportunity to understand the current language rather than background text to ignore.

  • We publish updated wording when our privacy policy changes.
  • A date shows a player which version they are reading.
  • Players returning after a long break can review the current policy.

Using information for account purposes

Registration context and support requests

We use registration information to support the account relationship. Our team can address registration, payments, bonus questions, game access and general account matters through live chat or email.

Payment and withdrawal account context

We use relevant transaction context when a player raises a deposit or withdrawal question. A first withdrawal can pause while identity documents are reviewed, which can bring account and verification context together in one support request.

Contact requests and privacy consent

We use information from a contact request to respond to its subject. The contact route includes privacy-policy consent, giving a player a moment to consider the request before sending it.

Your privacy questions and choices

We invite players to raise privacy questions through our support routes. Live chat is the fastest route for an urgent first conversation; email suits a detailed request. Tell us whether the question concerns registration, contact, payment, or verification so we can keep the conversation in the relevant account context.

  • We use live chat for an urgent first privacy question.
  • Email suits a request that needs fuller background or document context.
  • Players can describe the relevant account stage in their own words.

Information that can arise in our service

Details supplied when joining

We may receive an email address, password, and the basic details in the registration form. UK material names a mobile number, date of birth, and UK address among further account fields.

Details connected with activity

We may handle account and transaction context when a player uses casino, live casino, sports book, or crash-game services under the shared account balance. This can include the details needed to address a payment or withdrawal question.

Details supplied during contact

We may receive name, email, an optional phone number and the detail included in a contact request. Keeping a message relevant to the question helps a player and our support team focus on the right matter.
Last updated: 20 November 2026