Reference

lexustoto Privacy Policy For Account Access

The lexustoto Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier.

Account clarityWallet recordsCookie choicesContact route
lexustoto lexustoto Privacy Policy For Account Access
CONTACT THE TEAM

Privacy Help Beside Your Account

A clear contact path matters when a privacy question appears during login or a wallet check.

Account support route Open the support link from your signed-in account and select the privacy subject. This gives us the account context needed to check a DANA, OVO, GoPay or QRIS reference without asking you to post sensitive details in a public message.
Cashier status question If your privacy request concerns a bank transfer or virtual account record, include its reference and date in the account form. We can compare the entry with the wallet status while keeping your password and security code out of the request.
Correction request Ask us to correct an account detail through the same support path. State the field that needs attention and the accurate replacement value; we may ask for an account check before changing contact or verification data.
DATA HANDLING

How We Handle Your Account Data

Privacy is practical when each record has a clear purpose. We separate account access events, wallet references and cookie preferences so a request can be directed to the relevant record.

Account details

We use the contact and verification details you provide to create your account, confirm account access and respond to account requests. If a detail changes, ask for a correction through support and we will check the request against the account record.

Wallet activity

A DANA, OVO, GoPay or QRIS action can create a reference, status and timing record. Bank transfer and virtual account entries may carry similar payment markers, allowing us to trace a cashier issue without storing your wallet password.

Cookies and devices

Cookies can retain session choices, language settings and security signals on the browser you use. If you move from a phone to desktop, the browser may not share every choice; check the privacy controls again on that device.

Session security

Login time, browser details and account activity can be assessed when we detect an unusual access pattern. Never share a password or one-time code with anyone claiming to handle your privacy request; use the signed-in support route instead.

Record retention

We keep account, security and payment-reference records only for as long as needed for the stated purpose, account administration or applicable legal duties. Retention can differ by record type, so ask support which category applies to your request.

Your request route

You can ask what personal data is connected to your account, request a correction or raise a question about cookies. Send the request through account support with your registered contact detail so we can verify the requester before replying.

Privacy Policy Questions Before Account Opening

These Privacy Policy answers focus on the points you may check before opening an account from Indonesia. We explain account records, wallet references, browser behaviour and the support route in direct terms. If your situation depends on local law or a specific verification record, contact us through the account support path rather than sending sensitive details through an unverified channel.

It covers account details, verification entries, login and device events, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains why we use those records and how you can ask about them.

You may provide contact and account details, along with information needed for an access or verification check. We use those details to connect you with your account and respond to requests. Do not include your password or one-time code in a support message.

Yes. A DANA or QRIS action can produce a payment reference, amount, status and time linked to your account activity. OVO, GoPay, bank transfer and virtual account steps may create similar records so we can trace a cashier question.

Cookies may keep a session active, remember selected settings and help assess unusual access. A phone browser and a desktop browser can hold separate choices, so review the privacy controls on each device. You can ask support about a particular cookie choice.

You can ask what account data is connected to your registered contact detail or request a correction through the account support route. Tell us which field or record you mean. We may verify your identity first, and the response depends on local law.

Retention depends on the record category and the reason it was collected. Account, security and payment-reference records may be kept for account administration or applicable legal duties. Ask support about the category involved rather than assuming every record has the same period.

Use the support link inside your signed-in account and choose the privacy subject. Include your registered contact detail and a short description, such as a cookie choice or QRIS reference. Never send your password, one-time code or full wallet credentials.