Reference

acgwin Privacy Policy For Your Account

acgwin Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and move between the lobby and your wallet.

Account dataWallet recordsCookie choicesSecurity checks
acgwin acgwin Privacy Policy For Your Account
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact route helps you act on your Privacy Policy rights without guessing which team to reach. Use our support path for account access questions, wallet records, cookie choices or a request to change personal details. Include the account phone number or email connected with your request, but do not send a password, wallet PIN or full payment credential. We may ask for a verification step before discussing account data. This protects you whether you are checking a QRIS status from Bandung or asking about a device session.

Team online

Account data request

Ask us to confirm the personal data linked with your acgwin account. We may request your verified phone detail or another account step before sending records, so private information is not released to the wrong person.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the transaction reference and date through support. We can check the matching status without asking you to disclose a wallet PIN or full credential.

Correction or deletion

Tell us which detail needs correction or which account data request you want to make. We review the account context first because some records may need to remain available for security, payment matching or a legal request.

DATA PRACTICES

How We Handle Your Privacy Policy

We keep the Privacy Policy practical by linking each data use to an account task you can recognise.

Data we receive

We may handle account details, verified phone information, device signals, session activity, payment references and messages you send to support. Pages such as Aviator Mobile Play or Fishing War Mobile Play may appear in service records when needed for operation or security.

Account protection

Phone verification and session checks help us separate your account from an unapproved login. Keep your password private, sign out on shared devices and contact support if a device path looks unfamiliar. We do not ask for your password through a support message.

Cookies on your device

Cookies can remember required site settings, support session continuity and help us understand technical errors. You can review cookie controls in your browser, although blocking required cookies may affect login, account pages or the route from mobile access to the lobby.

Payment references

A wallet or bank record may include a reference, amount status and processing time connected with DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI. We use these details to match a transaction and investigate a status question.

Retention choices

We retain account, support and payment records only as long as needed for the purpose described, account protection, dispute handling or a legal requirement. When you ask for removal, we explain if a record must remain and why the period applies.

Requesting changes

You can ask for a copy, correction, restriction or deletion of relevant personal data through support. Include the account contact and a precise request. We verify ownership first, then explain the action, timing and any limit that depends on local law.

Privacy Policy Answers For acgwin

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep the wording tied to real acgwin steps, including phone verification, mobile sessions and local wallet references. If your situation is not covered, contact support with the smallest amount of detail needed to identify your account.

The acgwin Privacy Policy covers details you provide when opening an account, your phone verification result, device and session signals, payment references and support messages. We use them for account access, payment matching, security and service operation, not for unrelated requests.

Yes. Our Privacy Policy covers payment references linked with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account status. We use a reference and processing detail to investigate a transaction, and we do not ask for your wallet PIN.

Send a Privacy Policy request through our support route and identify the account with its verified phone detail or email. State whether you want a copy, correction or deletion. We confirm account ownership before discussing records so the request reaches the right person.

Phone verification connects you with the correct account and gives us a security step when you request account changes or data access. It may also help us investigate an unusual session. We use this process as part of the Privacy Policy controls around account protection.

Our Privacy Policy includes technical details from the device and session used to reach the site. These details can help maintain login continuity and identify errors when you move from a mobile browser to the lobby. Review browser cookie controls if you want to adjust storage.

You can request correction or deletion through support, with enough account detail for us to verify ownership. We review the request under the Privacy Policy and explain any record that must remain for payment matching, security, dispute handling or a requirement that depends on local law.

You can read this Privacy Policy on the acgwin privacy page before completing the account path. Check the sections on data, cookies, payment references, retention and contact requests. If access or eligibility is discussed, it depends on local law or where local law permits.