Reference

qqnusa Privacy Policy For Your Account

Our qqnusa Privacy Policy explains what we collect when you open an account, sign in, browse Dragon Tiger or use DANA and QRIS, and why each record supports…

Account dataWallet recordsCookie choicesPolicy requests
qqnusa qqnusa Privacy Policy For Your Account
REQUEST HELP DIRECTLY

Where To Ask About Privacy Policy

A clear contact route helps you act on this Privacy Policy instead of searching through account screens. We handle questions about collected data, cookie settings, wallet references, phone verification, and access records through the routes below. Include your account phone number and a short description, but do not send a wallet password, one-time code, or full payment credential. We may ask for a safe identity check before changing account data.

Team online

Privacy request

Use the privacy contact route on qqnusa to ask what account data we hold, request a correction, or ask how a DANA, OVO, GoPay, or QRIS reference is used.

Account help

If phone verification or sign-in stalls, use the account help path beside your cashier records. We can connect the access issue with the relevant device and payment-status data.

Receipt question

For a missing QRIS receipt or bank-transfer reference, send the transaction time and account phone number through support. We use those details to locate the matching record.

SECURITY IN PRACTICE

QRIS Security And Account Control

Our handling process separates access data from payment references so a routine lobby visit does not expose wallet credentials.

Data collection

We receive data from your account form, phone verification, sign-in activity, support messages, and payment status. Browsing Dragon Tiger, Aviator, Bingo, or Fish Hunter may create lobby and device records.

Cookie choices

Cookies help keep your session active and remember selected settings. You can manage browser cookie controls, though limiting necessary cookies may interrupt sign-in or return you to phone verification.

Device signals

Our mobile web path may record device type, browser version, approximate network details, and session events. This helps us identify unusual access without reading unrelated files, photos, or messages.

Account security

Phone verification is part of account access, while one-time codes should remain private. We may pause a session when device or sign-in signals do not match expected account activity.

Retention period

We keep account, support, and payment-reference records only as long as needed for service delivery, dispute handling, security checks, or legal obligations, followed by deletion or anonymisation.

Change requests

Ask us to correct account data, explain a record, or address a privacy concern through the privacy route. We verify the request before making changes and reply using the contact details on file.

Privacy Policy Questions For qqnusa

These Privacy Policy answers address the searches we hear most often before account access. They cover wallet records, cookies, device activity, corrections, retention, and the steps to contact us from Indonesia. If your question concerns a specific transaction or phone number, use the privacy route and provide only the minimum details needed to locate your account.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity.

We use payment status, reference numbers, amounts, and timestamps to match a wallet action with your account, answer receipt questions, detect unusual activity, and complete required account checks.

Yes. Use the privacy contact route and describe the record you want copied or corrected. We verify that you control the account before releasing data or changing phone and account details.

Yes. The mobile web path may record browser type, device signals, network details, and session events needed for sign-in security. It does not read unrelated photos, messages, or files.

Cookies help maintain your session and remember settings during account access. Browser controls can limit them, but necessary cookie restrictions may interrupt login or require phone verification again.

We retain account, payment-reference, support, and security records for service needs, dispute handling, protection, and legal duties. When the period ends, we delete or anonymise the records.

Use the privacy contact route on this page or the account help path when access is involved. Include your account phone number and request type, never a wallet password or one-time code.