Reference

Open mangga toto Privacy Policy with Clarity

mangga toto Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and access the lobby from your phone.

Account data choicesWallet data contextMobile privacy steps
mangga toto Open mangga toto Privacy Policy with Clarity
CONTACT PATHS

Ask About Privacy Through Support

A clear support path helps you question a record without sending sensitive details into a public message.

Privacy request Use the support link to ask what account details we hold, why a field…
Account access If phone verification or a login check blocks access, tell us the account email…
Payment reference For DANA, OVO, GoPay or QRIS questions, include the payment reference and status shown…
HANDLING DETAILS

Protect Your Account Data on Mobile

We handle privacy requests alongside the account checks that protect your access, rather than treating a message as proof of identity.

Collected details

We may handle contact details, verification results, login events, device signals and transaction references. The exact record depends on the account step, wallet choice and support question you send us.

Cookie choices

Session cookies help keep an account page connected while you move from login to the lobby. Browser settings can remove or block them, although some account functions may then need another check.

Account security

Phone verification and unusual-login checks can protect access before account details are shown. We will not ask you to disclose a DANA PIN, OVO code, GoPay password or banking password.

Retention approach

We keep records only for the period needed for account operation, payment matching, security review and legal duties. When a record is no longer needed, our handling follows the applicable retention requirement.

Request a change

You can ask us to correct inaccurate account details or explain a stored field through support. Include the affected account step, but send only the minimum details needed to locate it.

Device behaviour

A mobile browser may retain a session cookie, while a new device can trigger phone verification. This can change what we request during access without changing the privacy choices available to you.

Find Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or asking us to change a record. We connect each answer to a practical step, such as phone verification, a DANA receipt or a browser session, so you know what to send and what to keep private.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps us confirm that the person requesting account access or a privacy change controls the account contact path. It can also appear after a new-device login or unusual access signal.

No. We may receive a payment reference or status from the payment path, but you should never send a DANA PIN, OVO code, GoPay password or banking password to support.

A session cookie can keep your browser connected while you move from login to the lobby and may help us identify a loading issue. You can manage cookies in your browser settings.

Contact support through the account help path and name the field or account step that needs correction. We may request an identity check before changing details linked to account access.

We retain payment references for account matching, support, security and applicable legal duties for the period needed for those purposes. The retention period can vary by record type and local requirement.

The policy applies to our website and account-related pages for supported Indonesian access. Eligibility and processing depend on local law, so access can differ by location or legal requirement.