Reference

koimas88 Privacy Policy for Your Account Data

koimas88 Privacy Policy explains what we collect when you open an account, complete phone verification, access Live Blackjack Turbo, or use DANA and QRIS.

Account recordsWallet activityCookie choicesPrivacy requests
koimas88 koimas88 Privacy Policy for Your Account Data
ASK OUR TEAM

Contact Us About Wallet And Account Data

A clear contact route helps you resolve a privacy question without sending sensitive details through an unsuitable channel. Start from the support path connected to your account and tell us whether your request concerns login records, DANA or GoPay status, cookies, or a correction. We may ask for an account identifier and a safe verification step before discussing personal data. Do not send a password, wallet PIN, or full payment credentials. We handle requests for Indonesian account holders where local law permits.

Team online

Account privacy request

Use the account support route when you want to ask what personal data is linked to your koimas88 account. We may confirm your phone verification status before sharing account-specific details, so your request is not answered to the wrong person.

Payment record question

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record, include the transaction reference and date rather than full wallet credentials. We use those details to locate the entry and explain its privacy handling.

Change or removal request

Ask us to correct, restrict, or remove eligible account data through the same support path. We may retain a limited record where needed for security, dispute handling, or a legal duty that depends on local law.

DATA HANDLING

Protect Your Login And Cookie Choices

Privacy work is tied to the steps you take from login to the lobby, so we describe the practical controls rather than using broad promises.

Account data collected

We may collect your phone number, verification result, login events, device details, and account settings. If you open Live Dragon Tiger Elite or browse casino and sports sections, related activity can be connected to your account record for access control and support.

Payment references

We record the rail and reference needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. We do not ask you to place a wallet PIN or full payment credential in a support message.

Cookies and browser data

Cookies can keep a session active, remember selected settings, and help us detect repeated failed logins. You can adjust browser cookie controls on an Android phone or desktop, though blocking some cookies may require another login.

Session security

Phone verification is an account access step, while device and IP signals help us spot unusual sign-ins. If a login looks unusual, we may pause access and ask for a verification step before discussing wallet or game activity.

Retention periods

We keep data only as long as needed for account operation, security checks, support history, dispute handling, or duties that depend on local law. When a record is no longer needed, we delete it or reduce its link to your account where practical.

Requesting corrections

You can ask us to correct inaccurate account details or explain how a record was used. Include the phone number linked to your account and the specific entry, such as a QRIS reference, so we can assess the request without collecting extra data.

Find Privacy Policy Answers Before Opening

These questions address the privacy points you are most likely to check before opening a koimas88 account in Indonesia. We cover account access, payment references, cookies, device records, corrections, and deletion. The answer may depend on the type of data and the legal basis for keeping it, so use the support route when you need an account-specific response.

The koimas88 Privacy Policy covers account opening, phone verification, login events, device details, cookies, support messages, and payment references. It also explains how records linked to DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity are handled.

We use phone verification to confirm that an account access request is connected to the right account holder. The result can support login security and privacy request checks. Access or eligibility depends on local law and applies where local law permits.

Our support process does not require you to send a DANA or QRIS PIN, password, or full payment credential. We may store a rail name, transaction reference, date, and status so we can match wallet activity to the correct account.

Send a correction request through the account support path and identify the field that needs attention. We may ask for phone verification or another safe account check. Include only the necessary details, such as the affected profile field or transaction reference.

Cookies can remember a session, maintain selected settings, and help identify repeated failed logins. On an Android phone, open your browser settings to adjust them. Blocking required cookies may sign you out or require a fresh login before account access.

You can ask us to delete eligible personal data through the privacy support route. We first verify the request and check whether a record must remain for security, disputes, account history, or a duty that depends on local law.

Retention depends on why the record exists. We keep account, security, support, and payment references only for the period needed for those purposes or where local law permits or requires it, then delete or reduce the link to your account where practical.