Privacy at GladiatorsBet: the data specification, stated together
We collect what an account needs to run, and the types, the purposes and the rights are stated in one pass. Our terms carry the security figures — TLS 1.2 with 256-bit encryption in transit, the player database behind a firewall — and this policy uses the same words for the rest.
The data our account may collect
| Data type | Purpose | Rule behind it |
|---|---|---|
| Registration fields | identifying the account | accurate details keep payouts inside the window |
| Account currency | fixing which figures apply | chosen at registration from 17 options |
| Transactions | running deposits and payouts | the payout clock and ceilings depend on them |
| Bonus records | tracking claimed stages | EUR 5 stake rule and 8x cap during a bonus |
| Verification files | confirming identity and payment ownership | requested at payout, 24-hour window |
How third parties touch the data
The payment routes process their own side
A deposit through Skrill or Bitcoin runs partly in the systems of that route; our lobby does not hold the payment credentials those systems use.
What our terms do not describe
Our terms name no marketing-sharing schedule and no advertising network on the lobby pages, and support messages travel inside the account environment rather than a separate system.
How policy changes are announced
The visible date line
Changes appear in the policy with the date line at the end updated, and the terms pages carry the same wording so a change never splits between texts.
The account message to registered players
Material changes reach registered players through an account message before they take effect.
The rights a reader keeps over the data
Asking what the account holds
A written request through support — the same routes that answer payments and bonuses in five languages — opens the account record.
Correcting the registration details
Registration fields can be corrected before verification, and a name that matches the form keeps the payout inside the window our terms give.
Closing the account and its data trail
The terms allow closure through support; a player who stops logging in meets the dormancy rule instead, with monthly fees on a positive balance.
How the data is used, purpose by purpose
- Registration fields identify the account and fix the currency figures.
- Transaction history keeps the payout clock, floors and ceilings working as published.
- Bonus records track the claimed stages and their wagering progress.
- Verification files serve the payout check within its window and nothing else.
- Support messages are read by the team that answers in five languages.
Cookies and analytics, briefly
The session runs on the cookies our cookie policy describes: essential cookies hold the login, preference cookies keep the language among the 13 interface languages, and no cookie carries balances or bonus states — those live in the account behind the login, inside the encrypted environment our terms describe.
Last updated: 2026-11-09