Reference

to188 Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use, protect and retain the details connected with your to188 account.

Clear data purposesWallet record controlsPhone access checksIndonesia policy access
to188 to188 Privacy Policy For Your Account
PRIVACY HELP PATH

Get Help With A Policy Request

A clear contact path helps you act on the Privacy Policy without guessing which team to reach. Send your request through the account support route and include the phone number or account detail that lets us locate the correct record. We may ask for an account check before discussing private data. If a DANA, OVO, GoPay or QRIS reference appears in your request, include the receipt or status detail, but do not send a password or one-time verification code.

Team online

Data access request

Ask us to identify the personal data linked with your to188 account and explain the purpose connected with it. Include your verified phone detail and a precise request so we can separate your account record from a DANA, OVO or QRIS payment reference.

Correction request

If your account name, phone detail or contact record is inaccurate, contact support with the corrected value and the reason for the change. We will check account ownership before updating the record, helping prevent an unrelated person from changing your privacy details.

Wallet record question

For a payment-status question, share the relevant DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference through the support path. We use that detail to trace the record while limiting the request to the transaction and account data needed to answer it.

DATA CONTROL PRACTICE

What We Do With Your Account Data

Privacy controls work best when each account step has a clear reason. We use the data needed to create access, confirm a phone number, keep a session secure and respond to a…

Account details

We use your account and contact details to create your sign-in path, complete phone verification and respond to account requests. Keeping these fields accurate helps us send privacy responses to the right account holder and prevents confusion when you ask about access or correction.

Device and session signals

When you move from a phone into the lobby or return on desktop, technical signals such as browser, device and session data may be recorded for security and service operation. We use these signals to investigate unusual access rather than to request your private device content.

Cookies

Cookies and similar storage can keep your session, remember selected settings and help us understand whether a page request completed. You can manage browser storage through your device settings, although removing necessary cookies may interrupt sign-in or the account path.

Payment references

A DANA, OVO, GoPay or QRIS reference can connect a payment status with the correct account. For bank transfer and virtual account records, we may retain the reference and reconciliation result. We do not need your wallet password to investigate a receipt or status question.

Retention and deletion

We retain account, security and transaction records only for as long as needed for the stated purpose, account protection or applicable legal duties. You may request deletion of eligible data, but some records may remain where retention is required or necessary to resolve a dispute.

Policy changes

If the Privacy Policy changes in a meaningful way, we will publish the updated wording on this page and show the current date or version where available. Check this page before opening an account or sending a new request, especially after a change to contact or retention details.

Privacy Policy Answers For to188

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data collected during phone verification, the records linked with DANA and QRIS, device access, cookies, retention and requests for copies or corrections. If your situation is not covered, use the account support path and describe the exact record or policy question. Access depends on local law, so we may need to confirm the applicable region before responding.

The to188 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages, security events and payment references. It explains why we use each category, how long records may remain, and how you can request access, correction or deletion of eligible data.

Yes. The Privacy Policy covers DANA and QRIS references connected with your account, along with OVO, GoPay, bank transfer and virtual account references. We use these records to match payment status and answer receipt questions; we do not need your wallet password for that check.

During phone verification, we may collect your phone number, verification result, account identifier, time of the request and security signals linked with the session. We use these details to confirm account access and investigate unusual attempts, not to read private content stored on your phone.

You can send a data access request through the account support path. State that you are asking under the Privacy Policy and include the verified phone detail or account identifier. We may complete an ownership check before sharing records, so private data is not disclosed to another person.

Contact support with the account field that needs correction, the accurate replacement and a short explanation. We may ask for phone verification or another account check before making the change. Payment references such as DANA or QRIS receipts should remain unchanged unless the correction concerns your account linkage.

We keep account, security and payment records for the period needed for their stated purpose, account protection, dispute handling or applicable legal duties. The exact period can differ by record type. You may ask support whether a particular record is eligible for deletion.

Cookies may keep your session active, remember settings and help us confirm that a page request worked. You can manage them through your browser or device settings. Necessary storage may still be needed for sign-in, and removing it can interrupt account access or policy requests.