Reference

Privacy Policy For Your mnctoto Account

Our mnctoto Privacy Policy gives you a clear view of how we handle the phone number used during verification, device details from your login and wallet references linked…

Clear collection purposesWallet reference controlsAccount access rulesCookie choices
mnctoto Privacy Policy For Your mnctoto Account
HELP WITH YOUR DATA

Get Policy Help Near Account Access

A clear support path matters when a Privacy Policy question meets a login or wallet-status issue. From your account help area, tell us whether you need a copy of your stored details, a correction to your phone record, clarification about a DANA receipt or removal of a device cookie. Include the account identifier you can safely share so we can locate the right record without asking for your password.

Team online

Account request

Use the account help path to ask what personal details we hold or to correct a phone verification record. We confirm that the request belongs to you before changing account data, and we do not ask you to send a password or full wallet credentials.

Wallet query

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, attach the receipt number and date shown in your account rather than private wallet login details. We use that context to check the policy record and explain what was stored for the payment status.

Device request

When a mobile browser keeps an old session or cookie, ask our account help team to explain the related record. We can outline the sign-in step, suggest clearing site data and assess a deletion request after confirming your account identity.

OUR DATA PRACTICE

What You Can Expect From This Policy

We keep this policy practical by linking each data use to an account action you recognise, from phone verification through a mobile sign-in to a payment status check.

Phone verification

We use your verified phone detail to connect sign-in activity with the right account and to reduce confusion when an…

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us reconcile a status question.

Cookies and sessions

Our site may keep a session cookie so your mobile browser can move from sign-in to the policy page without…

Account security

We examine login time, browser type and device signals for unusual account access.

Retention period

We keep personal data only while it supports account operation, security checks, payment disputes or a legal duty.

Change requests

You can ask for access, correction or deletion through account help.

Privacy Policy Answers For mnctoto

These Privacy Policy answers cover the practical searches you may make before opening an account or while checking a wallet record. We keep the wording tied to mnctoto account steps, mobile access and Indonesian payment references, so you know what to send and what to expect when asking for help.

The mnctoto Privacy Policy covers details supplied during account creation and phone verification, login and device signals, cookies, support requests and payment references. It also explains retention, security checks and the ways you can request access, correction or deletion where local law permits.

We use your phone number to complete the account verification step, connect later sign-ins with your account and help investigate an access question. If your number is wrong or changes, use account help to request a correction after we confirm your identity.

No. The Privacy Policy distinguishes a payment reference from private wallet credentials. We may retain a DANA, OVO, GoPay or QRIS reference, date and status context to investigate an account question, but you should never send us a wallet password or banking sign-in.

Open the account help path and request a copy of the personal details linked to your account. Include a safe account identifier and the verified phone detail we can use for identity checks. We then explain the available record and any lawful reason for limiting access.

Yes, you can request a correction or deletion through account help. We first confirm that you control the account, then check whether the record is still needed for sign-in security, a payment dispute or a legal duty before explaining the result.

The Privacy Policy does not treat every record the same way. We retain account, device or payment-reference data while it supports operation, security, dispute handling or legal requirements. After that need ends, we delete the record or remove identifying details.

Yes, it describes our handling of data when you access the account from Indonesia, including a mobile browser and local wallet references. Account eligibility and access depend on local law, and we apply the policy where local law permits.