Reference

Open the kuy89 Privacy Policy

kuy89 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and lobby access.

Account dataWallet recordsCookie choicesContact route
kuy89 Open the kuy89 Privacy Policy
CONTACT PATHS

Ask about Privacy Policy changes

A clear contact path helps when you want to understand a data record, correct an account detail or ask why a verification step appears.

Account request Use the account support route to ask about your registered phone number, sign-in record…
Wallet record For a QRIS, virtual account or bank transfer record, send the transaction reference rather…
Policy question If a paragraph is unclear, contact us with the page subject and your question.
DATA PRACTICES

Check how kuy89 protects your details

We handle Privacy Policy requests as account matters, not as general lobby questions. Phone verification helps us separate an account holder from an unknown sign-in, while wallet references…

Data handling

We use account details for access, security, support and transaction reconciliation.

Cookie controls

Cookies can keep a session active, remember a language or device preference and help us understand an account access event.

Account security

Phone verification is part of the account access check, especially when a sign-in or account request needs confirmation.

Payment records

A payment record may show the rail selected, such as DANA, OVO, GoPay, QRIS, virtual account or bank transfer, plus…

Data retention

We retain account, security and payment records only for the period needed for the stated service, account protection, dispute handling…

Change requests

Ask us to correct an inaccurate phone, profile or contact detail through the verified account support route.

Find Privacy Policy answers quickly

These Privacy Policy answers focus on the account questions you are most likely to search before opening access. We explain the practical effect of cookies, phone verification, wallet references, retention and contact requests in plain English. If your situation is not covered, use the account support route and include only the details needed to identify your request. Eligibility and access depends on local law.

The kuy89 Privacy Policy covers details connected with your account, phone verification, sign-in activity, support requests, cookies and payment records. It also explains how we use those details for account access, security, reconciliation, retention and eligible requests to correct or remove data.

Phone verification helps us confirm account control before access or a sensitive account change. It can also help us investigate an unfamiliar sign-in. We do not need your wallet PIN or password for this check, and support should not ask you to disclose either.

Yes. The Privacy Policy covers account-side records linked to DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity. These records can include a selected rail, reference and status so we can reconcile an account request without collecting your wallet security code.

Cookies may remember a session, language or device setting and can help connect an access event with the correct account. Required cookies may be needed for sign-in and verification. You can adjust browser settings, but removing them may interrupt the mobile account path.

You can contact us through the verified account support route to request a correction to an eligible phone, profile or contact detail. We may confirm account control first. If a record must remain for payment reconciliation, security or legal duties, we explain that reason.

We keep account, security and payment details for the period needed for the stated service, account protection, dispute handling or applicable legal duties. After that reason ends, the available process may remove or anonymise the record, subject to what local law permits.

Use the support route connected with your account and describe the Privacy Policy issue, such as a cookie question, wallet reference or correction request. Include the relevant account reference, not a password or wallet PIN. We will explain the next verification step and response path.