Reference

kingkong39 Privacy Policy for Indonesia

kingkong39 Privacy Policy explains how we handle your account details, phone verification, device signals and wallet records when you use our Indonesia lobby.

Account dataDevice signalsWallet recordsPolicy requests
kingkong39 kingkong39 Privacy Policy for Indonesia
HELP ROUTE

Where to Ask About Privacy Policy

A clear contact path matters when a wallet record or account detail looks unfamiliar.

Account data request Use the support link beside the cashier to ask what account details we hold…
Wallet record question Mention DANA, OVO, GoPay or QRIS and the transaction reference shown in your account…
Device access concern Tell us if a phone, tablet or desktop session looks unfamiliar; we can direct…
CONTROL ROOM

Six Privacy Controls for Your Account

We apply the Privacy Policy to the practical points you see during an account session, from phone verification to a return from the mobile lobby.

Collection

We collect account and phone verification details during the access step, plus device signals that help identify unusual sign-ins or repeated security checks.

Cookies

Necessary cookies and device storage help maintain your session on mobile or desktop; you can ask support which cookie purpose relates to your account.

Wallet separation

DANA, OVO, GoPay and QRIS references are handled as payment records, while your game category choices such as Fish Hunter remain separate context.

Account security

Phone verification, login records and device checks support account protection; never place a wallet PIN or full password inside a support message.

Retention

We retain records for the period needed for account security, transaction checking or a legal requirement, then assess whether continued storage is needed.

Policy changes

If this Privacy Policy changes, we will present the updated wording through the policy page so you can check the new data purpose before continuing.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. They cover the records created by phone verification, mobile sessions and local payment choices, with access handled where local law permits. If your situation is more specific, use the support route beside the cashier and refer to the relevant account or payment reference.

It covers account details, phone verification, device signals, cookies, payment references and security events connected with your use of the site, including DANA, OVO, GoPay and QRIS records.

Phone verification helps connect an account request to the correct account record and supports security checks. We use the result for account handling rather than treating your phone number as public lobby content.

Yes. The policy covers QRIS, DANA, OVO and GoPay references and status results. We use those records to check the related payment event, not to request your wallet PIN through support.

You can contact us through the support link beside the cashier and describe the incorrect field. We will check the account record and explain the available correction path, which depends on local law.

We may record device and session signals when you move from login to the mobile lobby. These signals help identify unusual access, while necessary cookies can keep your session and policy choice active.

Retention depends on the purpose of the record, such as account security, transaction checking or a legal requirement. Ask support about a specific reference and we will explain the applicable period where local law permits.

Use the support path beside the cashier, provide your account phone number through the protected form and state whether you need account, device or wallet records. We will explain the next step under local law.