Reference

apg9 Privacy Policy for Indonesia

The apg9 Privacy Policy explains how we use account details, device signals and wallet records when you access our Indonesia lobby.

Account clarityWallet recordsDevice controlsPolicy requests
apg9 apg9 Privacy Policy for Indonesia
REQUEST SUPPORT

Reach Us About Privacy Policy

A clear support route helps when you want to ask about the Privacy Policy rather than troubleshoot a lobby screen. Start from your signed-in account support area and include the email or phone detail attached to your account, plus the subject of your request. If your question concerns a DANA receipt, QRIS reference or device login, send only the relevant reference and hide unrelated wallet details. We use the account path to reduce mistaken identity and direct privacy questions to the right handling queue.

Team online

Account request

Use the signed-in support path for an access, correction or deletion request. Include your account contact detail and a short description of the Privacy Policy question so we can connect the request to the correct record.

Wallet reference

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the payment reference only. We can check the matching record without asking you to send a wallet password, full security code or unrelated account details.

Login concern

If a phone verification or device login concern affects your privacy request, tell us the device type and approximate login time. Do not send a password. We use those limited signals to locate the relevant access event.

DATA HANDLING

How apg9 Applies This Policy

The Privacy Policy works alongside the account controls you use each day. We separate identity details, technical access signals and payment references so a question about QRIS does not require broad access…

Account data

When you open an account, we use the contact details you submit to create access and complete phone verification. We keep those details connected to your account request, not as a general profile for unrelated purposes.

Device signals

A mobile login can create records such as device type, browser setting, session time and failed access attempts. These signals help us investigate account access and are considered within the Privacy Policy when you move from login to a game page.

Cookies

Cookies and similar files can remember a session, language choice or page state. If you clear them, the lobby may ask you to log in again or repeat phone verification; this change does not erase account records by itself.

Payment records

A DANA, OVO, GoPay or QRIS payment can leave a reference, amount and status linked to your account request. Bank transfer and virtual account records follow the same matching need, while wallet passwords stay outside our requested support details.

Retention approach

We retain account, access and payment records for the period needed to operate the account, investigate security concerns and meet applicable duties. A retention question can be sent through support with the specific record or account step you mean.

Change request

Where local law permits, you can ask to access, correct or request removal of personal details. Sign in first when possible, identify the relevant account contact and explain whether the request concerns login, a game page or a wallet reference.

Privacy Policy Questions for Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or sending a payment-related request. We keep the examples practical: phone verification, mobile sessions, QRIS references and named lobby pages can all create different records. If your question is not covered, use the signed-in support route and describe the exact account step.

The Privacy Policy covers details you submit for account access, such as contact data used during phone verification. It also covers related login, device and payment records needed to operate the account and respond to a specific support request.

Yes. The Privacy Policy covers payment references, status and matching details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records. Do not send wallet passwords or full security codes in a support request.

Where local law permits, you can request access or correction of personal details held for your account. Use the signed-in support path, identify the account contact and state which detail is wrong so we can assess the request against the relevant record.

A mobile or computer session may create device type, browser setting, login time and failed-access signals. The Privacy Policy treats these as technical records used for account access and security checks, including when you open Live Blackjack Grand or Aviator Mobile Play.

We keep records for the period needed to operate account access, match payment status, investigate security concerns and meet applicable duties. The exact period can depend on the record and local requirements; ask support about a named account or payment reference.

Sign in and use the account support path, then describe whether your request concerns access, correction, removal, device data or a payment reference. Include only relevant details, such as a QRIS reference, and never include a password.

No. Clearing cookies can end a saved session, remove a page preference or require phone verification again, but it does not automatically remove account, device or payment records. Send a separate request through support if you want a permitted data action.