Skip to content

Welcome package

Up to €13,000

+ 300 free spins

across 3 deposits

Explore the deposit offer

What does your second deposit earn?

Code 2LB gives a 50% match and 100 free spins.

Example range: €20–€8,000. Enter up to two decimal places.

Bonus amount

€100.00

Required playthrough

€4,000.00

Free spins

100

40× the bonus amount within 7 days. Terms apply. Bonus terms

What Happens To Player Data At Legionsbetscasinos?

An online casino account cannot exist without data: a name, a date of birth, a payment record, a history of play. We collect what the account requires, use it for purposes a player can trace to a feature they chose, and keep it protected for as long as the relationship lasts.
Nothing on our list exists for its own sake — every type maps to a feature the account actually runs, from the login itself to the session clock. This policy walks through the data types, the purposes, the sharing and the rights around them in plain lines.

Your Rights Over Your Data, And How To Use Them

What a player can ask about their data

A player can ask what data their account holds, request a correction where a detail is wrong, and ask for closure of the account. Requests run through our support: chat opens the case, email carries the detail, and the account email ties the request to the right data set. A correction to contact data takes effect once we confirm the sender owns the account.

How a request runs

The account email identifies the data set, the request is matched against the terms, and the answer states what was done; dormancy rules at 90 days form the one boundary the player does not set.

The Data Types An Account Produces

Data typeExampleWhy it exists
Identity dataName, date of birthAge and document checks at verification
Contact dataEmail, phone numberLogin name, confirmation pair, support replies
Transaction dataDeposits, withdrawals, methods usedCashier operation, payout review, 3x turnover
Verification documentsIdentity document, card photo, statementThe identity check around a first withdrawal
Play dataSession duration, wagering historyBonus progress, session clock, loyalty points
Preference dataChosen currency, language, favouritesShowing amounts in the chosen currency and saved machines

How Each Type Is Used, Purpose By Purpose

Identity and contact data at work

Identity and contact data make the login, the confirmation pair and the verification work; without them the cashier cannot release a payout to the right person. Preference data keeps a euro account reading in euros and a favourite slot one tap away.

Keeping the rules workable

Transaction and play data feed the visible controls — turnover tracking, wagering progress, the session clock — and the review screens a payout request passes before it moves. Wagering progress decides when a bonus can ride along with a withdrawal, and the turnover record decides whether the 3x rule is met — both read straight from the transaction history.

Protection In Practice, Without Overclaiming

What the design aims at

Data sits behind account access, and documents sent for verification are used for that check; the minimum a request needs is the maximum we ask.

What a player controls

Strong credentials on the email that serves as account name, confirmation of both contact channels, and no password shared in any message keep the player side of the protection real. Support never asks for a password, so a message that does is not from the desk.
Last updated: 12 November 2026