Reference

Privacy Policy for Your ligamension2 Account

The ligamension2 Privacy Policy explains what account, device and payment details we use when you open an account, access Live Roulette Royal or check a wallet status.

Account dataWallet recordsCookie choicesSecurity requests
ligamension2 Privacy Policy for Your ligamension2 Account
CONTACT YOUR WAY

Get Privacy Policy Help Without Guesswork

A clear support route matters when your account record or wallet reference needs attention.

Account data request Ask support to explain the personal data linked to your ligamension2 account.
Wallet record question For a DANA, OVO, GoPay or QRIS record, provide the payment rail, reference number…
Device access concern If your account opened on an unfamiliar phone, tablet or desktop, contact us with…
DATA HANDLING DETAILS

What Our Privacy Policy Covers

We treat privacy as an account operation, not a small print link. The policy explains why we collect each useful record, how it supports account access and wallet…

Account details

We use the contact and verification details you provide to create your account, confirm account access and respond to a…

Device signals

Login time, browser or device type and security events can help us identify unusual access.

Payment references

We may store a payment rail and transaction reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Cookies and sessions

Cookies and similar session tools help keep your account connected while you move through login, policy pages and the lobby.

Retention periods

We keep personal and transaction records only as long as needed for account service, security review, dispute handling and applicable…

Privacy changes

If our handling changes, we will present the revised Privacy Policy through the account or policy access path.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often from people deciding whether to open a ligamension2 account. They cover the data behind login, device sessions, wallet references, cookies and requests for access or correction. If your situation is not listed, use the support path and describe the exact account step or record involved.

It covers account details, verification records, device and login signals, cookie use, support messages and payment references. It also explains retention, security handling and your route to request access, correction or deletion of personal data connected with your account.

We need contact and verification details to create your account, confirm that the person requesting access is the account holder and respond to account questions. The same details help us keep a wallet-status request attached to the correct profile.

Yes. The policy covers transaction references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use these references to reconcile a receipt or status, and you should not send wallet passwords or one-time security codes.

Contact our support path and state that you are making a Privacy Policy data request. Provide your registered contact detail and the record you want to access. We may complete an account check before sharing personal information with you.

Yes. Send support the incorrect field, the accurate replacement and your registered account detail. We may ask for verification before editing the profile. Payment references may require a separate check when they are tied to DANA, QRIS or a bank receipt.

Cookies can keep a browser session connected while you move between login, the Privacy Policy and account pages. You can change browser settings, but blocking session cookies may sign you out or trigger another verification step when you return.

Yes. It applies when you access your account from a mobile browser, tablet or desktop. Device and login signals may be recorded for security, while your account remains linked to your verified login rather than to a shared device.