Reference

Privacy Policy for lion casino Accounts

lion casino Privacy Policy explains how we collect, use, protect, and retain the details connected with your account, wallet activity, and device access.

Account clarityWallet recordsDevice controlsContact route
Browse Our Lobby Read FAQ
lion casino Privacy Policy for lion casino Accounts
CONTACT OPTIONS

Three Ways To Ask About Privacy

A clear contact path helps you ask what we hold, why we use it, or how to correct an account detail.

Account request Use the support path inside your account to ask for a copy of account details, the purpose of processing, or a correction. We may confirm your registered phone before responding, so another person cannot request your private records by mistake.
Wallet record For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, send the transaction reference and date through support. We use those details to locate the record while avoiding a request for your wallet password or full authentication code.
Device concern If a login appears on an unfamiliar phone or browser, contact us through the account support route and describe the device path. We can review security events, help protect the session, and explain which device records relate to your Privacy Policy request.
DATA CONTROLS

How We Handle Your Account Records

We keep our data handling practical: collect what is needed for an account request, use it for a stated purpose, and restrict access to authorised operational work.

Account details

When you create an account, we use the submitted contact details to identify the account and complete phone verification before access. We do not need your account password in a support message. Keep that password private and use the account path when asking us to change a record.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account entries can create status, reference, and reconciliation records. We use them to match a cashier event or receipt question to your account. A payment record does not give us your wallet login credentials.

Cookies

Cookies can keep a session active, remember a language or display choice, and help identify unusual sign-in behaviour. You can adjust cookie controls in your browser settings. Some account security functions may not work as intended when essential session cookies are blocked.

Device security

We may record device type, operating system, browser, approximate network signals, login time, and security events. These signals help us spot an unfamiliar access attempt from a mobile phone or desktop. They are used for account protection, not as a request for your device contents.

Retention period

We retain account, payment, and security records only for as long as needed for the purpose described, account support, dispute handling, or legal duties. When a record is no longer needed, we remove it, anonymise it, or restrict it according to our retention process.

Change request

You can ask us to correct inaccurate contact details, explain processing, provide eligible account records, or raise an objection through the support route. Include the registered phone or email and a precise request. We verify identity first, then explain any limit required by local law.

Privacy Policy Questions From Indonesia

These answers focus on the questions we expect you to have before opening an account or sending a privacy request. They explain the practical link between your account, local wallet records, cookies, device signals, and our support route. Read the full Privacy Policy alongside these answers, especially where local law permits or restricts a request.

It covers account details, phone verification, payment references, cookies, device signals, security events, support requests, and retention. For example, a QRIS receipt reference or a login from a new browser may be stored for account service and security checking. Eligibility depends on local law.

We use your phone number to identify your account and complete the phone verification step before account access. It also helps us match a privacy request to the correct record. Send changes through support rather than posting your number or verification code in a public message.

Yes. The policy covers records created when you use DANA or QRIS, including a payment reference, status, date, and reconciliation result. We use those records to answer receipt or wallet questions. We do not ask for your DANA or QRIS password through support.

You can submit a request through the support route inside your account and ask which eligible account, wallet, cookie, or device records we hold. Include your registered phone or email. We may verify identity first, and the response depends on local law and applicable limits.

Send a correction request through account support and identify the field that is wrong, such as a phone or email detail. We may ask for verification before changing it. This protects your account from an unauthorised edit and lets us keep the record accurate.

We keep records for the period needed for the stated purpose, account support, payment disputes, security checks, or legal duties. This can include DANA, GoPay, bank transfer, and virtual account references, plus device events. Afterward, we remove, anonymise, or restrict them.

Contact us through the account support path, describe the device or browser, and avoid sharing your password or full security code. We can examine the related security event. You can also adjust browser cookie settings, although blocked session cookies may affect account access.

Related Pages

lion casino Indonesia Super Bull Live Arena lion casino Casino Account information FAQ