Reference

How lancar138 Privacy Policy handles account data

Our Privacy Policy explains what we collect when you open an account, sign in on mobile, check DANA or QRIS status, and contact support.

Account dataWallet recordsCookie choicesAccess requests
Browse Our Lobby Read FAQ
lancar138 How lancar138 Privacy Policy handles account data
HELP WITH YOUR DATA

Get a clear answer about Privacy Policy

A data question should not leave you searching through account screens. We provide a support route connected to the cashier area, so you can explain a correction, access or deletion request while referring to the relevant wallet record. Include your account contact and the date of the event; we can then match the request without asking you to send a full password or private wallet PIN.

Team online

Account data requests

Use our support route beside the cashier when you want a copy, correction or explanation of account data. We may ask for account details to confirm that the request comes from you.

Wallet record questions

For DANA, OVO, GoPay or QRIS records, mention the payment rail, amount reference shown in your account and approximate date. Do not send your wallet PIN or full sign-in password.

Access concerns

If a login or phone-verification step appears unusual, contact support through the account path before sharing more details. We use the available account signals to assess the request securely.

YOUR DATA CONTROLS

Privacy choices for every account step

We treat privacy as an account process rather than a single checkbox. The same controls apply when you browse on a phone, move from login to the lobby, or return on desktop…

Account details

We collect details needed to create and maintain your account, including contact information and phone-verification status. We use these records to confirm access, respond to requests and protect the account from misuse.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can create a reference, status and timestamp. We use those fields to match account activity without requesting your wallet PIN.

Device signals

Your browser, device type, session time and security events may be recorded when you sign in. These signals help us identify unusual access across a mobile phone and desktop browser.

Cookie settings

Cookies can keep sign-in flow, language choices and security checks working between pages. You can adjust cookie controls in your browser, although restricting them may interrupt account access or verification.

Retention periods

We retain records while they support account operation, security checks, disputes or legal duties. When a record no longer serves one of those purposes, we remove it or reduce it to a non-identifying form.

Requesting changes

Ask us to access, correct or remove personal data through the support path near the cashier. We may verify your account contact first, and we will explain any action that depends on local law.

Privacy Policy answers for lancar138 accounts

These Privacy Policy answers address the searches we hear most often before account access. They cover the records created by phone verification, wallet checks, cookies, mobile sessions and support requests, so you can decide what to share and how to ask for a change.

We may collect account contact details, phone-verification status, device and browser signals, cookie choices, support messages and payment references linked to DANA, OVO, GoPay, QRIS or bank transfers.

Phone verification helps confirm that the person requesting account access is connected to the account contact. We use its status for access and security checks, not as a request for your private wallet PIN.

We record the payment rail, reference, status and time needed to match an account event. These details help resolve a cashier question, while your wallet PIN and private wallet credentials should remain with your payment provider.

Yes. Send an access request through the support path beside the cashier and include your account contact. We may verify ownership before sharing records, and the response depends on local law.

Tell support which account detail is inaccurate and provide the corrected value. For a payment reference, include the rail and date rather than a wallet PIN, so we can locate the right record safely.

Cookies may support sign-in flow, security checks and saved choices when you browse on a phone. Your browser controls them, but blocking required cookies can interrupt verification or account access.

We keep records while needed for account operation, security, disputes or legal duties. After that need ends, we remove or anonymise them, subject to retention requirements that depend on local law.

Related Pages

lancar138 Indonesia Live Roulette About Us Access guide Great Rhino