Reference

qqstat88 Terms & Conditions for Indonesia

Our Terms & Conditions explain how we check your account name, how DANA, OVO, GoPay, and QRIS records are matched, and when access can be paused or restored.

Account rulesWallet checksDevice checksLocal law
qqstat88 qqstat88 Terms & Conditions for Indonesia
CONTACT ROUTES

How to reach support

If a term is unclear, we keep three contact routes open: live chat, email, and the account form. Our support desk works daily from 08:00 to 23:00 WIB, and we ask you to send the registered email or phone number so we can match the question to the right account. That makes it easier to explain a clause, track a change request, or confirm why access was paused.

Team online

Live chat

Use live chat when you want a fast read on a clause, a status check on a name mismatch, or help finding the latest version. We answer in English and Indonesian during support hours.

Email desk

Send a written question to email if you want a record of the reply or need to attach a screenshot, wallet label, or device detail. We link the message to your account before we respond.

Account form

The account form is the cleanest path for correction requests, access questions, or a notice that looks wrong on your screen. Use the registered contact details so we can verify the request against the account.

DATA AND ACCESS

How we handle your record

We handle this policy with a short trail: consent logs, login checks, and request tickets stay linked to your account so you can ask what changed and when.

Data use

We only use account data needed to apply the terms, confirm the profile name, and answer a request. If a DANA, OVO, GoPay, or QRIS record does not match, we may ask for another check.

Cookies

Cookies store language choice, session state, and device type on mobile and desktop. If you clear them, we may ask you to log in again so the policy record stays tied to the right device.

Device security

When you switch from Android to desktop or iPhone to browser, we can flag the new device and request one-time confirmation. That helps us stop account changes from being made on a phone you do not usually use.

Retention

We keep consent logs, support tickets, and access changes for a limited period so you can ask what happened later. After that period, we remove or archive the record according to the request type.

Change requests

If your name, email, or wallet label needs a correction, send the request from the registered contact route. We process it only after we confirm the account and check that the change fits the policy trail.

Policy contact

For questions about access, wording, or a decision we made under these terms, contact support through live chat or email. We keep the same reference number on the ticket so you can follow the thread without repeating it.

Questions about the terms

This page answers the questions we hear most about the terms, from access timing to data handling and change requests. If local law does not allow access where you are, we do not open an account there. For anything else, use the contact paths above and quote the section name so we can answer in the same thread. We keep the wording short so you can check the rule before you take any next step.

Yes. We place the terms before account setup, and you can read them on mobile or desktop first. If local law does not permit access where you are, the account is not opened for that location.

The same terms apply on Android, iPhone, and desktop browser. A new phone or a cleared browser can trigger another login check, because we keep the account tied to the device history we see.

We keep only what we need to run the policy: consent logs, support tickets, login records, and the contact details linked to your account. We do not use extra data for unrelated account actions.

A fresh check can happen if the name on your DANA, OVO, GoPay, or QRIS record does not match the profile, or if the device looks new. We ask before we move the request forward.

Yes, if the change is allowed by the policy and local law. Send it from your registered email or phone number, then we match the request to the account before any update is made.

Use live chat or email and quote the clause name, or add a screenshot from the account form. We keep the reply in the same thread so you can read it later.

We keep records for the period needed for the request type, such as support history or access checks, then archive or remove them under our retention rules. The exact period depends on the record.