BetBlast

Privacy at BetBlast

We collect the data an account needs to function: sign-up details, transaction records and the usage information that keeps the lobby working. We use it to run the account, process payments, answer support requests and meet verification duties, and we protect it with the encryption that also carries the sign-in.

Who we share data with

  • Payment processors receive the transaction details a deposit or withdrawal needs.
  • Verification partners receive document categories when the second step applies.
  • Support systems keep chat and e-mail history so a case is answered in one thread.

Beyond these three, data moves nowhere without a duty behind it; the account itself decides most of what exists, because a field left empty at sign-up never enters the record.

When this notice changes

We announce changes to the notice through the account and the visible date line below, so players can see when the wording moved. A change that touches how existing data is used gets its own line in the announcement, and continued play follows the current wording shown here.

How data is protected

Sign-in and cashier traffic runs over 128-bit SSL/TLS encryption, tiered KYC keeps each account level to the data it needs, and support asks for document categories rather than full files where the tier allows it. The second verification step applies at deposits over EUR 2,000 or any withdrawal, which keeps a payout behind more than a password.

Your rights over your data

  • Access: a request through support shows what the account holds.
  • Correction: wrong details are fixed once identity is confirmed.
  • Deletion: closed accounts are handled per the retention rules below.
  • Objection: requests about processing go through the same support route.

Requests are answered in the language of the account, and the reply names what was found, what was changed and what stays for a stated duty.

How long information is kept

Account and transaction records are kept while the account is open and for the period verification and payment duties require; support history is kept so a case can be reopened with its context. When a retention period ends, the data leaves the operational systems rather than lingering as a spare copy.

How we use information, purpose by purpose

Sign-up data opens and identifies the account, transaction data moves deposits and payouts, usage data keeps the lobby and promotions relevant, and verification data satisfies the second-step checks that guard withdrawals. Promotions use the account data to show the offers a player qualifies for, from the welcome match to the Sunday cashback, and nothing beyond the account’s own record feeds that decision.

Information we may collect

Data typePurpose
Sign-up detailsOpen and identify the account
Transaction recordsProcess payments and payouts
Verification documentsMeet second-step checks
Support historyAnswer cases in one thread
Usage informationKeep the lobby and offers relevant

Last updated: 2026-11-18