Reference

lexustoto Privacy Policy for Your Account

The lexustoto Privacy Policy shows what we collect when you open an account, verify your phone, use DANA or QRIS, and access the lobby from a mobile browser.

Account clarityWallet data careMobile access contextLocal law applies
lexustoto lexustoto Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact route matters when you want to ask about your data rather than a wallet status.

Account support path Use the support link inside your account area for a Privacy Policy question. Include your registered phone number so we can confirm which account record your request concerns.
Wallet record query If your request concerns DANA, OVO, GoPay or QRIS references, mention the transaction date and rail. We use those details to find the correct account record without asking for an account password.
Access concern For a sign-in or phone-verification concern, describe the device path, such as Android browser or desktop browser. We can focus the privacy response on the relevant session record.
HANDLING PRACTICES

Six Ways We Handle Your Data

We keep the practical side of this Privacy Policy visible because your account journey creates different kinds of records.

Account details

We use your phone number and account details to create access, complete phone verification and respond to account requests. Keeping these fields accurate helps us connect your privacy question to the right record.

Payment references

DANA, OVO, GoPay and QRIS references help us reconcile an account request. We treat these references as account records and do not need your wallet password to investigate a status question.

Cookies

Cookies and similar browser storage can retain sign-in preferences, session continuity and basic page measurements. You can manage browser storage through your device settings, though some account steps may then need repeating.

Account security

We use phone verification, session signals and sign-in checks to reduce unauthorised account access. Never send your password in a support message, even when asking about a Privacy Policy request.

Retention approach

We retain records for as long as needed for account operations, support history, security checks and applicable legal duties. When a record is no longer needed, our handling process moves it toward removal or restriction.

Change requests

You can ask us to correct account details, explain a data use, provide available access to your records or address a deletion request. We may verify ownership before making a change.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account questions you are most likely to ask before opening access. They cover data collection, wallet references, cookies, corrections and contact steps, with account ownership checks used where a request could affect your records.

It covers account details, phone verification, sign-in and device signals, support messages, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create an account path, complete phone verification and identify the correct record when you contact support about access or a Privacy Policy request.

Yes. It covers references needed to match an account request with QRIS, DANA, OVO or GoPay activity. We do not ask for your wallet password when checking those references.

Use the support path inside your account and state whether you want a correction, an explanation of use, available access to records or a deletion request. We may confirm account ownership first.

Cookies and browser storage may support sign-in continuity, preferences and basic page measurement. You can manage them in your browser settings, but turning them off may require repeated account steps.

We keep records for account operations, support history, security checks and applicable legal duties for as long as needed. Records no longer needed move toward removal or restricted handling.

Access and eligibility depends on local law. Our Privacy Policy describes handling for the website and account pages, while payment services and other linked services may apply their own privacy terms.