Reference

Privacy Policy For Your adaqq Account

adaqq Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet recordsCookie choicesAccess requests
adaqq Privacy Policy For Your adaqq Account
PRIVACY SUPPORT

Get Help With A Privacy Request

A clear contact path matters when your Privacy Policy question concerns a login, wallet record or stored account detail.

Account privacy Use the account support route for a Privacy Policy question about your name, contact details, verification step or sign-in history. We may ask you to confirm account ownership before discussing stored data, so another person cannot receive details connected with your profile.
Wallet records Choose the cashier-related support path when your request concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account records. Share the payment reference and date only; we use those details to locate the relevant transaction without asking for your wallet password.
Privacy changes For a correction, access request or question about cookie use, send the request through the privacy contact path shown in your account area. We will explain the next account check, the data involved and any limits that depend on local law.
DATA PRACTICES

How We Handle Your Account Data

We handle Privacy Policy matters around the actions you take on the service: opening an account, signing in, checking a wallet status or asking for support.

Account details

We use the details entered during account opening to create your profile, support sign-in and respond to account requests. Before changing or disclosing those details, we may ask for a clear account step, such as confirming the contact route already linked to your profile.

Device signals

A phone or desktop browser can create technical records such as session data, device type and sign-in time. We use these signals to maintain access and spot unusual activity. They are not a substitute for your password, and we do not ask you to share that password.

Cookies

Cookies help keep your session active and remember selected page settings. Browser controls let you remove or restrict them, although sign-in functions may then behave differently. Our Privacy Policy explains why a cookie is used before it supports an account or wallet action.

Wallet matching

Payment records let us connect a cashier event with the correct account. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we check references and status details rather than requesting your wallet credentials.

Retention period

We retain account, security and payment records only for the period needed for the stated service purpose, account protection or a legal requirement where local law permits. When a record is no longer needed, our handling follows the applicable removal or de-identification process.

Your request

You can ask what account data we hold, request a correction or question a cookie through the privacy contact route. We first verify ownership, then explain the result, any affected records and any response limit that depends on local law.

Privacy Policy Answers For adaqq

These Privacy Policy answers address the searches we hear most often before an account is opened. We focus on account records, device behaviour, cookies, wallet references and the steps for asking us to inspect or change stored details. If your situation involves a local restriction, the outcome depends on local law.

The adaqq Privacy Policy covers details you provide for an account, technical records from your phone or browser, cookie activity, support messages and payment references. It explains how we use those records for access, security, wallet matching and requests, where local law permits.

Use the privacy contact path shown after you sign in and ask for an account data access request. We verify that you control the account, identify the records covered and explain any restriction that depends on local law before we respond.

Yes. Our Privacy Policy covers references and status details created when you use DANA, OVO, GoPay, QRIS, bank transfer or virtual account funding. We use those records to match a cashier event with your account and do not need your wallet password.

You can ask us to correct an account detail through the privacy contact route. Include the detail you believe is wrong and the updated value, but do not send a password. We verify ownership first and then explain the change or any local-law limit.

Device data helps us maintain a sign-in session and identify unusual access, while cookies can remember session continuity and page settings. Browser controls can restrict cookies, though sign-in may work differently. The Privacy Policy describes these uses in connection with your account.

We keep payment references for the period needed to match wallet or bank activity, protect account access and meet a legal requirement where local law permits. The exact record depends on the transaction, and you can ask support which category relates to your account.

Start with the privacy contact path in your account area so we can connect the question to the correct profile. For a DANA receipt, QRIS status or sign-in concern, include the date and reference, never your password, and we will explain the next check.