Reference

Privacy Policy For Your mambawin Account

mambawin’s Privacy Policy explains how we use account, device and wallet details when you open the lobby, check VIP Baccarat or move through DANA and QRIS steps.

Account clarityWallet recordsDevice choicesLocal-law access
mambawin Privacy Policy For Your mambawin Account
HELP WITH YOUR RIGHTS

Get Privacy Help Near Account Support

A clear support route matters when you want to ask about your Privacy Policy rights or a wallet record.

Account data request Ask us what account details we hold, why they are used and which records…
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction reference…
Correction or deletion You can ask us to correct inaccurate details or request deletion of eligible data…
CONTROLLED DATA USE

What You Can Check Before Opening

The Privacy Policy is designed to answer the questions that arise before you open an account: what follows your login, what happens to wallet references, and how long…

Account details

We use the details you submit to create and maintain your account, connect phone verification to the correct profile and…

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us identify a payment attempt and match a receipt…

Cookies and browser signals

Cookies and similar browser signals can keep a session working, remember selected settings and help us detect unusual sign-in behaviour.

Mobile device access

When you open the lobby from a phone, we may receive device and connection details needed for session security and…

Retention and deletion

We keep records only as long as needed for the stated account, security, support or dispute purpose, subject to applicable…

Policy requests

For a copy, correction, restriction or eligible deletion request, contact support with the account detail used for phone verification.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account and wallet questions you may search before opening mambawin. They cover phone verification, mobile access, payment references, cookies, retention and requests for changes. If your situation is not listed, use the account support path and include enough detail for us to locate the relevant record safely.

The mambawin Privacy Policy covers account details, phone verification, sign-in events, device and browser signals, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains your available requests and processing limits.

Phone verification helps us connect account access to the correct person, reduce mistaken sign-ins and protect account requests. It can also help support locate your profile when you ask about a Privacy Policy matter. Never send your verification code in a support message.

Yes. The Privacy Policy applies when you use a mobile browser to sign in, browse Rocket Crash or check an account page. We may process device type, browser details, connection signals and security events needed to maintain the session and investigate unusual access.

We may store a payment reference, status, amount-related record and account connection for QRIS, DANA, OVO, GoPay, bank transfer or virtual account activity. We do not need your wallet PIN or banking password to match a receipt question or check a status.

You can contact account support and request a copy of eligible personal data connected with your profile. Include the phone or account detail used during verification. We may confirm ownership first, then provide the available records or explain why part must remain restricted.

Send a correction request through the account support channel and identify the detail that appears wrong. We may ask for phone verification or another account step before changing it. If the record is tied to a payment or security event, we will explain the review path.

We retain account, support, security and payment records for the period needed for their stated purpose and any applicable requirement. A deletion request can remove eligible data, but some records may remain for dispute handling, payment reconciliation or security where local law permits.