Reference

andalas188 Privacy Policy for Indonesia

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

Account dataWallet recordsDevice sessionsCookie choices
andalas188 andalas188 Privacy Policy for Indonesia
CONTACT PATHS

Where To Ask About Privacy

A clear contact route helps you ask about the Privacy Policy without exposing more data than needed. Start from the account support path when you can still sign in; it keeps your request beside the relevant account record. If login or wallet status stalls, use the available support contact and state that your message concerns privacy, access or a data change. We may ask for an account step or phone verification detail so we respond to the right person.

Team online

Account support

Sign in and use the account support path for a Privacy Policy question, access request or correction. Include the email or phone detail attached to your account, but never send a wallet PIN, full password or one-time code in your message.

Payment status help

For a DANA, OVO, GoPay or QRIS record, tell us the payment rail, date and reference shown in your account. We use that limited context to locate the status without asking you to disclose unrelated wallet credentials.

Access concerns

If your privacy request follows a locked sign-in or unfamiliar device alert, contact us through the same account help route. We may confirm phone verification before discussing records, helping keep account data with the person who requested it.

HANDLING PRACTICES

How We Apply This Privacy Policy

Privacy is handled through ordinary account controls rather than broad promises. We separate login checks from payment references, review device signals for account protection and keep only the records needed for the…

Account data use

We use your account identifiers and phone verification status to create, maintain and protect access. When you move between casino and wallet areas, the account record helps connect the session without requiring you to submit the same details repeatedly.

Payment references

We record payment references and status signals, not your private wallet password. DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries help us match a transaction question to the correct account support request.

Cookies and browsers

Cookies may retain a sign-in session, language choice or security preference on your browser. You can clear them through browser settings. Clearing cookies can end your session and require phone verification or another account sign-in step.

Device protection

Device type, browser signals and sign-in times can help us identify an unfamiliar session. If an alert appears, we may pause discussion of account records until you complete the account check linked to your phone.

Retention approach

We retain personal data only for the period needed to provide the requested account function, resolve a payment or security issue, meet a valid legal requirement, or establish and respond to a data request.

Change requests

To request access, correction or removal, contact us through account support and identify the record you mean. We may request a matching account detail, explain any necessary retention and confirm the result through the contact route on file.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the account, device and payment questions you may have before opening access. We keep the wording tied to actual actions: phone verification, browser cookies, wallet references and the support route. If your situation is not covered, contact us with the smallest amount of personal data needed to locate your record.

The andalas188 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use those records for sign-in, account protection, wallet status checks and privacy requests, with access depending on local law.

The policy covers status and reference details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account payments. We use those references to investigate a matching account question; you should not send a wallet password, PIN or one-time code.

Yes. Contact us through the account support path and request access to your personal data. Tell us the account phone or email used for sign-in. We may complete a phone verification step before releasing records to protect your account.

Send a correction request through account support and name the detail that needs changing. We may compare it with your account record, ask for a verification step and then confirm which change was made or why a record must remain.

Cookies can keep your browser session, language choice and security preference available while you move through account pages. You can clear or block them in browser settings. After that, you may need to sign in again or complete phone verification.

We keep records for the period needed to operate the requested account function, investigate a payment or security matter, meet a valid legal duty or handle a data request. The required period can differ by record type and applicable local law.

You can contact account support to request removal. We assess the request against account security, unresolved payment references and any valid retention requirement. Where removal is possible, we explain the outcome; access and eligibility still depend on local law.