Reference

Open komandan88 Privacy Policy Clearly

Our Privacy Policy explains what we collect when you create an account, verify your phone, browse Auto Roulette or use DANA and QRIS, and why each step is…

Account dataWallet recordsCookie choicesPolicy requests
komandan88 Open komandan88 Privacy Policy Clearly
REQUEST HELP SAFELY

Use Policy Support For Account Questions

A clear contact path matters when you want to ask about your Privacy Policy rights, correct an account detail or check why a wallet record is attached to a transaction. Start from the support contact option shown in your account area and include the relevant receipt or date without sending your password. We use the details you provide only to locate the request and respond with an appropriate account check.

Team online

Privacy request

Ask us to explain, correct or remove eligible personal data through the account support path. We may request phone verification before discussing records connected with your identity.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and payment date. We compare the receipt with the account record without asking for your wallet PIN.

Login data concern

If a new device or unfamiliar login appears, use the account help route promptly. We can review the access details and guide the next verification step.

DATA CONTROL POINTS

See How We Handle Your Privacy

The Privacy Policy is supported by practical controls rather than broad promises. We separate identity checks from payment references, limit account discussions until verification is complete and use device signals to spot…

Collection

We collect details you enter during account creation, including your phone number, plus device and login signals needed to maintain account access and investigate unusual activity.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account record can be linked to your account reference, but we do not ask for your wallet PIN.

Cookie settings

Cookies can remember sign-in preferences and page settings on your phone or desktop. You can manage browser cookie controls, though some account functions may then need repeated checks.

Account security

Phone verification is part of account access. We may compare login device details with earlier activity before discussing personal data or changing account information.

Retention period

We keep account, payment and support records only as long as operational security, dispute handling or applicable legal duties require, then remove or limit them.

Correction request

If your phone detail or another account field is inaccurate, contact the support route with the requested correction. We check ownership before changing records linked to you.

Ask About Privacy Policy Access

These Privacy Policy answers address the questions you may have before opening an account or returning to the lobby. We keep each answer tied to an actual account step, device action or payment record, so you know what to prepare when contacting us. For access or eligibility, the applicable position depends on local law and the service is available where local law permits.

It covers account details, phone verification, login and device activity, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps us confirm account ownership before access or account changes. It also lets us investigate an unfamiliar device or answer a Privacy Policy request without exposing your records.

No. We may retain a payment reference, receipt details and account matching status for a wallet transaction, but you should never send your DANA, OVO, GoPay or QRIS PIN.

Use the support contact option in your account area and ask for a Privacy Policy data request. Include your account phone detail, then complete any ownership check we provide.

Yes. Send the inaccurate field and the requested correction through the account support path. We verify the request first, then update eligible records or explain why a record must remain.

Payment and account records remain while needed for security, receipt matching, disputes or applicable legal duties. After that period, we remove them or restrict their use.

Start with the support contact option displayed in your account area. Mention whether the concern involves cookies, login activity, phone verification, a payment receipt or a data correction request.