Reference

Privacy Policy For Your muncang Account

Our Privacy Policy explains how we collect, use and protect the details connected with your muncang account.

Account clarityWallet recordsDevice choicesContact path
muncang Privacy Policy For Your muncang Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A privacy question should not interrupt your account access. We keep the contact route close to the account and wallet path so you can ask about a phone number, device record, payment…

Account request Use the account contact route to ask for a copy, correction or explanation of personal details held with your profile. Include your registered phone number and the specific record, such as a phone verification entry or a DANA reference, so we can locate the request.
Wallet question For a privacy question tied to OVO, GoPay, QRIS, bank transfer or virtual account activity, identify the payment rail and date without sending a password or full security code. We use the transaction reference to separate wallet status from other account data.
Access concern If a mobile device or desktop session shows an unfamiliar account event, contact us through the support path and mention when you noticed it. We can review the account access record, ask for verification and help you protect the profile before discussing its contents.
DATA PRACTICE

How We Handle Your Policy Requests

We apply the Privacy Policy to practical account events rather than treating every record alike. Registration details support account access, device signals help us spot unusual sessions, and wallet references help us…

Account data

We use registration and phone verification details to connect you with the correct account and respond to policy requests. If you ask us to correct a detail, we compare the request with the account path before changing the stored record.

Device signals

A mobile browser or desktop session can create technical access records, such as device and session details. We use them to identify unusual sign-ins and protect your profile; they are not a reason to request your password in a support message.

Cookie choices

Cookies can keep a session active and remember basic page choices. Your browser settings provide controls for removing or limiting them, although changing those settings may affect account access steps or require you to verify the phone again.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity help us match a request with your account. We use the smallest useful detail for status checks and do not ask you to share a security code.

Retention period

We retain personal records while they serve account access, security, dispute handling or legal duties. When a record is no longer needed for those purposes, our handling process removes it or separates it from direct account identification.

Change requests

To request access, correction or deletion of eligible personal data, contact us with your registered phone or email and the exact request. We may confirm ownership first, then explain any part that must remain for security or legal reasons.

Privacy Policy Answers For muncang

These Privacy Policy answers address the account questions you are most likely to have before opening access. They explain what we collect, why wallet references appear in records, how device sessions are handled and how you can request a change. If your situation is not covered, use the account contact route with the registered detail that identifies your profile.

The muncang Privacy Policy covers account registration, phone verification, device sessions, cookies, support requests and payment references. It explains why we use each category, how we protect it, when retention ends and how you can request access or correction where local law permits.

We collect the details needed to create and secure your account, including contact information used for phone verification. We can also record device and session events, support messages and payment references from DANA, OVO, GoPay, QRIS or bank transfer activity.

DANA and QRIS references help us match a cashier request with the correct account and check its status. The same principle applies to OVO, GoPay, bank transfer and virtual account records. Do not send us your wallet password or security code.

You can contact us to request access to eligible account data or ask for a correction. Include your registered phone or email, identify the record and explain the change. We may verify ownership first, and some records may remain for security or legal duties.

When you use a mobile browser, we may record technical session details that help identify unusual account access and protect your profile. These records support security checks; they do not require you to share a password. Desktop sessions can create similar technical records.

We keep personal data while it supports account access, security, a payment dispute, a support request or an applicable legal duty. After the relevant purpose ends, our process removes the record or separates it from direct account identification where appropriate.

Use the account contact route and include the phone or email linked to your profile, the request type and any relevant date. For a wallet matter, add the payment rail and transaction reference without a password or security code. We then confirm ownership and respond to the request.