Reference

mancing duit Privacy Policy for Your Account

mancing duit explains how we collect, use and protect your account details when you open the lobby from Indonesia.

Account dataWallet recordsDevice accessCookie choices
mancing duit mancing duit Privacy Policy for Your Account
CONTACT ROUTES

Ask About Data, Login or Wallet Records

A clear support request helps us locate the right account record without asking you to post private details in a public message. Use the support route shown on our site for questions about this Privacy Policy, phone verification, a device record or a DANA, OVO, GoPay or QRIS status. We may ask for account identifiers so we can check the request safely.

Team online

Policy questions

Send a support request when you want to know what account, device or payment records we hold. Include your account contact details only through the private support route shown on our site.

Access concerns

If phone verification or account access stalls, tell us the device type and the step that stopped. We use those details to investigate without asking for your password or wallet PIN.

Wallet records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, keep the receipt reference ready. We use it to match payment status while limiting unnecessary account exposure.

HANDLING DETAILS

Browse How We Handle Your Policy Rights

We keep this policy practical by linking each data purpose to a real account step: phone verification, device sign-in, wallet status or support handling.

Account details

We use the contact and verification details you submit to create your account, confirm access and respond to requests.

Device signals

When you sign in from a mobile phone or desktop browser, technical signals can help us recognise sessions and investigate…

Cookies

Cookies can remember session settings and help pages load correctly.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to your account.

Account security

We use verification checks and access records to reduce unauthorised account activity.

Changes and requests

To correct details, ask about retention or request an eligible deletion, contact support through the site route.

Find Privacy Policy Answers Before Joining

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening access. They explain what we collect, why device and payment records appear, how to request a change and what to do when local eligibility applies. If your situation is not listed, send a private support request through our site.

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

We use phone verification to confirm account access and help identify the correct account during support requests. We do not need your password, one-time code or wallet PIN for a policy enquiry.

Yes. The policy covers technical records created when you sign in from a mobile phone or desktop browser, including session details used to investigate unusual access and maintain account security.

We use payment references and status details to match a wallet activity or QRIS receipt with your account, investigate a stalled status and respond to support requests without requesting a wallet PIN.

Send a private support request through the contact route shown on our site. Tell us which account detail needs correction, and we may verify account ownership before making the change.

You can request removal of eligible personal data through support. We assess the request against account needs and applicable duties, so some payment or security records may need to remain.

Yes. Account access and eligibility depends on local law. If you are unsure whether access is available in your location, contact support before sharing personal or payment details.