Reference

Privacy Policy for Your koi93 Account

Our Privacy Policy explains how koi93 handles the account details you provide before you reach Live Casino, bonanzatoto or other lobby areas.

Clear data purposesWallet record contextCookie choicesAccount request path
koi93 Privacy Policy for Your koi93 Account
CONTACT ROUTES

Get Privacy Help Beside Your Account

A direct support route helps you resolve a privacy question without guessing which account area to use. We connect your request to the relevant login, wallet or receipt context, while keeping the request focused on your personal data. Use the support path shown beside your account or cashier area, and include the email or phone detail linked to your koi93 account so we can locate the correct record.

Team online

Account access

Ask us to explain an account-data record, correct a contact detail or help with a privacy request after you complete the requested verification step. We use the account path so a data answer reaches the right person.

Wallet records

For DANA, OVO, GoPay or QRIS questions, send the payment reference and date through the support route beside the cashier path. We use those details to check status without asking you to repeat unrelated account data.

Device concerns

Tell us if a phone, browser or login session shows unfamiliar activity. We can review the relevant access event, explain the security step and direct you through account protection while the privacy request is assessed.

DATA PRACTICE

What Our Privacy Process Covers

Privacy work follows the same account path you use to reach the lobby: we identify the record, check its purpose and limit the response to the request.

Data collection

We use account details, verification data, login events and device signals to create access, protect the account and respond to support requests. A request about Live Casino or slotbingo activity is handled as account data, not as a reason to collect unrelated details.

Cookie control

Our cookies can support a signed-in session, remember a selected setting or help identify unusual access. You can manage browser cookie controls, although disabling a necessary session cookie may affect account access until the setting is restored.

Account security

We may compare a login device, phone verification result and recent account event before changing sensitive details. This step helps prevent a privacy response or wallet update from being sent to someone who cannot verify the account.

Payment matching

A DANA, QRIS or bank transfer reference lets us match a receipt with the correct account and status. We keep the reference for that operational purpose, while avoiding use of the payment detail as a substitute for account verification.

Retention period

We retain records according to their purpose: access and security events support account protection, while payment references support reconciliation and receipt questions. When a record is no longer needed for those purposes or legal duties, our process removes or restricts it.

Change requests

Send a correction, access or deletion request through the account support route with the contact detail attached to your profile. We may request phone verification, explain any legal reason for retaining a record and confirm the action through the same account channel.

Privacy Policy Questions About koi93

These Privacy Policy answers address the practical questions you may have before opening or using an account from Indonesia. We cover the records linked to your login, wallet activity, cookies, device access and requests for correction or removal. Where a request requires an account check, use the contact route beside your account so we can respond to the correct data subject.

The Privacy Policy covers account details, phone verification, login and device events, cookies, support messages and payment references. It explains why we use each category, how we protect it, when we retain it and how you can ask for access or correction.

We keep transaction references and status details for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us match receipts and investigate status questions. We do not treat a payment reference as a request to collect unrelated personal data.

Phone verification helps us confirm that a sensitive account or Privacy Policy request comes from the account holder. We may use it before discussing login events, changing contact details or disclosing a wallet record, particularly when the request involves a new device.

Cookies can keep your session active, remember a selected setting and help us identify unusual access. Browser controls let you manage them. If you disable a necessary session cookie, you may need to sign in again before opening account areas such as Live Casino.

Yes. Send the correction request through the account support path and identify the contact detail or record that needs attention. We may ask for phone verification, then confirm the result or explain why a specific record must remain under the Privacy Policy.

Retention depends on the record and its purpose. Security events help protect account access, while payment references support receipt matching and status checks. We remove or restrict records when they are no longer needed for those purposes or for duties required where local law permits.

Use the support route shown beside your account or cashier area and include the email or phone detail connected to your profile. For DANA, QRIS or other wallet records, add the payment reference and date so we can check the correct account context.