Reference

qq88asia Privacy Policy for Your Account

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

Account data explainedWallet activity coveredYour request options
qq88asia qq88asia Privacy Policy for Your Account
REQUEST SUPPORT

Open A Privacy Request From Your Account

A clear request path helps you ask what we hold, why we hold it, or whether a detail needs correction.

Account request Send an access, correction, or deletion question from your account area. Including your registered phone detail helps us locate the correct record without asking you to send wallet credentials.
Wallet status For a DANA, OVO, GoPay, or QRIS privacy question, mention the payment rail and reference shown in your account. We use that detail to separate one transaction record from another.
Login assistance If your phone path will not open the request form, contact our support route with the affected device type and account identifier. Do not include your password or wallet PIN in the message.
DATA CONTROLS

Browse qq88asia Privacy Controls Clearly

We handle this policy area through practical account controls rather than vague promises. Phone verification helps us confirm account access, while sign-in records and device signals can help identify unusual attempts.

Collection purpose

We collect account and contact details to create your record, confirm phone access, answer support requests, and connect account actions with the correct DANA, QRIS, OVO, or GoPay status.

Cookie choices

Cookies can keep your signed-in session and remember necessary settings on mobile or desktop. Your browser controls let you remove or block cookies, although some account functions may then require another sign-in.

Account security

Before discussing private account data, we may check your registered phone detail or another account marker. Never send a password, wallet PIN, or one-time code through a support message.

Payment records

A bank transfer or virtual account reference may be retained with its status and timestamp so we can resolve matching questions. We do not need your wallet PIN to investigate a receipt.

Retention period

We keep personal data only while it supports account security, payment reconciliation, support handling, or a legal requirement. When a record no longer serves those purposes, we assess it for removal.

Change requests

Ask us to access or correct your personal data through the account request path. State the change clearly, and we may verify ownership before applying it to protect your account.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or connecting a local wallet. We explain the practical route for data requests, browser cookies, device access, and payment references. If your question is not covered, use the account support path and identify the relevant record without sharing secret credentials.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use your phone detail to help create and protect the account, confirm that a sign-in request belongs to you, and locate the correct record when you submit a Privacy Policy request.

Start from the signed-in account request path and ask for access to your personal data. Include your account identifier and request scope; we may verify ownership before releasing private details.

Yes. Submit a correction request through the account support path, describe the inaccurate field, and provide the updated detail. We may ask for a phone or account check before changing it.

The Privacy Policy allows us to use the selected rail, reference, status, and timestamp to match an account action, answer a receipt question, and investigate a stalled payment record.

Yes. The policy covers mobile, tablet, and desktop sessions. A new device may create a fresh session or security signal, and we may request account verification before discussing related data.

Access depends on local law. Our Privacy Policy explains data handling, but it does not change local eligibility rules. Check your position before opening an account or sending payment details.