Reference

Privacy Policy for Your cola99 Account

Our Privacy Policy explains how cola99 handles the details you provide when you open an account, verify your phone, enter the lobby or check a wallet status.

Clear data purposesWallet record contextPhone verificationAccess depends on local law
cola99 Privacy Policy for Your cola99 Account
HELP PATHS

Privacy Questions Reach Our Account Team

A clear contact path matters when your Privacy Policy question concerns a login, phone check or wallet record.

Account access If your phone verification or login detail looks wrong, use the account support route and identify the affected account step. We use the details you send to locate the request and avoid changing data on an unrelated account.
Wallet records For a DANA, OVO, GoPay or QRIS record, include the payment name and visible status rather than sharing a wallet password or full security code. We use that limited context to check the account record tied to your request.
Policy requests To ask about access, correction or removal of eligible account data, state the request clearly through our account contact path. We may ask for phone verification before acting, so your personal details are not released to the wrong person.
DATA PRACTICE

How We Apply Privacy Policy

We apply this Privacy Policy at the points where your account creates a record: phone verification, login, wallet selection, lobby access and support contact.

Account data

We handle your phone number, verification state and account activity to provide account access and protect against mistaken or unauthorised changes. We use the minimum context needed to connect a request with the correct cola99 account.

Cookies and sessions

Cookies and session markers help the site remember a requested page, keep a login flow connected and detect unusual device behaviour. You can manage browser storage settings, but changing them may interrupt phone verification or account access.

Wallet records

When you select DANA, OVO, GoPay or QRIS, we may record the method and status needed to match account activity. We do not need your wallet password for that check, and you should never send it through support.

Account security

Phone verification provides an account step before access and helps us assess requests involving login details. If a device path appears unusual, we may ask for further confirmation before changing personal data or releasing account details.

Retention

We keep account and support records only for the period needed to provide the service, protect the account, resolve a payment-status question or meet a valid legal requirement. When a record is no longer needed, our handling follows the policy purpose.

Your requests

You can ask what personal data we hold, request a correction or ask how a record is used through the account contact route. We verify the request first, then explain any limits that depend on local law or an active account duty.

Privacy Policy Answers for cola99

These Privacy Policy answers address the account questions you are most likely to have before opening or using cola99 in Indonesia. They cover phone verification, wallet records, cookies, device access, data changes and contact requests. If your situation is not listed, use the account support route and describe the specific record or step you want us to check.

It covers account details, phone verification, login activity, device signals, cookies, wallet method and status records, plus messages sent through account support. We use those details for access, security, payment-status checks and policy requests, subject to local law.

Phone verification links an account request to the right person and helps us protect login and data changes. It may be required before we discuss personal records or update account details, and access depends on local law.

Yes. The Privacy Policy includes the DANA, OVO, GoPay or QRIS method and status connected with your account activity. We use that context to match a cashier record, not to request your wallet password or private security code.

Cookies and session markers help connect your login, requested page and device session. You can adjust browser settings, but blocking necessary storage may interrupt phone verification or prevent the account path from working as intended.

Yes. Send a clear correction request through the account contact route and identify the affected detail. We may ask for phone verification before making a change, then explain any restriction that depends on local law or an active account duty.

We retain records for the period needed for account access, security checks, payment-status questions, support handling or a valid legal requirement. The Privacy Policy purpose controls retention, and records are handled further when they are no longer needed.

Use the account support route and include the request type, relevant date and the phone number linked to your account. Do not send wallet passwords. We verify identity before discussing or changing personal data.