Reference

kino4d Privacy Policy for Indonesia

Our Privacy Policy explains how kino4d handles the details you provide when you open an account, verify your phone, enter the lobby or use DANA, OVO, GoPay and…

Account clarityWallet data careCookie choicesAccess requests
Explore Our Lobby Read FAQ
kino4d kino4d Privacy Policy for Indonesia
CONTACT THE DESK

Privacy Help When Account Details Stall

A clear contact path matters when a phone check, wallet status or account record needs attention. We ask you to contact our support desk from the account contact path and include the email or phone number linked to your account, the affected device and a short description of the request. For a DANA or QRIS receipt, include the transaction reference while hiding passwords, one-time codes and full security credentials. We use the details in your request to locate the relevant record, explain the next step and avoid asking you to resend information we already have.

Team online

Account contact path

Use the support route connected with your account when you need a Privacy Policy answer, a correction to your contact detail or help understanding a phone-verification record. We may ask for an account identifier so we can match the request without exposing another person's data.

Payment receipt check

If a DANA, OVO, GoPay or QRIS status appears incorrectly, send the transaction reference through the support desk rather than a wallet password or one-time code. We compare the reference with our payment record and explain what data was used for that check.

Access and correction

Ask us to see, correct or clarify personal data linked to your account through the same contact path. We verify that the request comes from you before discussing account records, and access remains subject to local law and necessary security protections.

DATA CARE DETAILS

What We Protect, Store and Change

Our handling process separates account access from the payment credentials held by your wallet or bank.

Account records

We keep the contact details and verification result needed to let you reach the correct account. If your phone number or email changes, request an update through support after signing in. We may keep the previous value in a security history for the period required to investigate access issues.

Payment references

Our payment record can include a rail name, amount status, time and reference for DANA, QRIS, bank transfer or a virtual account. It is used to reconcile your account activity, not to request your wallet PIN. BCA, BRI, Mandiri and BNI references follow the same account-matching purpose.

Cookies and sessions

Cookies can keep your signed-in session and security preference aligned while you move from a phone browser to a desktop browser. Clearing them can sign you out or trigger phone verification again. Browser controls let you remove or block cookies, subject to the account functions that require them.

Security signals

We use device, browser and login-time signals to identify unusual access, such as a new device appearing during an active session. These signals support account protection and may lead to an extra verification step. We do not ask you to share a password or one-time code with support.

Retention choices

We retain records for account operation, payment reconciliation, security investigation and legal duties only while a valid reason exists. When that reason ends, we delete, aggregate or anonymise the relevant record where practical. A retention request can be raised through support, although some records may need to remain temporarily.

Policy requests

You can ask what personal data we hold, request a correction, ask about processing or raise a deletion request through the account contact path. We confirm your identity before acting, explain any lawful reason for refusal and tell you if a request affects account access or payment record duties.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access or returning from a mobile device. We keep the wording specific to the data path: what we collect, why we use it, how cookies work and how you can contact us. If a situation is not covered, use the account contact path and tell us which record or payment reference needs attention.

The Privacy Policy covers data connected with your account, phone verification, login sessions, device signals, cookies, support requests and payment status. This includes records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, subject to the purpose and retention rules described on this page.

We use your phone number to create and protect account access, complete the required verification step and help support match a request to you. We do not need your wallet PIN or one-time code. If the number changes, request a correction through the account contact path after signing in.

No. We use payment references and status details to match activity with your account, but your DANA, OVO, GoPay or QRIS password and PIN belong with the payment service. Never send those credentials to us. For a receipt check, provide only the reference needed to locate the transaction.

Yes. Ask through the account contact path for access to personal data linked to your account or for a correction. We verify the request before sharing or changing records. Where local law permits, we explain the result and any reason a security, payment or legal record must remain.

Cookies can preserve a session and remember security preferences between account pages. You can block or clear them through your browser, but doing so may sign you out or require phone verification again. Our Privacy Policy explains this device behaviour so you can choose settings with a clear account impact.

We keep information while it supports account access, payment reconciliation, security review, dispute handling or a legal duty. After the relevant reason ends, we delete, aggregate or anonymise the record where practical. You can ask support about a particular record, though required retention can limit immediate removal.

Use the support route connected with your account and describe the data request clearly, such as a phone correction, cookie question or QRIS receipt check. Include your account contact detail and avoid passwords or one-time codes. Access and responses depend on local law and identity verification.

Related Pages

kino4d Indonesia kino4d Casino Account information FAQ Fan Tan VIP Table