Reference

lexitoto Privacy Policy for Your Account

Our Privacy Policy explains how we handle your account details, device activity and payment references when you use DANA, OVO, GoPay or QRIS.

Account clarityWallet referencesCookie choicesPhone verification

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

lexitoto Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy describes how we receive, use and protect details connected with your lexitoto account. That can include your phone number, verification result, login records, device type, browser signals, support messages and payment references such as a DANA, OVO, GoPay or QRIS status. We use

1
these details to provide account access, identify unusual sign-in activity, reconcile a receipt and answer a wallet-status request. We do not treat a payment reference as permission to view the contents of your personal wallet. If you use bank transfer or a virtual account, we may
2
retain the reference needed to match the account event. Access and eligibility depends on local law, and our policy applies where local law permits. The current policy is available from the privacy link connected to your account area.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Privacy Questions Through Account Support

A clear contact route helps when you want to ask about a record, cookie or account detail.

Account privacy request Use the support channel inside your account to ask which personal details are linked to your phone verification. We may ask for an account step to confirm that the request comes from you.

Wallet reference check Send the transaction reference and payment rail when a receipt needs matching. We check the event without requesting your wallet PIN, full banking password or unrelated wallet contents.

Access concern If a device or login record looks unfamiliar, contact us through the account support path and describe the device used. We can review the sign-in context and advise the next account-security step.

HANDLING DETAILS

How We Manage Cookies and Account Data

Our handling practices are designed around the points where your account creates a record: login, phone verification, wallet status and support contact.

Account records

We keep the contact and verification details needed to open and maintain your account. Phone verification helps us connect a privacy request with the correct account rather than exposing another person’s records.

Device signals

Browser type, device details and sign-in time can help us spot an unfamiliar access attempt. These signals support account protection and are not treated as the contents of your personal device.

Cookie controls

Cookies can remember session settings and help the account path load correctly. You can manage browser cookie controls, though restricting essential cookies may interrupt login or the page used to reach policy settings.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account events, we use payment references and status details needed for account reconciliation. We do not ask for wallet PINs through support.

Retention timing

We retain account, security and payment records only for the period needed for the stated account, support and legal purposes. When a record is no longer needed, our handling process removes or separates it.

Changes and contact

You can ask us to correct an inaccurate account detail or explain a processing purpose through the support channel shown after login. We may verify your phone-linked account before making a change.

Privacy Policy Answers for lexitoto Accounts

These Privacy Policy answers focus on the account and payment questions you may have before opening access. They cover the data connected with phone verification, device use, cookies, local wallets and requests made through our support path, with access where local law permits.

It covers account details, phone verification, login activity, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account events.

Phone verification helps connect account access and privacy requests to you. It also gives us an account signal when a login or wallet-status question needs checking through support.

Yes. It explains our use of payment references and status details for DANA, QRIS, OVO and GoPay. We use those details to match an account event, not to view your wallet contents.

Device signals help identify unusual sign-ins, while essential cookies help maintain your session and policy access. Browser cookie controls remain available, but blocking essential cookies can interrupt login.

Yes. Contact us through the support channel shown after login and describe the detail needing correction. We may confirm your phone-linked account before changing or explaining the record.

We keep payment and account-security records for the period needed for reconciliation, support and legal purposes. This can include a receipt reference for a DANA, QRIS or bank transfer event.

Use the account support path and include the request type, such as cookie access, account correction or wallet-status data. Do not send your password, wallet PIN or full banking credentials.

lexitoto Privacy Policy for Your Account

Privacy Questions Through Account Support

How We Manage Cookies and Account Data

Account records

Device signals

Cookie controls

Payment references

Retention timing

Changes and contact

Privacy Policy Answers for lexitoto Accounts

01 What does the lexitoto Privacy Policy cover?

02 Why does lexitoto need phone verification?

03 Does the Privacy Policy include DANA and QRIS data?

04 How does lexitoto use device and cookie data?

05 Can I request a correction to my account data?

06 How long does lexitoto keep payment references?

07 Where can I ask about a Privacy Policy request?

Related Pages