Reference

Privacy Policy for Your kc bet Account

kc bet Privacy Policy explains how we collect, use and protect details connected with your account, including login records and DANA, OVO, GoPay or QRIS activity.

Account dataWallet recordsCookie choicesAccess requests
kc bet Privacy Policy for Your kc bet Account
CONTACT ROUTES

Ask About Wallet Data Without Guesswork

A clear contact route helps you ask what we hold, why a record appears, or how to correct an account detail. Start from the support path connected to your login and include the account phone number, the relevant date and the payment rail, such as QRIS or bank transfer. We use those details to locate the right record without requesting your password.

Team online

Account privacy request

Use the account-linked support path to ask for a copy, correction or explanation of personal data. Include your verified phone detail and request type so we can check identity before discussing records.

Wallet record check

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the reference and date through support. We compare the payment record with the account event and avoid asking you to share a password or access code.

Login access concern

For an unexpected sign-in or a phone verification problem, contact us through the login support route. Tell us whether the attempt came from mobile browser or desktop so we can focus the security check.

SECURITY PRACTICE

How Login Data Stays Account Bound

Our privacy process follows the practical moments you meet: opening an account, confirming a phone, moving through the lobby and checking a wallet record.

Phone verification

Before account access, we use the phone detail you provide to confirm that the sign-in request belongs to you. Keep that detail current, and contact support if a verification message reaches an old number.

Cookie controls

Cookies and similar browser signals can keep a session active, remember selected settings and help us identify repeated sign-in failures. You can adjust browser controls, although some account functions may then require another login.

Device signals

We may record device type, browser version, language setting and sign-in time to spot unusual account access. The same check can apply when you switch from a mobile browser to desktop for Live Roulette Salon.

Payment matching

A wallet reference, virtual account detail or bank transfer record helps us match a transaction to your account. We use that payment context for status checks and do not need your wallet password to investigate a receipt.

Retention period

We keep account, support and transaction records for as long as needed for the stated service, dispute handling and legal duties. When a record is no longer needed, our process removes it or separates it from direct account identity.

Data changes

You can ask us to correct an inaccurate phone detail, contact record or account preference. Send the request through the account-linked support route; we may confirm identity before changing data connected with DANA or QRIS.

Privacy Policy Questions For Indonesian Accounts

These Privacy Policy answers cover the questions we expect you to ask before opening an account or checking a wallet record. They explain the practical route for data access, corrections, cookies, phone verification and contact, while local access remains subject to local law.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, security checks and how to ask about your records.

We use your phone number to create and verify account access, connect support requests to the correct account and help detect unusual sign-ins. If the number changes, contact us through the account support route before requesting changes to related wallet records.

Yes, you can ask what personal data is connected with your account and how it is used. Send the request through the account-linked support path with your verified phone detail. We may confirm identity before releasing account or payment records.

Tell us which detail is inaccurate, such as a phone number, contact entry or account preference, and send the request through support. For a DANA, OVO, GoPay or QRIS record, include its date or reference so we change the correct entry.

Cookies can support sign-in sessions, remember selected settings and help identify repeated access failures on mobile browsers. You can change cookie controls in your browser. If cookies are restricted, you may need to sign in again when returning to the lobby.

We retain account, support and transaction records for the period needed to provide the account service, investigate disputes or meet legal duties. After that need ends, our process removes the record or separates it from direct account identity.

Use the support path connected to your account and state that your request concerns the Privacy Policy. Include the account phone detail, subject and relevant payment rail or sign-in date. Access or eligibility depends on local law and applies where local law permits.