Reference

qqbonus Legal Starts With Clear Account Rules

qqbonus Legal sets out how account access, wallet records and personal data are handled before you open the lobby.

Account accessData requestsWallet recordsLocal-law access
qqbonus qqbonus Legal Starts With Clear Account Rules
CONTACT ROUTES

Get Direct Help With Legal Questions

A clear contact path matters when your Legal question concerns account access, a wallet record or a data request.

Account access Use the signed-in account-help route when your Legal question concerns phone verification, a locked profile or the details attached to your account. Include the contact detail on file so we can check the correct record before explaining the next step.
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference through the cashier support path. We use that reference to distinguish a status check from a request about how payment data is handled.
Policy requests If you want a copy, correction or clarification of personal data held with your account, contact us from the verified account route. State the request plainly, and we will explain any identity check needed before handling it.
DATA PRACTICE

How qqbonus Handles Legal Records

Our policy process is designed around traceable account actions rather than vague promises. We connect phone verification, login activity and payment references to the relevant account record, while keeping policy enquiries separate…

Data handling

We use account details to identify the profile connected to a Legal request, confirm the requested change and connect payment references to the correct record. A request about DANA or QRIS is handled as an account-linked matter, not as an open public enquiry.

Cookie choices

Cookies can support login continuity and account-area settings on your device. If you ask about cookie use, tell us the device path involved, such as mobile browser or desktop browser, and we can direct your question to the relevant policy route.

Account security

Phone verification forms part of the account access process, and we may ask for matching details before discussing private records. Do not send passwords in a support message; use the signed-in route so the request stays connected to your account.

Record retention

We retain account and payment records only as required for the stated account, policy and transaction purposes. If you ask how long a particular record is kept, include its type or reference so we can provide a more precise response.

Change requests

You can ask us to correct an inaccurate account detail or clarify how a record is used. Submit the request after phone verification and identify the field concerned, such as contact number, wallet reference or account name.

Policy contact

For a Legal matter that does not fit account or cashier support, use the policy contact route from your account area. Explain the issue in English, include the relevant date or reference, and we will identify the appropriate next step.

Common qqbonus Legal Questions

These Legal answers cover the questions you may have before opening an account or sending a policy request. We keep the wording practical: account access depends on local law, payment records remain linked to the relevant profile, and data enquiries should use the verified contact path. If your situation is unusual, send the details through account help so we can assess the correct route.

qqbonus Legal covers account access, phone verification, personal-data handling, cookies, payment records, retention and contact routes for policy requests. It also explains that access depends on local law, so you should check whether use is permitted in your location before opening an account.

Access from Indonesia is available only where local law permits. We ask you to complete the account path and phone verification before account access, and you remain responsible for checking local eligibility. A payment option such as DANA or QRIS does not change that condition.

DANA and QRIS references are connected to the account activity that created the transaction, so we can check the correct record when you contact support. For a Legal question, use the signed-in cashier route and provide the payment reference rather than sending private details publicly.

You can ask us to clarify how an account record is used, request a copy where applicable, or seek correction of an inaccurate detail. Submit the request through the verified account route, identify the field or record, and complete any identity check we explain.

Send a cookie question through account help and mention whether you used a mobile browser or desktop browser. We can explain the policy route connected to login continuity and settings. Avoid including your password or unrelated payment details in the message.

Retention depends on the type of account or payment record and the purpose for keeping it. Ask through the policy contact route with the relevant reference, such as a GoPay, OVO, bank transfer or virtual account record, and we will explain the applicable handling.

Start with the signed-in account-help route and describe the dispute, date and connected reference. Use the cashier support path when it concerns wallet status. If it is a policy matter, we will direct it to the appropriate contact route for further handling.