Reference

indomax88 Privacy Policy for Indonesia

Our Privacy Policy explains what we collect when you open an indomax88 account, sign in from a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesAccess requests
indomax88 indomax88 Privacy Policy for Indonesia
CONTACT ROUTES

Privacy Help When Account Details Stall

A clear contact path helps you ask about the Privacy Policy without explaining your whole account history. Send a request through the account support route and include the phone number or email connected to your profile, the device you used and the subject of your request. Do not send a password, wallet PIN or one-time verification code. We use the details you provide to locate the relevant record and keep the response focused.

Team online

Account access

If you cannot sign in, tell us the device path you used and the phone number linked to your account. We can explain which account details are needed to check access without asking you to disclose a password or wallet PIN.

Wallet records

For a DANA, OVO, GoPay or QRIS query, include the payment rail, date and reference shown on your receipt. We use those details to locate the transaction record while limiting unrelated account data in the response.

Privacy requests

To ask for a copy, correction or deletion review, state the request clearly and identify the account contact. We may ask for an account step to confirm that the request comes from you before changing or releasing personal data.

DATA HANDLING

Inside indomax88 Privacy Controls

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

Account security

We use phone verification before account access and may compare sign-in signals such as device type, browser and IP address. These checks help us identify unusual access and protect the account without placing your password in a support message.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a wallet event to the correct account record. Bank transfer and virtual account references are handled for the same status-check purpose, not as a reason to collect unrelated wallet details.

Cookie settings

Cookies may keep your session active, remember a language or device preference and show whether a page loads correctly. Your browser can block or remove them, although some account access functions may then require you to sign in again.

Mobile signals

When you open the lobby on a phone, we may record screen, browser and connection details needed to diagnose page errors. This can help us investigate access to Fishing War Mobile Play or a stalled account step without reading unrelated phone content.

Retention choices

We keep account, support and payment records for the period needed to provide the requested service, resolve disputes and meet applicable legal duties. When a record is no longer needed for those purposes, our handling process moves it toward deletion or de-identification.

Change requests

You can ask about the data connected to your account, request a correction or ask whether deletion is available. Use the privacy contact route with your account contact details; we may verify identity before acting, and access depends on local law.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the account and wallet questions you are most likely to have before opening an account. We explain the records used during sign-in, payment matching, cookie control and privacy requests in plain terms. If your situation is different, send the relevant account step and payment reference through the contact route so we can assess it under the current policy.

It covers details you submit for an account, phone verification records, device and browser signals, cookie activity, support messages and payment references. This includes activity connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account status when those records are used for account service.

We use your phone number to create and locate the correct account, complete phone verification before access and respond to account requests. It can also help us distinguish two records when a wallet receipt or a failed login is being checked.

Yes. The policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those records to match a receipt, investigate a pending status or answer a request about the related account.

You can send a correction request through the privacy contact route and identify the account contact you use. Tell us which field is wrong and what should replace it. We may verify your identity first, and the available action depends on local law.

Cookies can support your session, remember selected settings and help us see whether pages load correctly on your browser. You can remove or block them through browser settings. If you do, the account path may ask you to sign in again or may not retain preferences.

Send a privacy request with the phone number or email linked to your account and describe the records you want to access. We may request an account verification step before responding. Our ability to provide or limit records depends on local law and applicable retention duties.

You may ask whether eligible data can be deleted by using the privacy contact route. We assess the request against account support needs, payment reconciliation, security records and legal duties. Some records may need to remain for a defined period, where local law permits.