Reference

mpo6204d Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you create an account, verify your phone, access Live Blackjack Grand or check DANA and QRIS wallet status.

Account dataWallet recordsCookie choicesSecurity steps
mpo6204d mpo6204d Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact route matters when you want to ask about your Privacy Policy rights or a wallet record. Sign in first when possible so we can connect your request with the correct account, then include the phone number linked to your profile and the relevant payment reference. We will ask only for details needed to confirm identity and locate the record, never your wallet PIN.

Team online

Account access help

Use the account help path when your phone verification stalls or you cannot reach the privacy request area. We can identify the affected profile using your registered phone details and explain which account records are connected to the request.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, send the payment reference and approximate date shown in your receipt. We compare that reference with the account ledger and explain what information is retained for the transaction.

Policy request

Ask us to access, correct or clarify personal details through the support path attached to your account. Include the subject of your request, and we will confirm the next identity step before discussing account data.

DATA PRACTICES

What We Do With Your Details

We separate account security, payment matching and site measurement so each process has a defined purpose.

Account details

We collect the name, phone number and verification result needed to create and protect your account. If you ask us to correct a spelling or phone detail, we may request a fresh verification step before changing the record.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a cashier event to your profile. We do not ask for a wallet PIN, and we keep payment references for reconciliation and dispute handling.

Cookies and devices

Cookies can remember a session choice, while device and browser signals help us detect an unusual login. You can clear cookies in your browser settings, although doing so may require phone verification when you return.

Security controls

Phone verification is part of account access, and unusual sign-in activity may trigger an additional check. Do not send a password or wallet credential to support; we use account-linked details rather than secret wallet codes.

Retention periods

We keep account, support and payment records only while they serve account operation, dispute checks or a legal requirement that depends on local law. When a record no longer has a valid purpose, we delete it or remove its account link.

Changes and requests

You can ask for a copy, correction or deletion assessment through the account support path. Tell us whether the request concerns a profile detail, a QRIS receipt, a cookie choice or a lobby record such as Aviator Crash Game.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account questions you may have before using mpo6204d. We explain the practical path for data access, corrections, cookies, wallet references and account closure without asking you to share secret payment credentials. Where a legal request or eligibility rule applies, the outcome depends on local law.

The mpo6204d Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect access, how long records may remain and how you can ask for access or correction.

We may collect your name, registered phone number, verification result, browser or device signals, session details and messages sent through account support. If you use DANA, OVO, GoPay, QRIS, bank transfer or virtual account, we may retain the related payment reference.

Yes. Use the support path connected to your account and request a copy of the personal details held about you. We first confirm that you control the account, then explain the scope, format and timing of the response under rules that depend on local law.

Send a correction request through account support and identify the field that is wrong, such as your phone number or name. We may require phone verification before making the change, because an unverified edit could block access to your account or misdirect a wallet record.

Yes, cookies may keep a session choice or help us understand whether a mobile page loaded correctly. You can remove them through your browser settings. After removal, the next visit may ask for phone verification again, and some saved privacy choices may need to be selected.

We use DANA and QRIS references to match a payment event with the correct account and investigate a receipt or status question. We do not need your wallet PIN. The reference, amount shown by the payment rail and related account event may remain for reconciliation.

You can submit a deletion request through the account support path. We assess which records can be removed and which must remain for an open dispute, payment reconciliation or a requirement that depends on local law, then explain the result and any remaining record category.