Reference

koko33 Privacy Policy And Your Account

Our Privacy Policy explains what koko33 collects when you create an account, sign in, use the lobby or check wallet status.

Account dataWallet checksCookie choicesAccess requests
Explore Our Lobby Read FAQ
koko33 koko33 Privacy Policy And Your Account
CONTACT PATHS

Get Privacy Policy Help Near Login

A clear contact route matters when you need a copy of your data, a correction or an explanation of wallet records. Start from the support contact shown beside the account and cashier path, then include the phone number on your account and the request you want us to assess. We use those details to locate the right record without asking you to send a password.

Team online

Account access

If a sign-in check stalls, contact support through the account path and describe the device involved. We can explain which account data is being used for verification without requesting your password.

Wallet record

For DANA, OVO, GoPay or QRIS questions, send the transaction reference and payment rail shown in your account. We use the reference to check status while limiting unnecessary personal details.

Privacy request

Ask for access, correction or removal through support and state the exact request. We may verify account ownership by phone before changing records, especially when the request affects account security.

HANDLING DETAILS

What We Do With Your Data

Privacy controls work best when they match real account steps. We separate sign-in checks from lobby activity, use payment references rather than wallet credentials where possible, and keep request handling tied to…

Account records

We use your phone number and verification result to create and protect account access. These records can also help us identify the correct account when you ask for a copy or correction.

Device signals

Browser, operating system and sign-in event details help us spot unusual access. On mobile, these signals support the path from login to the lobby without exposing your wallet password.

Payment references

DANA, OVO, GoPay and QRIS status records show whether an account action is pending or matched. We use the payment reference and status, not a request for your wallet PIN.

Cookie controls

Session cookies keep you signed in during an active visit, while preference cookies can remember selected settings. You can adjust browser cookie controls, though some account steps may then need repeating.

Retention choices

We keep account, security and payment records for as long as needed for operations, dispute handling or legal duties. When no longer needed, records are removed or changed so they no longer identify you.

Change requests

Send a request through support with your account phone number and the specific correction or deletion sought. We check ownership first, then explain the result where local law permits.

Privacy Policy Questions For koko33

These Privacy Policy answers cover the questions we expect before account creation or a wallet action. They explain what we collect, why we use it and how you can contact us. If your request concerns local access, eligibility depends on local law, and support may need to confirm account ownership before sharing records.

It covers account details, phone verification, device signals, cookies, lobby activity and payment status records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Yes. The Privacy Policy explains that phone verification helps create and protect your account and lets us confirm ownership before handling access, correction or deletion requests.

We use browser, operating system and sign-in event details to identify unusual access and protect your account. These signals support the mobile login path without requiring your wallet PIN.

Our Privacy Policy focuses on payment references and status records for DANA, OVO, GoPay and QRIS. We do not ask you to provide a wallet PIN through support.

Contact support through the account path, include your account phone number and ask for an access copy. We may verify ownership first, then handle the request where local law permits.

Yes. State whether you want a correction or removal and identify the relevant account record. We assess the request against security, operational and legal needs before confirming the outcome.

We retain account, security and payment records only as long as needed for operations, disputes or legal duties. After that, we remove or anonymise them through our internal process.

Related Pages

koko33 Indonesia Account information VIP Baccarat About Us koko33 Casino