Reference

olxtoto alternatif Privacy Policy

olxtoto alternatif Privacy Policy explains how we handle the account details behind your mobile lobby access, including phone verification and wallet records for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPolicy requests
olxtoto alternatif olxtoto alternatif Privacy Policy
CONTACT PATHS

Where Privacy Questions Meet Support

A clear contact path helps when you want to ask what a record means or request a correction.

Account help route Use the account help route when your phone verification record, sign-in device, or account…
Wallet status request For a DANA, OVO, GoPay or QRIS record, send the payment reference through the…
Policy clarification If a Privacy Policy paragraph is unclear, contact us from the signed-in account menu…
HANDLING YOUR DATA

How We Protect Account Data

We treat account data as part of the access process rather than as a public profile. Our handling separates sign-in checks, wallet references, device signals, and support messages so each request has…

Data collected

We may collect your phone number, account identifier, sign-in timestamps, device details, connection data, payment reference, and messages you send to support. Phone verification before account access helps us connect these records to the correct account instead of relying on an unverified request.

Cookie controls

Cookies and similar browser storage can remember a session, protect the account flow, and retain a policy choice. On mobile or desktop, you can clear browser data through your device settings; clearing it may sign you out and require phone verification again.

Account security

We use sign-in checks, phone verification, session controls, and device signals to reduce account misuse. Never share a verification code or wallet password with support. If a sign-in looks unfamiliar, use the account help route before changing payment details.

Payment records

A DANA, OVO, GoPay or QRIS reference may be retained to reconcile a cashier request, while bank transfer and virtual account records help identify the matching account entry. We do not need your wallet password to check a receipt status.

Retention period

We retain account, security, support, and payment records only for the period needed for account operation, fraud checks, dispute handling, and legal duties. When a record no longer has a valid purpose, we delete it, anonymise it, or restrict its use.

Change requests

You may ask us to correct an inaccurate phone detail, account record, or support entry through the signed-in policy request form. We may verify ownership first, then explain whether the change is possible where local law permits and what record remains necessary.

Privacy Policy Questions About Your Account

These answers address the searches we hear most often before account access. Each response stays focused on how our Privacy Policy applies to Indonesian account, device, and payment records.

It covers account details, phone verification, device and connection signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It also explains retention, security, correction requests, and access conditions where local law permits.

Phone verification helps us confirm that the person requesting account access or a data change controls the registered contact. It also lets us connect sign-in, support, and payment records to the right account instead of releasing details after an unverified request.

We may store a payment reference, amount status, channel name, timestamp, and account match for DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. We do not need your wallet password to locate a receipt or explain a cashier status.

Open the policy link from your signed-in account menu, choose the request path, and describe the inaccurate record. Include the registered phone number only in the protected form. We may verify ownership before correcting the detail where local law permits.

Yes. The policy applies when you use a mobile browser to sign in, complete phone verification, open the lobby, or contact support. Browser cookies may keep a session active; clearing browser storage can sign you out and trigger another account check.

Retention depends on the purpose of each record, such as account operation, security checks, payment matching, dispute handling, or legal duties. We remove, anonymise, or restrict records when the purpose ends, subject to duties that depend on local law.

Use the signed-in account help route for questions about personal data, cookies, phone verification, retention, or correction. For DANA, OVO, GoPay and QRIS references, use the cashier status path and include the receipt reference inside that protected request.