Reference

Privacy Policy for colokan t Accounts

Our Privacy Policy explains how colokan t handles the details connected to your account, device and wallet activity before you enter the lobby.

Account clarityWallet awarenessPhone verificationIndonesia access
colokan t Privacy Policy for colokan t Accounts
CONTACT ROUTES

Privacy Policy Help When You Need It

A clear contact route matters when you want to ask about the Privacy Policy or correct an account detail.

Account help Use the account help path for questions about data held under your login, phone verification or a request to change inaccurate details. We may ask you to confirm the account step connected to the request before discussing private records.
Wallet questions For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference and approximate time rather than wallet passwords. We use those details to locate the relevant status without exposing unrelated account activity.
Policy requests Ask through our available support contact when you want a copy, correction or explanation under this Privacy Policy. We review the request against your account details and may need phone verification before making a change.
DATA PRACTICES

Inside colokan t Privacy Controls

We keep the Privacy Policy practical by tying each data use to an account action you can recognise.

Account records

When you open an account, we retain the details needed to identify that account and connect phone verification with access. We do not ask you to place a password in a support message, and we use account checks before discussing private records.

Device signals

Your browser and device can provide session details such as access time, device type and technical identifiers. These records help us investigate repeated login errors or unusual access without treating every device change as a policy breach.

Cookie controls

Cookies can keep your account session active and help us trace a page or lobby loading issue. You can manage browser cookie settings on your device, although turning them off may require another login or affect account access.

Wallet references

Payment records may include a DANA, OVO, GoPay or QRIS reference, plus bank transfer or virtual account details needed to match status. We use these references for reconciliation and support rather than requesting your wallet password.

Retention checks

We retain account, security and payment records only for as long as needed for the stated account purpose, dispute handling and required records. When a record is no longer needed, our handling follows the deletion or anonymisation process available for that record.

Change requests

You can ask us to correct account data, explain a data use or provide the records available under this Privacy Policy. Include your account reference through support; phone verification may be required before we act on the request.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain which account and device details may be used, how wallet references are handled and where to send a request. If your situation is not covered, contact account help with the smallest set of details needed to locate your record. Access depends on local law.

The colokan t Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references. It explains why we use those details for access, security, wallet matching and account help, including records connected with DANA, OVO, GoPay and QRIS.

We may collect details needed to open and maintain your account, including contact details, phone verification results and account activity needed for security. Support messages and payment references can also be retained when they help us resolve access, receipt or wallet-status questions.

Yes. The Privacy Policy includes technical session details from the phone, computer or browser you use to reach the account. Device type, access time and similar signals can help us investigate login errors or unusual sessions, while browser cookie settings remain under your control.

We use payment references to identify whether a DANA, OVO, GoPay or QRIS request matches your account and to answer a status question. We may also use bank transfer or virtual account references for reconciliation, but you should never send a wallet password.

You can contact account help to ask what records are available, request a correction or ask why a detail is used. Include your account reference and the specific change. We may complete phone verification before discussing or changing private account data.

We keep account, security and payment records for the period needed for the stated account purpose, support disputes and required record keeping. The exact period can differ by record type. When retention is no longer needed, the record follows our deletion or anonymisation process.

Send your question through the available support contact and identify it as a Privacy Policy request. Add your account reference, but leave out passwords and full wallet credentials. Our support path can explain data use, access requests, corrections and payment-record handling.