Reference

danaqq Privacy Policy, Made Clear

Your account details, wallet choices and device signals receive a clear explanation in the danaqq Privacy Policy.

ACCOUNT DATAWALLET RECORDSDEVICE CONTROLSACCESS REQUESTS
danaqq danaqq Privacy Policy, Made Clear
HELP WITH DATA

Get Policy Help Beside Your Account

A clear support route helps when a Privacy Policy question sits beside a login or wallet issue.

Account access If your phone verification is pending, tell us which account step stopped and the…
Wallet status For a DANA, OVO, GoPay or QRIS status question, share the payment reference shown…
Data requests When you ask to correct, access or remove eligible account data, state the request…
CONTROL YOUR RECORD

What You Can Check And Change

We keep this policy practical by connecting each data use to an account action you recognise.

Account details

We use the details supplied during account opening to maintain your account path and respond to account requests. Check your entered contact details before access, and ask support to correct an eligible mistake.

Device signals

A phone or desktop session may create device, browser and login records for security checks. If access looks unusual, we may ask you to repeat the phone verification step before discussing account data.

Cookies

Cookies and similar browser records can help keep your session connected and remember selected settings. You can manage browser permissions on your device, although changing them may affect account access or saved preferences.

Wallet records

DANA, OVO, GoPay and QRIS references help us match a receipt or status to your account. We do not need your wallet password for that check, so keep those credentials outside support messages.

Retention

We retain account, security and payment records for the period needed for operations, dispute handling and applicable legal duties. Ask support which category applies when you need a retention explanation.

Change requests

You may request access, correction or deletion of eligible data through the account support route. Include the account contact and the specific record concerned; we may verify ownership before changing it.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often about account records, wallet references, device access and contact steps. If your situation is not covered, use the support route inside your account and describe the specific data question.

It covers account details, phone verification, device and browser signals, cookies, login events, payment references and support requests. It also explains retention, eligible access or correction requests, and the circumstances that depend on local law.

We use the phone verification step to confirm that an account request relates to the right account before access or a data change. The check can also help us respond safely when a login or wallet status appears unusual.

Yes. The Privacy Policy covers references, receipts and status details connected with DANA, OVO, GoPay and QRIS activity. We use these records to match account activity, while your wallet password remains with the relevant payment service.

You can ask for access to eligible records or request a correction through the support path shown in your account. State the specific data category, such as contact details or a payment reference, and complete an ownership check if requested.

Device type, browser setting, session details and login time can help us detect unusual access and investigate account problems. These signals support security checks; they do not replace your phone verification or allow support to request your wallet password.

Retention depends on the record type and the operational, dispute or legal reason for keeping it. Account, security and payment references may therefore have different periods. Contact support with the category you mean for a clearer retention response.

Sign in and use the support route shown near the account or cashier path. Include your account contact and a short description of the request, but not a wallet password. Access and any requested action depend on local law.