Privacy and personal information at Bety
We treat privacy as part of a considered account experience. This policy explains how personal information connects with the account path we describe: contact details, a password, the checks shown during registration, sign-in, the account area and the lobby. We use plain language because a player should be able to recognise the account context before raising a privacy question.
The same care applies when a player uses Bety through a mobile browser. Our mobile route does not require an app download, and password recovery uses a reset step sent to the contact detail linked to the account. A private device, a protected password and attention to the linked contact detail help keep account access deliberate.
Your choices about personal information
We invite players to raise a question about information connected with an account, to correct a contact detail that has changed, or to explain which account stage needs attention. A clear request starts with the relevant context: registration, sign-in, password recovery, deposit activity or a first-withdrawal question.
- Keep the contact detail linked to the account current.
- Describe the account stage when raising a privacy concern.
- Separate a password-recovery question from a payment-related question.
- Use a private device and keep reset messages private.
These choices help us understand what the player is asking about without turning a privacy request into a general account conversation. Our normal contact route is the place to raise the request, and a focused description helps keep the response tied to the right account context.
How we use account-related information
Information from account registration
Our registration flow uses contact details and a password, then continues through the checks shown in the flow. We use the account context to maintain the account relationship and to communicate about the journey from registration through sign-in. The contact detail also has a defined role in password recovery because the reset step is sent to that linked detail.
Information connected with payment activity
Payment activity can connect a deposit or withdrawal with the account. Our payment information names fiat currencies and crypto assets, says deposits generally show immediately in the account balance, and describes a first-withdrawal KYC point in historical information. We handle payment-related account context with the same care as other information connected with use of Bety.
Information used for account questions
When a player writes about sign-in, a linked contact detail, a deposit balance or a first withdrawal, the account stage gives the question useful shape. We use that context to keep the conversation focused on the product journey the player identifies. It is more useful than a message that mixes unrelated account stages together.
Account and payment information in context
We describe the Bety registration path as contact details, a password, and the checks shown in the flow. After those checks, the sign-in area leads to the account area and lobby. That sequence explains why account information deserves deliberate handling: each stage is part of the same player journey, while each question can concern a different part of it.
Payment-related context is similarly specific. Our payment information names fiat and crypto routes, deposit balance visibility, recipient transaction costs and a historical first-withdrawal note. A privacy question can identify whether it concerns a deposit balance, a listed currency route or the first-withdrawal account stage, rather than combining all payment details into one request.
Protecting access to account information
We encourage a strong, private password and careful control of the contact detail linked to an account. Password recovery uses a reset step sent to that detail, so the detail and the reset message both form part of careful account access. Mobile-browser use makes the same point practical: choose a private device and end a session with attention to the account context.
Last updated: 17 November 2026
