Reference

Privacy Policy for polo 188 Accounts

polo 188 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet recordsCookie choicesAccess requests
polo 188 Privacy Policy for polo 188 Accounts
CONTACT YOUR WAY

Get Privacy Help Beside Your Account

A clear contact route matters when you want to ask about a Privacy Policy request rather than a wallet transaction.

Account route Open the support path from your signed-in account when you need to ask what…
Payment record For a DANA, OVO, GoPay or QRIS privacy question, include the payment date and…
Access request If you want a copy, correction or deletion assessment, state the request plainly through…
DATA HANDLING

What We Do With Your Account Details

Privacy controls work best when they match the real account journey. We separate sign-in details, wallet references, device signals and support messages so each record is used for a stated purpose.

Collection points

We receive details when you create an account, verify your phone, sign in, contact support or submit a wallet request. Technical signals can include device type, browser version, IP-related access data and session timestamps used to protect account entry.

Use of records

Account details support sign-in, phone verification, wallet matching and responses to your privacy questions. Activity records can help us investigate an unusual login or a failed access attempt without turning those records into unrelated marketing material.

Cookie controls

Cookies can keep a signed-in session working and remember selected settings on your mobile browser. You can review cookie controls in your browser menu; switching some cookies off may affect account access or require you to sign in again.

Account protection

Never send us your password, one-time code or complete wallet credentials in a support message. We use the account step and phone verification details to confirm that a privacy request comes from the person connected with the profile.

Retention approach

We keep records only while they serve the account, payment reconciliation, security or legal purpose for which they were collected. Retention can vary by record type, including QRIS receipts, login events and support correspondence.

Change requests

To request access, correction or deletion assessment, contact us through the support route shown in your account. Tell us which record concerns you; we will verify the request, explain any legal restriction and respond through the available account contact.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the account questions you are most likely to have before opening access or sending a wallet request. We keep the wording practical: what we collect, why a phone check may appear, how cookies work on mobile and where to send a data request. Access remains subject to local requirements, and any eligibility depends on local law.

The polo 188 Privacy Policy covers account details, phone verification, device and session records, cookie use, support messages and payment references from DANA, OVO, GoPay or QRIS. It explains why we use each category, how retention works and how you can request access or correction.

We use your phone number to create and protect the account, complete the account access step and connect a privacy request with the right profile. A phone check can also help us avoid discussing private account records with an unrelated person.

Yes. The Privacy Policy covers payment references and receipt details that help us match a DANA or QRIS request with your account. We use those records for wallet status, reconciliation, security and support, and you should share only the visible reference needed for a query.

You can ask for access to the personal details connected with your account through the support path shown after sign-in. Tell us the account phone number and the record you want checked. We may verify your identity before releasing private account data.

Cookies can retain a session and selected settings when you open the lobby through a mobile browser. Your browser menu provides cookie controls. If you block required cookies, you may need to sign in again or lose parts of the account path.

Send a correction request through the account support route and identify the detail that needs changing. We may ask for phone verification or another account check before editing it. Payment references such as BCA, BRI, Mandiri or BNI records may require reconciliation checks.

You may request a deletion assessment through the listed support path. We review the request against account safety, payment reconciliation and applicable legal duties. Some records may need to remain for a stated period, and we will explain the relevant reason where local law permits.