Reference

Open dunia77 Privacy Policy With Clear Data Controls

Our Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet activityCookie choicesSecurity steps
dunia77 Open dunia77 Privacy Policy With Clear Data Controls
CONTACT PATHS

Ask About Privacy Policy Through Account Support

A privacy question should not get lost beside a payment query, so we keep the request path tied to your account details. When a login or wallet status stalls, include the affected account step and payment reference rather than sending sensitive credentials. We use the contact route shown in your account area to match your request and explain the next action.

Team online

Data request

Ask what account details we hold and why they are used. Include your account phone number through the signed-in support path so we can match the request without asking for your password.

Correction request

If a phone detail or account record needs changing, tell us which field is incorrect. We may ask for the same phone verification step used before account access.

Wallet query

For a DANA, OVO, GoPay or QRIS receipt, share the transaction reference and date through support. We use those details to check payment status without requesting your wallet PIN.

DATA PRACTICES

Explore Our Privacy Policy Handling Steps

We treat privacy as an operating process connected to account access, payment matching and device security.

Account details

We use the phone number and verification details you provide to create an account, confirm account access and connect support replies to the correct record.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us reconcile a payment with your account. We do not need your wallet PIN for that check.

Cookies

Cookies may retain a sign-in preference or help us identify an error path on mobile or desktop. You can manage browser cookie settings, though some account functions may then need another sign-in.

Security controls

Phone verification is used before account access, while unusual sign-in or payment activity may require an additional check. Never send us your password, wallet PIN or one-time code.

Retention

We keep account and payment records for the period needed for security checks, reconciliation, support handling and legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Change requests

To request access, correction or removal of eligible details, contact us through the account support route. We verify ownership first, then explain what can be changed under local requirements.

Browse Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the searches you may make before creating an account or checking a wallet record. If your situation is not covered, use the account support path and describe the exact data or payment step involved.

It covers account details, phone verification, device and browser data, cookies, payment references, security checks, retention practices and requests to access or correct eligible information.

Yes. The Privacy Policy covers payment references and status details from DANA, OVO, GoPay and QRIS when they are used to match a transaction with your account.

Phone verification helps confirm that you control the account before access is provided. It also supports account recovery and helps us distinguish a genuine request from an unauthorised change.

Use the support route shown inside your account and ask for an account data request. We may verify ownership through your registered phone before explaining the available records.

Yes. Tell support which account field is inaccurate and provide the matching phone details through the account route. We check ownership before changing information connected to access or payments.

Cookies can remember a sign-in preference and help trace a mobile browser error. You can adjust browser settings, but disabling cookies may require repeated sign-in or affect account access.

The policy is written for our Indonesia account flow, while access and eligibility depend on local law. We apply these practices where local law permits and explain limits through support.