Reference

kino168 Privacy Policy For Your Account

Our Privacy Policy explains how kino168 handles the details connected with your account, wallet activity and lobby access.

Account dataCookie choicesWallet recordsPrivacy requests
kino168 kino168 Privacy Policy For Your Account
PRIVACY SUPPORT

Where To Ask About Your Privacy Policy

A direct support path helps when you want to understand, correct or limit the information connected with your account. Contact us through the account support chat and include the email or phone detail used during verification, without sending a password or one-time code. We can then locate the relevant record, explain its purpose and route a privacy request to the appropriate team. If a DANA, OVO, GoPay or QRIS receipt is involved, attach only the reference needed for the status check.

Team online

Account support chat

Use the support chat from your signed-in account for a Privacy Policy question, correction request or access query. We can connect the request to your verified phone detail and explain which account record is being handled without asking you to reveal your password.

Wallet record check

For a wallet privacy question, share the relevant DANA, OVO, GoPay or QRIS reference with sensitive numbers covered. We use that limited reference to identify the transaction status and avoid exposing unrelated account or payment details.

Access assistance

If you cannot reach the privacy page after login, tell us the device path you used, such as mobile browser or desktop browser. We will help you reach the request route while keeping account credentials and verification codes private.

SIX DATA CHECKS

Six Checks Behind Your Privacy Choices

We apply the Privacy Policy to the practical moments you see: opening an account, confirming a phone number, changing a session, using a wallet and asking support for help.

Account creation

We use the details you enter during account creation to establish your profile and connect later activity to the correct account. A clear account path helps us avoid duplicate records when you move from the lobby to a wallet request.

Phone verification

Phone verification helps us confirm that an account access request comes from the person controlling the registered number. We do not ask you to place a password or one-time code inside a support message or privacy request.

Cookie controls

Cookies can keep a signed-in session available and remember basic browser choices. If you clear them through your mobile or desktop browser settings, some account access steps may need to be completed again before the privacy page opens.

Session security

Login activity and device signals can help us identify unusual access and protect account records. If a session looks unfamiliar, we may ask for account verification before discussing DANA, QRIS or other wallet-linked information.

Retention decisions

We keep records for the period needed to operate account security, resolve a wallet dispute, meet accounting duties or answer a legal request. When a record is no longer needed for those purposes, our handling process can remove or de-identify it.

Change requests

You can ask us to access, correct or clarify personal data connected with your account through support chat. Include enough detail to locate the record, but leave out passwords, one-time codes and complete wallet credentials.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the questions we expect before you create an account or connect a local wallet. Each response stays focused on account data, cookies, verification and privacy contact steps, so you can decide what to share before entering the lobby. Where access or eligibility is discussed, it depends on local law.

The kino168 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and wallet references. It explains why we use each category, how we protect access and how you can ask for access, correction or clarification.

When you use DANA or QRIS, we may receive a transaction reference, status, amount-related record and account identifier needed to match the request. We use those details for wallet processing, security and support rather than for unrelated contact.

Yes, you can ask support chat to identify the personal data connected with your account. Include your verified email or phone detail, and we may complete an account check before explaining which records can be provided under applicable law.

Send a correction request through the signed-in support chat and describe the inaccurate field clearly. We may ask you to confirm the registered phone detail before changing it, especially when the correction could affect account access or wallet matching.

Our mobile browser path can use cookies to maintain a session and remember basic choices. Clearing cookies through your browser settings may sign you out or require phone verification again. You can ask support which cookie-related record concerns your request.

We retain personal data only as long as needed for account security, wallet dispute handling, accounting, support history or legal duties. The period can differ by record type. You may ask support why a particular record remains in our systems.

Use the account support chat and state whether you want access, correction, clarification or another privacy action. Do not include a password or one-time code. If you cannot sign in, describe your mobile or desktop access path so we can help.