Below are answers to the questions players ask most about personal data at Lüks Casino. It works alongside the Rules of Use, and opening an account counts as accepting both.
What data does the platform hold, and for how long?
- Phone number and email.
- Used to open the account, confirm login, and reach the player. Kept while the account stays open.
- Full name and date of birth.
- Checked against the 18 age limit and account ownership. Kept for the period the law sets.
- Payment details.
- Needed to process a deposit or a withdrawal. Kept for the period the law sets.
- Betting and game activity.
- Used for settlement, bonus wagering checks, and complaint review. Kept for the period the law sets.
- IP address and device fingerprint.
- Used against fraud and duplicate accounts. Kept for a short window after the record is created.
- Support tickets.
- Kept to track and close an open case, then for a short window afterward.
- Cookie identifiers.
- Kept for as long as the individual cookie is set to last.
None of this is bought from outside data brokers; every entry above comes from the player directly, from platform activity, or from a payment partner.
On what basis is the data processed?
| Basis | What it covers |
|---|---|
| Contract performance. | Opening the account, accepting a bet, settling a payment. |
| Legal duty. | Age checks, identity verification, statutory record keeping. |
| Legitimate interest. | Blocking fraud, bots, and duplicate accounts. |
| Consent. | Bonus alerts and campaign messages, revocable at any time. |
Turning off consent-based messages does not touch the account itself — it only stops marketing content.
How are cookies used?
Three cookie categories run on the site. Essential cookies keep a session logged in and cannot be switched off without losing access. Preference cookies remember language and display settings. Measurement cookies report usage patterns in aggregate rather than by individual player. Browser settings can clear or block any of the three, with the caveat that blocking essential cookies breaks login.
Who receives this data?
- Payment providers, limited to what settling the transaction needs.
- Game studios, to confirm a round outcome against the bet record.
- KYCAID as the identity verification partner, to confirm age and ownership.
- Public authorities, only where the law requires it and only to the extent asked.
Advertising sales and list rentals to outside parties do not happen. Any processor working with this data acts strictly on instruction, not on its own initiative.
How is the account kept secure?
Traffic between the browser and the platform runs encrypted, and stored passwords cannot be reversed by anyone, including support staff. Internal access is scoped by role: payment records are visible only to the payments team, a complaint file only to the assigned handler. Half of the security burden sits with the player — reusing a password elsewhere, sharing a confirmation code, or leaving a session open on a shared device all weaken it regardless of platform controls.
What rights does a player have over their data?
- Request a copy of the personal data held on file.
- Ask for incorrect or incomplete details to be fixed.
- Ask for deletion of anything that has passed its legal retention window.
- Object to marketing use and withdraw consent at any point.
Requests go through support. Closing an account does not erase records instantly — payment and betting history stays until the statutory period runs out, and a self-exclusion record stays on file for its full term so the exclusion holds, detailed on the Play Safe Guide page. A data-handling dispute follows the steps on the Complaint Roadmap page.
Does this notice change over time?
Yes — the version live on this page is the one in force, effective from publication. Any change that widens what is collected or who it is shared with triggers a notice to the contact address on file.