Reference

dragon 303 Privacy Policy For Your Indonesia Account

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA and QRIS for account funding.

Clear data purposesWallet record clarityAccount request pathMobile access context
dragon303.best page image
ACCOUNT HELP

Get A Clear Privacy Request Path

A direct support path helps you ask about the Privacy Policy without repeating your account story.

Policy questions Send your question through the account support route and name the Privacy Policy topic…
Wallet records For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate time…
Access checks If a mobile browser sign-in looks unfamiliar, contact support from the account path and…
DATA PRACTICE

What We Do With Your Account Data

We keep the Privacy Policy practical by linking each data use to an account task you can recognise.

Collection scope

We collect account details, contact details, verification data, sign-in events, device signals and payment references when those records are needed…

Cookie choices

Cookies and similar browser storage help keep your session available and remember selected settings.

Account security

We use account checks before discussing protected records, especially after an unfamiliar mobile-browser entry.

Retention reasons

We retain records only for stated needs such as account administration, payment matching, security checks, dispute handling and required record…

Requesting changes

You can ask us to correct inaccurate account data or explain a particular use.

Policy contact

Use the account support path for Privacy Policy questions, access requests and data concerns.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers cover the searches we hear most often before account access. They explain the records connected with wallets, mobile sign-in, cookies and requests, while the policy wording and available rights remain subject to local law.

It covers account and contact details, verification records, device and sign-in events, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We need payment references and status details to match a DANA or QRIS transaction to the correct account, check a receipt question and investigate a disputed account event.

Yes. Use the account support path, describe the inaccurate field and complete the requested account check. We assess the request under the Privacy Policy and applicable local law.

We may record sign-in time, device signals and session events to protect your account. If an entry looks unfamiliar, contact support and complete verification before we discuss that record.

Retention depends on the record and its purpose, such as account administration, payment matching, security or dispute handling. We follow the Privacy Policy and any period required by local law.

Send the request through the account support route and identify the account record you want to access. We may ask for verification before releasing protected data or confirming its contents.

Browser cookie controls can affect session continuity and selected settings. You can adjust them in your browser, but sign-in or account-area functions may require the storage described in the Privacy Policy.