Reference

lionbola Privacy Policy for Indonesia Accounts

Our Privacy Policy explains how we handle the account details, device session and wallet references connected with Live Casino, Medusa and other lobby areas.

Account dataCookie choicesLocal access

Browse Our Lobby Read FAQ

How DANA Data Fits Our Privacy Policy

lionbola Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details you provide during account creation, including your phone number, verification result and account sign-in records. It also explains technical data from your browser or device, such as session time, approximate region and security events, so we can connect the correct

1
account with the correct wallet status. If you select DANA, OVO, GoPay or QRIS, payment references and transaction status may be passed between us and the relevant payment process; we do not present wallet credentials as public account details. Bank transfer and virtual account references are
2
handled for matching and reconciliation. We use these records to process your request, protect account access and answer a policy query. Access to the service depends on local law, and we may ask for account details before discussing a privacy request.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Privacy Help Through Your Account Path

A clear account route helps you ask about the Privacy Policy without sending sensitive details through an unrelated channel. Open your account support path, state whether the question concerns sign-in, a wallet reference or stored device data, and include the account phone number only when requested. We use that context to locate the right record and respond to you.

Team online

Account access

If your phone verification or sign-in stalls, use the account support path and mention the affected device. We can connect the access issue with the relevant Privacy Policy request.

Wallet records

For DANA, OVO, GoPay or QRIS references, tell us which transaction status you are asking about. Avoid sending wallet passwords; we need only the account details required to trace the record.

Policy request

Ask for a copy, correction or removal review through your account support route. We may verify your phone before changing records, which helps prevent another person from acting on your account.

SECURITY PRACTICE

Security Steps Before QRIS Access

We apply the Privacy Policy at each account step, from phone verification to a return visit on your mobile browser.

Account security

Phone verification links an account request to the contact detail you supplied. We may use sign-in time, browser signals and unusual session activity to protect access before showing wallet records.

Payment references

DANA, OVO, GoPay and QRIS may return a reference or status value rather than wallet credentials. We use that value to match your account request and resolve a payment query.

Cookies

Cookies and similar session tools help retain login state, remember selected settings and identify security events. You can clear browser data, though this may require phone verification again.

Retention

We keep account and transaction records for the period needed for access, dispute handling, security checks and legal duties. When that need ends, records are removed or separated from account use.

Your changes

You can ask us to correct contact details or clarify the data linked to your account. We first check your identity through the account path before applying a change.

Other services

Payment processors may handle the transaction references needed for DANA, QRIS, bank transfer or virtual account matching. Their handling follows the role they perform for that request.

Privacy Questions for Your lionbola Account

These answers address the Privacy Policy questions that usually matter before account access: what we collect, how wallet references appear, how cookies work and how to request a change. Read the full policy above, then use your account support path if your situation needs a record-specific answer.

It covers account details, phone verification, device and session signals, cookies, payment references, retention and requests to access or correct records connected with your account.

We handle payment references and status values for DANA, OVO, GoPay and QRIS matching. Do not send wallet passwords through support; those credentials are not needed for a policy request.

Phone verification helps connect an account request to the correct person and reduces unauthorised changes. We may request it before discussing stored data or changing account contact details.

Yes. Use the account support route and request the data linked with your account. We may confirm your phone or another account detail before releasing records to the correct requester.

Send the correction request through your account support path, identify the field that needs updating and explain the change. We check account ownership before applying any amended contact detail.

We retain records while they are needed for account access, transaction matching, security checks, dispute handling or legal duties. After that need ends, records are removed or separated from account use.

Yes. The policy covers data from a mobile browser, including session and cookie records. Clearing browser storage may end your session and require phone verification when you access the account again.

lionbola Privacy Policy for Indonesia Accounts

Privacy Help Through Your Account Path

Account access

Wallet records

Policy request

Security Steps Before QRIS Access

Account security

Payment references

Cookies

Retention

Your changes

Other services

Privacy Questions for Your lionbola Account

01 What does the lionbola Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS password?

03 Why does lionbola need phone verification?

04 Can I ask for my account data?

05 How do I request a correction under the Privacy Policy?

06 How long are account and payment records kept?

07 Does the Privacy Policy apply on mobile browsers?

Related Pages