Reference

mustang178 Privacy Policy and Your Account

mustang178 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and browse from a mobile device.

Account dataWallet recordsCookie choicesAccess requests
mustang178 mustang178 Privacy Policy and Your Account
SUPPORT ROUTES

Wallet Status Contact Path

A clear contact route helps you act on a privacy question without sending payment details through an unverified channel.

Account privacy request Use the account support path to ask which personal details are held, why they are used, or how to correct a phone number. We may ask you to confirm account ownership before discussing private records, keeping the request attached to your verified profile.
Payment record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the reference shown on your receipt rather than a wallet password. We check the payment status against the account record and explain what was retained for reconciliation.
Access and deletion help Ask support to explain an access, correction or deletion request through the same account route used for login help. We may retain limited records where needed for an open dispute, fraud check or legal duty, then remove or anonymise them when practical.
ACCOUNT SAFEGUARDS

Cookies Beside Account Security

We handle privacy as an account process rather than a hidden setting. Our records help us complete phone verification, recognise a returning device, match a wallet reference and investigate an unusual sign-in.

What we collect

We may receive your account contact details, phone verification result, login timestamps, device information, cookie choices and payment references. For a game such as Live Baccarat Elite or Esports PUBG Mobile, records may also show session activity needed to display account history and resolve a service question.

Why we use it

We use account and device data to sign you in, complete verification, protect the profile from unusual access, process wallet status and answer support messages. We use payment references to reconcile a receipt, not to request or store your DANA, OVO or GoPay password.

Cookies and devices

On mobile, cookies and device signals help keep the path from login to the lobby connected, including when you check QRIS status. Browser settings can clear or block cookies, but clearing them may sign you out or require phone verification again on the next account visit.

Account protection

Phone verification is required before account access, and we may compare sign-in details with earlier device activity when something looks unusual. Never send a password or wallet PIN to support. If your phone changes, use the account help path so we can confirm ownership before changing contact details.

Retention approach

We keep each record only for as long as it serves account operation, payment reconciliation, security review, dispute handling or a legal duty. When a record is no longer needed, we delete it or remove identifying links where practical, subject to unresolved account or payment matters.

Requesting a change

You can ask us to access, correct, restrict or delete personal data through support, explaining the account contact and request clearly. We may request a verification step to prevent disclosure to another person, and we will explain any part that cannot be changed while a legal or payment duty remains.

Privacy Policy Questions for Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia, including phone verification, wallet payments, mobile access and requests about stored data. We keep the wording direct so you know what to send through support and what may be needed to confirm that the account belongs to you.

The mustang178 Privacy Policy covers account details, phone verification, sign-in and device signals, cookie choices, payment references and support messages. It explains why we use those records, how long we keep them for a stated purpose, and how you can request access or correction where local law permits.

No. We use the payment reference, status and time needed to match DANA or QRIS activity with your account. We do not ask for a wallet password or PIN. If a cashier status stalls, send the receipt reference through account support so we can check the correct record.

Use the account support path and state that you want a copy of your personal data. Include the account contact used for phone verification and describe the records you need, such as sign-in history or payment references. We may confirm ownership before releasing private account details.

Yes, ask support to correct an account detail and explain what has changed. Because phone verification controls account access, we may require an ownership check before changing the number. This helps prevent another person from redirecting your profile or receiving a private account response.

Cookies and device signals help maintain your session from mobile login to the lobby and can flag unusual access. Clearing browser data may sign you out or trigger phone verification again. You can manage cookie settings in your browser, while some account functions may require them.

We retain records for the time needed to operate the account, match DANA, OVO, GoPay, QRIS or bank references, investigate security events, resolve disputes or meet a legal duty. After that purpose ends, we delete or anonymise records where practical, subject to unresolved matters.

Yes. Access and eligibility depend on local law, and this Privacy Policy applies where local law permits. If you ask us to delete or restrict a record, the response may also depend on legal, security or payment obligations that require limited retention for a defined purpose.