Reference

lexustoto Privacy Policy For Your Account

lexustoto Privacy Policy explains how we collect, use, secure and retain the details connected with your account, including phone verification and wallet activity.

Clear data purposesWallet record controlPhone verification
lexustoto lexustoto Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Near Your Account

A clear contact route helps you act on our Privacy Policy without searching through the lobby. Tell us which account step concerns you, whether the matter involves phone verification or a wallet receipt, and what change you want us to check. We use the details you provide to locate the relevant record, while avoiding requests for your full password or one-time code. This keeps a privacy question separate from general game browsing.

Team online

Account access

When a phone verification record looks wrong, contact our support desk with your account phone number and the date of the attempt. We can check the access event without asking you to send a password or one-time code.

Wallet records

For DANA, OVO, GoPay or QRIS questions, include the payment reference and wallet name rather than sharing a wallet password. We use that reference to match the receipt, status event and account record.

Data requests

To request a correction, copy of available account data or deletion check, state the request clearly and use the contact route attached to your account. We may ask for phone verification before changing private records.

DATA PRACTICE

What We Do With Your Account Data

The practical controls behind our Privacy Policy are visible in ordinary account steps: phone verification before access, device checks during sign-in and payment references attached to wallet activity.

Collection

We collect details you submit for account creation, such as your phone number, plus sign-in events, device signals and payment references. We limit collection to what helps provide access, check account ownership and investigate a wallet status question.

Use

We use account and transaction records to complete verification, connect a payment reference to the correct account and respond to support requests. We do not turn a privacy request into a request for your password or wallet credentials.

Cookies

Cookies and device storage can preserve a login session, remember a selected language or help us identify an interrupted account step. Your browser controls can remove them, although a cleared session may require phone verification again.

Security

Phone verification, sign-in event checks and restricted staff access help protect account records. Keep your password and one-time code private, and contact support if a device you do not recognise appears in your access history.

Retention

We retain account, verification and payment-reference records for the period needed for account operation, security checks or legal duties. When a record is no longer needed for those purposes, we assess it for removal or de-identification.

Changes

If your phone details, identity record or account data needs correction, send a clear request through support. We may verify ownership first, then confirm whether the requested change can be made under local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions we hear most often from Indonesian customers. They explain what to prepare when you ask about a record, how wallet references are treated and what access wording applies. If your question is not listed, use the support path with the smallest useful set of details.

The lexustoto Privacy Policy covers account creation, phone verification, sign-in events, device details, support messages, cookies and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and verify the account, connect later sign-in attempts with the right record and help support check ownership. Keep one-time codes private; support will not need the code itself.

We use the payment reference, wallet name and status event to match a DANA or QRIS action with your account. We do not ask for your wallet password. Share only the receipt details needed for the check.

Yes. Send a clear request through the account support path, identify the record you want copied or corrected and provide the relevant date. We may complete phone verification before releasing or changing private account data.

We keep account, verification and payment-reference records while they support account operation, security checks or legal duties. We then assess whether the record can be removed or de-identified, where local law permits.

Yes. The Privacy Policy also covers mobile sign-in, device signals, cookies and phone verification. Clearing browser storage may end your session, so you might need to verify your phone again on the next login.

Access and eligibility depends on local law. If a local restriction affects your account, contact support with your location and account issue. We can explain the available privacy and account process without asking for unnecessary personal details.