Reference

ninja188 Privacy Policy for Your Account

Our Privacy Policy explains how we handle the account details connected with Live Baccarat Prestige, Ceme Keliling Room and wallet activity.

Clear data purposesCookie choicesAccount access rightsWallet record handling
ninja188 ninja188 Privacy Policy for Your Account
CONTACT PATH

Privacy Questions Near Your Account

A clear contact route helps when you want to ask about a record, correct a phone detail or check how a cookie works. Start from your signed-in account support path and include the subject of your Privacy Policy request, without sending a password or wallet PIN. We can then match the request to the right account step and explain any identity check needed before discussing personal data.

Team online

Account support

Use the support path connected to your account when you need a copy, correction or explanation under this Privacy Policy. Include your registered phone number only through the protected account route, and never place a password, PIN or full payment credential in your message.

Wallet status help

If a DANA, OVO, GoPay or QRIS record looks unfamiliar, tell us the date, amount reference and displayed status through account support. We use those details to locate the relevant record without asking you to resend a wallet password or share a complete card credential.

Access requests

For a Privacy Policy request from a mobile browser, open account support after login and ask for access, correction or deletion review. We may ask for an account check before releasing data, helping prevent another person from receiving details linked to your account.

DATA PRACTICE

Cookies, Login Security And Retention

We handle this policy area through practical account controls rather than broad promises. Login records help us identify unusual access, cookies help remember selected settings, and wallet references help reconcile a payment…

Account details

We receive details such as your phone number when you create or verify an account. These details support sign-in checks and account recovery. If a detail is wrong, request a correction through support after login so we can confirm the account before changing it.

Device records

When you sign in on a phone or desktop browser, we may record device and session signals used to protect access. These signals can help us spot an unfamiliar login around casino or sports pages without treating your device as a permanent identity.

Cookie choices

Cookies can keep a session active, remember a selected language or help us understand whether a page loads correctly. You can manage browser cookie settings, although switching them off may require another login or affect parts of the account path.

Payment matching

A receipt or status linked to DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI may be used to match a wallet or bank step to your account. We do not need your wallet PIN or banking password to check that reference.

Retention checks

We retain account, security and payment records only while they serve an operating, dispute, fraud-prevention or legal purpose. Once a record no longer serves one of those purposes, our handling process removes it or separates it from direct account use.

Policy changes

If our data handling changes, we update this Privacy Policy and show the revised wording on the policy page. Check the page before completing a new account step, and contact support if a change affects a request already made.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account and wallet questions you are most likely to search before opening access. They also explain how to reach us when a personal-data request needs a human check.

It covers account details, phone verification, device and session records, cookies, payment references, security handling, retention and requests connected with your personal data. It applies when you access the account path from Indonesia, where local law permits, and explains how to contact us.

We may collect your phone number, verification responses, login events, device signals and account activity needed for access and security. We can also retain DANA, OVO, GoPay, QRIS, bank transfer or virtual account references to trace a payment status.

Wallet and bank references can identify which account step a payment belongs to and whether a receipt is pending, accepted or needs checking. The Privacy Policy explains this limited use; we do not ask for your DANA PIN, banking password or complete wallet secret.

After signing in, use the account support path and state that you want a Privacy Policy data-access request. Add the registered phone number through that protected route. We may verify account ownership before sending a copy or describing the records held.

Yes. Send a correction request through account support after login, identify the detail that is wrong and provide the replacement carefully. We may ask for an account check, then update the record where the request is valid and explain any limit.

The retention period depends on why the record exists. We may keep account, payment and security details for account operation, dispute handling, protection against misuse or a legal requirement. When none applies, our process removes the record or limits its use.

You can adjust cookies through your browser settings and contact account support about a removal request. We assess deletion against security, payment reconciliation, disputes and legal duties. If access is restricted or depends on local law, we explain the reason through the same support path.