Reference

Open mineraltotologin Privacy Policy Before Account Access

mineraltotologin Privacy Policy explains how we handle your account details, device signals and wallet references before you enter the lobby.

Account detailsWallet referencesMobile device dataPolicy accessIndonesia rules
mineraltotologin Open mineraltotologin Privacy Policy Before Account Access
POLICY HELP ROUTES

Check Privacy Policy Help Through Account Support

A clear contact route matters when your Privacy Policy question involves a phone verification record, a wallet reference or a device sign-in.

Account contact Use the account support path for a Privacy Policy request, and identify the email or phone detail attached to your account so we can match the correct record.
Receipt context If your question concerns DANA, OVO, GoPay or QRIS data, include the receipt reference and payment status rather than a wallet password or full security code.
Access questions Ask us to explain a data category, correct an account detail or clarify retention. We will check the request against local law before changing stored records.
DATA CONTROL DETAILS

Browse Privacy Controls From Login To Retention

We handle this policy area through practical account controls rather than broad promises. Phone verification helps us connect a login to the right account, while sign-in events and device signals help identify…

Phone verification

Before account access, we may use the phone verification step to confirm that a login request belongs to you. The verification record supports account protection and contact matching.

Device signals

A mobile browser can provide device type, browser version, connection details and security events. These signals help us investigate access without treating them as your wallet password.

Cookie choices

Cookies can keep a session working, remember selected settings and help us understand technical errors. You can manage browser cookie controls, though some account steps may then require another login.

Account security

We use login records, verification events and selected device signals to detect account access that does not look familiar. Never send a one-time code or wallet credential through support.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain status, amount and receipt references needed for reconciliation, without requesting your wallet password.

Retention requests

You can ask which personal data we hold, request a correction or ask whether deletion is available. We first verify the account link and check whether local law requires retention.

Find Privacy Policy Answers Before You Join

These Privacy Policy questions focus on the account steps you are most likely to encounter on mineraltotologin. We explain what data may be connected to a login, how wallet references are used, what happens on mobile devices and how to ask for a change. Where an answer concerns access or eligibility, the result depends on local law and the account details available to us.

It covers account details, phone verification, device and browser signals, cookies, security events, support messages and payment references. For DANA, OVO, GoPay and QRIS, we may use receipt or status details to reconcile an account without storing your wallet password.

Phone verification helps us connect an account access request with the correct account and investigate unusual sign-ins. We may retain the verification event and related security record for account protection, subject to the retention needs and access rules that depend on local law.

No wallet password should be sent to us through the site or support path. Our Privacy Policy refers to payment status, receipt references and account matching for DANA or QRIS, while your wallet credential remains with the relevant payment service.

We may receive device type, browser version, connection details, session data and security events when you sign in from a phone. This helps diagnose access issues and protect the account. The policy does not treat those signals as permission to read unrelated content on your device.

Contact our account support path and state the record you believe is incorrect, such as a phone number or email detail. Include enough account context for verification, but do not send a password or wallet code. We assess the requested change under the Privacy Policy and local law.

We keep each category only while it supports an identified account, security, payment reconciliation or legal need. A receipt reference may need a different period from a cookie record. When a record is no longer needed, we remove or de-identify it where local law permits.

Yes. Send a request through account support asking for the personal data categories connected with your account. We verify that you control the account, explain any lawful limits, and respond about available access, correction or removal steps where local law permits.