Reference

Privacy Policy for dunia666 Accounts

Our Privacy Policy explains how dunia666 handles the account, device and wallet details you provide before you enter the lobby.

Clear data purposesWallet status checksAccount access controlsPolicy contact path
dunia666 Privacy Policy for dunia666 Accounts
CONTACT OPTIONS

Ask About Your Privacy Policy

A direct support request gives you a practical route to ask how your Privacy Policy rights work on an active account.

Account request Use the account support path to ask what personal details are linked to your…
Wallet question For a DANA, OVO, GoPay or QRIS privacy question, send the payment reference rather…
Access concern If a login or device signal appears unfamiliar, contact support through the account path…
DATA PRACTICES

What We Do With Your Details

We keep our Privacy Policy practical: each data category has a reason connected with account access, security, payment matching or support.

Account data

When you open an account, we handle the details needed to create your profile and connect it with your phone verification step. We use that link to manage sign-in requests and to respond to a Privacy Policy access or correction request.

Device signals

A phone or desktop browser can produce session, browser and login signals. We use these signals to identify unusual access and protect the account, not to read unrelated files on your device. Your browser path remains subject to local access rules.

Cookies

Cookies can remember a session and help us understand whether an account request belongs to the same browser. You can manage cookies through your browser settings. Turning them off may require another sign-in, but it does not erase account records automatically.

Payment matching

A wallet or bank reference lets us match a transaction with the right account and investigate a status question. For DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI records, we use the reference needed for that check rather than requesting a wallet password.

Security controls

Phone verification, sign-in events and account support checks work together when access looks unusual. If you suspect someone used your account, contact us promptly and avoid sharing credentials. We can explain the security record connected with the request.

Retention requests

You may ask what data we hold, request a correction or ask whether deletion or restriction is available. We assess the request against account security, transaction records and local duties. Where local law permits, support will explain the next step and any identity check.

Privacy Policy Questions About dunia666

These Privacy Policy answers address the account and payment questions you are most likely to have before access. We keep the route concrete: use your account identifier, complete phone verification when requested and share only the transaction reference needed for a check. If eligibility or access is part of your question, it depends on local law and applies where local law permits.

The dunia666 Privacy Policy covers account details, phone verification, login and device events, support messages, cookies and payment references. It explains why we use each category for access, security, transaction matching or support, and how you can ask about correction, restriction or deletion where local law permits.

No. Our Privacy Policy describes payment-reference handling, not wallet-password collection. When you use DANA or OVO, we may retain the reference needed to match a status or receipt with your account. Do not send your wallet password to support, even during a transaction question.

Contact us through the account support path and state that you are making a Privacy Policy data request. Include your account identifier and complete phone verification if asked. We will explain what can be provided, how identity is checked and whether local law limits the response.

Device and login events help us investigate unfamiliar access and protect your account. They can show whether a request came from a phone or desktop browser and when the session occurred. Our Privacy Policy limits this use to security, access handling and related support checks.

Yes, you can contact support with the account detail that needs correction. We may use phone verification to confirm that the request belongs to you. Our Privacy Policy allows corrections where appropriate, while transaction and security records may need to remain accurate for their original purpose.

Retention depends on the reason the record exists, such as account security, a DANA or QRIS reconciliation check, support handling or a legal duty. Our Privacy Policy does not promise one period for every record. Support can explain the applicable route where local law permits.

You can ask support whether deletion or restriction applies to a particular data category. We first verify the account and assess security, payment and legal needs. Where local law permits, we will explain what can be removed, what must remain and how the request is handled.