Reference

lexus288 Privacy Policy for Indonesia Accounts

lexus288 Privacy Policy explains how we handle your account details, mobile-browser activity and wallet records when you open access to Dragon Tiger, Rocket Crash or other lobby areas.

Account dataWallet recordsMobile accessPolicy requests
lexus288 lexus288 Privacy Policy for Indonesia Accounts
CONTACT ROUTES

Get Privacy Policy Help From Your Account

A clear contact route matters when a data question affects your account or wallet record.

Account request Open the account support path and ask what personal details are stored, why they…
Wallet record For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, include the…
Access correction If your phone number, device detail or account name needs correction, send the old…
HANDLING DETAILS

Six Practical Privacy Policy Commitments

Privacy Policy choices are easier to assess when each handling step has a practical purpose. We separate account administration from payment matching, keep security events for account protection and use access controls…

Account collection

We collect the details needed to create and maintain your account, including a phone number and verification result. Optional details are treated separately where the account flow identifies them as optional.

Cookie choices

Our site may use browser storage or cookies to keep a session working and remember selected settings. You can clear browser data on your mobile device, though this may require another account sign-in.

Security controls

We use sign-in events, device signals and phone verification to help detect unusual access. Never send a password, wallet PIN or one-time code through a support message or payment request.

Payment matching

DANA, OVO, GoPay and QRIS references are used to match a wallet event with the correct account. Bank transfer and virtual account details support the same reconciliation step.

Retention period

We keep personal and transaction records for the period needed to operate the account, answer disputes, protect access and meet applicable obligations. Records are removed or restricted when that purpose ends.

Change requests

You can request access, correction or deletion where available by contacting support from the account route. We may verify your phone before releasing, amending or restricting personal details.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear most often before account creation. They cover what we collect, how wallet references are used, how mobile sessions work and how you can ask for a copy or correction of your records.

It covers account details, phone verification, device and browser signals, security events, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create the account, complete the required verification step and help protect sign-in access. We may use it to match a support request with the correct account record.

Yes. The policy covers session details, device type, browser signals and security events from a mobile browser or desktop session. Clearing cookies can sign you out and start a fresh session.

We use the transaction reference, amount and status needed to match a DANA or QRIS event with your account. We do not ask for your wallet PIN or full wallet credentials in support messages.

You can contact us through the account support route and request access to personal details connected with your account. Include your phone number and request subject; phone verification may be required.

Send the requested correction through support, identifying the detail and the new value. We compare the request with your account record before making a change, especially for phone or payment-linked details.

We retain payment references only for account administration, reconciliation, dispute handling, security and applicable obligations. When those purposes end, we remove, restrict or anonymise the relevant record where appropriate.