Reference

koko11 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a koko11 account, use the Live Dealer Lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesCookie controls
Explore Our Lobby Read FAQ
koko11 koko11 Privacy Policy For Your Account
PRIVACY CONTACT

Get Help With Privacy Requests

A clear contact path helps you ask about the Privacy Policy without repeating your account story. Tell us which account detail, device record, cookie setting or wallet reference concerns you, and include only the minimum information needed to locate it. We use the same account checks for a privacy request as we use for a login or payment receipt question. Where local law permits, we can explain the request status and any reason a record must remain available.

Team online

Account privacy

Ask our support team to explain personal data linked to your account. Include your registered phone number only through the account contact path, never a password or wallet PIN. We may ask for a phone verification step before discussing private account details.

Wallet records

For a DANA, OVO, GoPay or QRIS reference, send the receipt details shown in your account rather than full wallet credentials. We can check whether the record matches your account and explain what data is kept for that request.

Data changes

If your contact detail is wrong, request a correction through support after signing in. We compare the request with your account step and phone verification, then explain any fields that cannot be changed while a security or payment check remains open.

DATA PRACTICE

What We Do With Your Data

Privacy controls work best when each data use has a clear purpose. We separate account access records from ordinary browsing signals, limit wallet references to payment and support checks, and use security…

Account details

We collect details needed to create and maintain your account, including contact information and phone verification status. These records support sign-in and account recovery. If you ask what we hold, we use your verified account path to reduce the risk of revealing data to another person.

Device signals

When you move from login to the lobby on a phone, browser or desktop, we may record device and session signals. These help identify unusual access patterns. They are not a request for your private files, contacts or unrelated device content.

Cookies

Cookies can remember your session and selected page settings, so you do not have to repeat the same choice on each visit. Your browser controls whether cookies remain. Changing them may affect sign-in continuity, but it does not erase account records by itself.

Payment references

A wallet receipt or QRIS reference can be connected to an account request so we can check its status. We do not need your DANA, OVO or GoPay PIN for that check. Bank transfer and virtual account references are handled for the same limited purpose.

Account security

Phone verification is an account step before access to private details. We may compare sign-in events, device signals and request history when a login or wallet status stalls. This helps us decide whether a request can be discussed through the account contact path.

Retention requests

We keep records only while they support account operation, a payment receipt check, an unresolved request or a legal need. You may ask us to explain retention or request deletion where local law permits. We will describe any record that must remain and why.

Privacy Policy Answers For koko11

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before opening an account. We explain the practical steps for access, correction, cookies, payment references and contact requests. If a question depends on your location or a current account check, our response will say so directly and use the account path needed to protect your details.

The koko11 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, wallet references and support requests. It explains why we use each category, how retention works and how you can ask about, correct or delete data where local law permits.

No. Our Privacy Policy does not require your DANA, OVO, GoPay or QRIS PIN for a receipt or wallet-status check. We use the payment reference connected to your account request, then ask for account verification before discussing private transaction details.

Sign in and contact our support team through the account contact path. State that your request concerns the Privacy Policy and identify the data category, such as device signals, cookies or account details. We may complete phone verification before sharing private records.

Yes, you can ask for a correction after signing in. Tell us which account detail is inaccurate and provide the updated value through support. We compare the request with your verified account step, while payment or security records may remain unchanged during an open check.

The Privacy Policy explains that cookies can preserve your session and page settings between visits. You control them through your browser. Removing or blocking cookies may interrupt login continuity, but it does not automatically remove account, payment-reference or support records held for valid purposes.

When you use a phone to move from login to the lobby, we may collect session and device signals linked to that visit. We use them for access security and unusual-activity checks. We do not request unrelated files, contacts or private content from your device.

You can ask support to explain deletion options under the koko11 Privacy Policy. We assess the request against account operation, unresolved wallet or receipt checks and legal needs. Where local law permits, we remove eligible records and explain any data that must remain.

Related Pages

koko11 Indonesia koko11 Casino Live Dealer Lobby FAQ Boxing Betting