What GladiatorsBet does with account data, purpose by purpose
We collect what an account needs to run, and the purpose comes before the type in this policy: registration fields exist to identify the account, transaction records exist to run the cashier, and verification files exist for the payout check alone. The security figures our terms state — TLS 1.2 with 256-bit encryption in transit, the player database behind a firewall — apply to every purpose equally.
The purposes run first, then the collected types, the change announcements, the cookies in brief and the rights a reader keeps, closing with the date line our policy carries.
How the data is used, purpose by purpose
Our use of the data follows the account rather than any marketing schedule: the registration fields identify the player, the currency choice fixes which figures apply, the transaction history keeps the payout clock and ceilings honest, the bonus records track claimed stages, and support messages are read by the team that answers in five languages.
What the account may collect
The registration and currency data
The form fields and the chosen currency — seventeen options at registration — sit at the head of the record and fix the figures everything else uses.
The transaction and verification records
Deposits and withdrawals with dates, routes and amounts; the claimed bonus stages and their wagering progress; and the verification documents a payout request asks for inside its 24-hour window.
The support exchange and its languages
Messages sent through live chat or email, read by the team that handles the account in the same five languages.
How changes to this policy are announced
The date line and the terms
A change lands in the policy with its date line refreshed at the end, and the terms pages are re-worded at the same moment, so no update ever stands half-applied between two texts.
The account message before the change
Registered players learn of material changes through an account message that lands before the change takes effect.
Cookies and analytics, in brief
- Essential session cookies carry the login state and the cashier session.
- Preference cookies keep the interface language among the 13 the site runs.
- No cookie carries balances, bonus states or payout requests; those live in the account behind the login.
- Our terms name no advertising network on the lobby pages; the full detail sits in the cookie policy.
The rights a reader keeps over the data
Asking what the record holds
Asking our support in writing — chat or email, whichever the reader uses — is enough to learn what the account stores.
Correcting before the check
Registration fields can be corrected before verification runs, and an exact name keeps the payout inside its window instead of delaying it.
Closing the account through support
Closure goes through support as well; an account left alone instead meets the dormancy rule, whose monthly fees land on a positive balance after the inactive period.
Last updated: 2026-11-08