Reference

Privacy Policy For Your muncang Account

muncang Privacy Policy shows what account details we collect, why we use them and how you can ask us to change or remove eligible records.

Clear data purposesWallet record controlsAccount access safeguardsPrivacy request path
muncang Privacy Policy For Your muncang Account
HELP WITH REQUESTS

Get Privacy Help Beside Account Support

A clear support route matters when your Privacy Policy question involves a phone number, wallet receipt or device sign-in. Open the account support path and describe the record you want checked; adding your transaction reference helps us separate a QRIS receipt from an unrelated account event. We use the same route for access questions where local law permits.

Team online

Account request

Tell us whether your request concerns account access, phone verification or a stored profile detail. We may ask you to confirm the account step involved so we do not disclose private records to the wrong person.

Wallet receipt

For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate time shown in your account. We use those details to locate the relevant record without asking you to send a full wallet password.

Device access

If a mobile browser or desktop sign-in looks unfamiliar, contact support through the account path and mention the device type. We can explain the security check, review the access event and direct you through the next account step.

DATA CONTROL

What We Do With Your Account Details

Privacy depends on clear handling at each point of the account journey. We separate identity checks from wallet status work, limit support access to the request being handled and use account security…

Account details

We use the contact and verification details you provide to create, protect and maintain your account. Phone verification comes before account access, helping us connect a support request to the correct account without relying only on a display name.

Payment records

A DANA, OVO, GoPay or QRIS status can be linked to an account event so we can identify a pending receipt or correct a matching error. We use the payment reference for that task rather than requesting your wallet password.

Cookies

Cookies can preserve sign-in preferences, security checks and the path between your account and the lobby. You can manage browser cookie settings, although changing them may require another phone check before private account details are displayed.

Device signals

We may use browser and device signals to spot an unusual sign-in pattern, such as a new mobile browser after a desktop session. These signals support account protection; they are not a replacement for your phone verification step.

Retention period

We keep account, support and transaction records for the period needed to provide the requested service, resolve a dispute or meet an applicable legal duty. When that need ends, records are removed, restricted or separated from active account work.

Change requests

You can ask us to correct eligible account details, explain a data purpose or remove a record where no continuing duty applies. Submit the request through account support, identify the category involved and complete any identity check we reasonably need.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account questions we expect before you use the muncang account path. They cover collection, wallet records, cookies, access, retention and requests. If your situation does not fit one of these answers, contact account support with the relevant reference so we can assess it under applicable local requirements.

The Privacy Policy covers details used during account creation, phone verification, sign-in security, wallet status checks and support conversations. It also explains cookies, device signals, retention and how to request a correction or deletion where the applicable legal conditions allow it.

Phone verification helps us connect account access and privacy requests to the correct person. It can also trigger when a device pattern changes. We use the check before discussing private account details, including wallet references linked to DANA, OVO, GoPay or QRIS.

Yes. The Privacy Policy covers transaction references and status records used to match a QRIS receipt or check a DANA, OVO or GoPay event. We ask for the relevant reference rather than your wallet password when investigating an account support request.

Use the account support path and name the detail or record category you want changed. We may ask you to complete phone verification before acting. Requests are assessed under the Privacy Policy and applicable requirements, including whether a legal retention duty still applies.

We retain records for the operational, dispute-handling or legal period connected to the record. The exact period can differ by category, such as a support message or payment reference. You can ask support to explain the purpose and retention basis for an eligible record.

Yes. Your mobile browser provides cookie controls, and the Privacy Policy explains why cookies may support sign-in preferences and security checks. If you restrict them, you may need to repeat phone verification or other account steps before private details are shown.

Account access depends on local law. We apply this Privacy Policy where local law permits, while requests involving eligibility, retention or data rights may depend on the rules connected to your location. Contact support if you need a location-specific explanation.