Reference

Privacy Policy For Your 0lxtoto Account

0lxtoto Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record checksDirect account requests
Explore Our Lobby Read FAQ
0lxtoto Privacy Policy For Your 0lxtoto Account
PRIVACY SUPPORT

Get Help With A Privacy Policy Request

A clear support route helps when your Privacy Policy question involves a phone check, wallet record or device sign-in.

Account request Use the support path displayed after account sign-in when you want to ask about your personal data. We may ask for the phone verification step already linked to your profile, helping us avoid discussing private records with the wrong person.
Wallet receipt For a DANA, OVO, GoPay or QRIS privacy query, provide the payment reference and date rather than a wallet password. Our support team can use that receipt detail to locate the relevant account record and explain its handling.
Device access If a phone or browser still shows an old sign-in, tell us which device path you used and whether the issue followed account verification. We can identify the access record connected to your profile and explain the next privacy step.
DATA HANDLING

What 0lxtoto Records And Protects

Privacy Policy choices are easier to use when each data purpose is visible. We separate account details from payment references, limit support checks to the record being discussed and use security signals…

Account details

We collect details needed to create and maintain your account, such as a phone number, verification result and settings you choose. The Privacy Policy ties these fields to account access and support handling, rather than treating every device detail as a profile attribute.

Payment references

A DANA, OVO, GoPay or QRIS transaction can produce a reference, amount status and time record. We use that narrow payment context to match account activity, investigate a receipt question and separate an unresolved status from a completed wallet event.

Cookies

Cookies and similar device markers can remember sign-in state, preserve a selected page and help us detect unusual account access. You can manage browser cookie settings, but removing required cookies may mean repeating the phone verification step.

Account security

We use account signals such as device type, sign-in time and verification state to protect your profile. Keep one-time codes private, sign out on shared phones and contact support through the account path if a session looks unfamiliar.

Retention

We keep personal records only for the period needed for the stated purpose, account support, payment reconciliation or a legal duty where local law permits. Retention can differ by record type, so a receipt reference may remain after a device session ends.

Change request

To request access, correction or deletion, use the support channel shown in your account and identify the record clearly. We may verify your phone before responding, then explain what can be changed and any reason a record must remain.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover data collection, wallet references, device behaviour, access requests and contact steps for people using the service in Indonesia. Where an answer depends on a legal or payment requirement, we say so directly. Check the full policy page again after a material change to account or wallet handling.

The 0lxtoto Privacy Policy covers account details, phone verification, device and session data, cookies, payment references and support requests. It explains why we use each category, how security checks work and how you can ask for access, correction or deletion where local law permits.

Yes. When you use DANA or QRIS, we may retain a payment reference, status and timestamp to match the transaction with your account. We do not need your wallet password for that check. The same approach applies to OVO, GoPay, bank transfer and virtual account records.

Phone verification connects an account request to the person asking for access and helps us reduce mistaken or unauthorised changes. It can also be used when you ask about a private record through support. Keep one-time codes private and never place them in a receipt message.

The Privacy Policy allows us to record practical device signals such as browser type, sign-in time and session status. These details help us protect your account and investigate an unfamiliar login. Clearing cookies can end a remembered session and require phone verification again.

You can request a correction through the support channel shown after you sign in. State which account detail is wrong and provide only the minimum identifying material requested. We may confirm your phone verification before making a change, and we will explain any restriction where local law permits.

Retention depends on the type of record and its purpose. A device session may end quickly, while a DANA receipt reference, bank transfer record or account support case may need to remain for reconciliation, security or a legal duty where local law permits.

Start with the support route displayed in your signed-in account and describe whether you need access, correction, deletion or an explanation of a payment record. For a faster check, include the relevant date and reference, but never send a wallet password or one-time code.

Related Pages

0lxtoto Indonesia Access guide bolajaya About Us Account information