Your account with Lüks Casino comes with certain data handling practices attached, and this page lays them out. It works alongside the Terms of Use, not instead of it.
Where your data comes from
Three channels feed the data we hold. You supply some directly when you register. Your activity on the site generates more of it automatically. Your payment provider passes along the rest when a deposit or withdrawal clears. None of it is bought in from outside sources for marketing purposes.
Contact and identity details
Your phone number and email stay on file for as long as the account is active, used to confirm logins and reach you when needed. Your name and date of birth serve a narrower purpose — confirming you are old enough to hold the account — and are kept for whatever period the law sets.
Financial and activity records
Payment details exist to process deposits and withdrawals; betting and game history exists to settle rounds correctly and to review any complaint that comes up later. Both categories are retained for the legally required period, not indefinitely.
Technical and support data
Your IP address and device information help catch fraud and duplicate accounts, and are kept only briefly after being logged. Messages exchanged with support are kept a short while after a complaint file closes, then removed.
Why the data gets processed
Four separate grounds justify processing, and each covers a different slice of what happens on the account.
- Fulfilling the contract between you and the site — the account itself, an accepted bet, a processed payment.
- Meeting a legal obligation — age checks, identity verification, statutory record-keeping.
- Protecting a legitimate interest — catching fraud, bots and accounts run in duplicate.
- Acting on your explicit consent — bonus announcements and campaign messages you can opt out of.
Consent for notifications can be pulled back whenever you like without any effect on the account itself — only the marketing stops.
Cookies on the site
| Cookie type | What it does |
|---|---|
| Essential. | Keeps your session open; without it, login and normal use are not possible. |
| Preference. | Remembers language and display settings between visits. |
| Measurement. | Shows aggregate usage patterns across sections, without identifying you individually. |
Your browser settings let you delete or block any of these categories, with one consequence worth knowing: blocking essential cookies removes your ability to log in at all.
Who else sees it
Data leaves our hands in a few specific, limited cases. Payment providers get only what a given transaction requires to complete. Game studios see enough to verify a round's outcome against the bet record. Identity verification services confirm your age and that the account belongs to you. Authorities receive data only when the law obliges it. Outside those cases, nothing is sold for advertising and no list is rented to a third party — any provider we use works strictly on our instructions.
Keeping the data secure
- Your connection to the site is encrypted end to end.
- Passwords are stored irreversibly, meaning even support staff cannot view yours.
- Internal access is role-based — payment records go only to the payments team, a complaint file only to whoever is handling it.
Part of this responsibility sits with you: reuse your password nowhere else, and never pass a confirmation code to another person.
Requesting access to your data
Support is the channel for any of the following requests: a copy of what we hold on you, a correction to inaccurate details, deletion of anything outside the mandatory retention window, or an objection to marketing contact. Closing an account does not erase everything instantly — payment and betting records still run out their legal retention period first. A self exclusion entry stays on record until its term is up, detailed further on the Responsible Gaming page, and a disagreement over how your data was handled follows the Player Complaint Policy.
Updates to this notice
Whatever version is published here at a given moment is the one in force. Should a future update expand what data gets collected, the contact address on your account is notified directly.