Reference

Privacy Policy For Your mineraltoto Account

Our Privacy Policy explains how mineraltoto handles your account details, wallet status and access records before you enter Live Baccarat, macan333 or another lobby.

Clear data purposesWallet status checksPolicy contact path
mineraltoto Privacy Policy For Your mineraltoto Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

Privacy questions should not interrupt your account path. We keep three clear support routes so you can ask what data is connected to your account, explain a wallet-status mismatch or request a change to your contact details. Include your account phone number and the relevant date, but never send a password or one-time code. If you are checking a QRIS receipt or a login record, tell us which device you used so our team can locate the right event.

Team online

Account data request

Ask the support team to confirm which account details we hold, why a phone check was needed and whether a correction can be made. We will use the account path rather than discussing private records in an open message.

Wallet record question

For DANA, OVO, GoPay or QRIS status concerns, share the transaction reference and date, not your wallet password. We can compare the payment record with your account while keeping unrelated account activity outside the request.

Policy change request

If you want to amend a phone number, ask about cookie choices or request removal of eligible data, state the exact action clearly. We may verify account ownership before changing or releasing any private record.

DATA CONTROL

Six Practical Privacy Safeguards

We handle Privacy Policy questions as account operations, not as a generic statement hidden from the cashier path.

Account creation

We use the details you enter to create and maintain your account, including phone verification before account access. A clear account path helps us connect a support request to the right record without asking you to repeat private details.

Payment matching

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we use the reference and status needed to reconcile the request. We do not need your wallet password to investigate a receipt.

Cookie controls

Required cookies keep sign-in and session protection working on your browser. If optional cookies are offered, you can ask support what they do and request a change without sending your password or one-time code.

Device security

We may record browser, device and sign-in signals to identify unusual account access. Returning from a phone to desktop can prompt an ownership check, protecting the account before private data or wallet status is discussed.

Retention period

We keep account, payment and support records for the period needed for service operation, dispute handling and legal duties. When a record no longer has a valid purpose, we remove it or separate it from direct account details.

Your request

You can ask what data relates to your account, request a correction or ask whether deletion is available. We verify ownership first, then explain the result through the support route connected to your mineraltoto account.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account and payment questions we hear before a new account is opened. They cover phone verification, cookies, wallet records, device access, retention and requests for changes. If your situation is specific, use the account support path with a date or receipt reference; access depends on local law and where local law permits.

The mineraltoto Privacy Policy covers account details, phone verification, sign-in and device records, cookie use, payment references and support requests. It explains why we use each category, how we protect it and how you can ask about correction, access or eligible removal.

We use your phone number to create the account, complete the account access check and connect private support requests to the right record. It can also help us identify an unusual sign-in. We do not need your wallet password or one-time code for a policy request.

Yes. The Privacy Policy covers the payment reference, amount status and date needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those details to investigate a pending record, not to request your wallet password.

Required cookies support sign-in, session continuity and security checks when you move through the web path. If optional cookies are available, you can ask support what they support and request a change. Clearing cookies may require you to complete account access checks again.

You can send a data request through the account support path and state that you want the records connected to your account. We may verify ownership before responding. Our answer can cover account, device, cookie, payment and support records still held for a valid purpose.

We retain account, payment and support records while they serve operational, dispute or legal needs. The exact period can differ by record type and local requirements. When the purpose ends, we remove the record or reduce its connection to your direct account details.

You can request a correction or ask whether removal is available by naming the record and the change you want. We verify account ownership first. Some records may need to remain for dispute or legal duties, and access depends on local law.