Reference

Open the ares 118 Privacy Policy

The ares 118 Privacy Policy explains how we handle your account data when you access casino rooms, sports pages or local wallet tools in Indonesia.

Account dataWallet recordsDevice choicesPolicy contact
ares 118 Open the ares 118 Privacy Policy
CONTACT ROUTE

Switch to a clear privacy contact path

A privacy question should not require you to search through the lobby. Start from your signed-in account support path and include the phone number linked to…

Account privacy request Use the account support path to ask about data held under your phone-verified profile.
Wallet record check For DANA, OVO, GoPay or QRIS questions, include the payment reference and date rather…
Access trouble If your privacy request follows a login problem, explain the device path and account…
DATA PRACTICE

Browse how we handle your account data

Your account record is handled around the actions you take, so the Privacy Policy separates identity, payment and device purposes.

Phone verification

Before account access, we use the phone verification step to connect your request with the correct profile. This reduces confusion when you ask about account data and helps us avoid discussing a record with the wrong person.

Payment separation

DANA, OVO, GoPay and QRIS references are treated as transaction context, not as a request for your wallet PIN. Bank transfer and virtual account records are used to match payment status with the account action that created it.

Device sessions

When you sign in from a mobile browser or desktop, session and connection details can help us identify an access fault. We use this context for account operation and security checks rather than asking you to repeat private credentials.

Cookie choices

Cookies can keep a session connected and help the account path work as expected. Your Privacy Policy rights still apply to cookie-related data, and you can ask support what record or purpose is connected to a cookie query.

Retention purpose

We retain account and transaction records for the operational purposes stated in the policy, including account support and payment status checks. When you ask how long a record remains, contact us with the relevant account step.

Change requests

You can ask us to access or correct account data, or request removal where the applicable rules allow it. Include your phone-verified account detail and a precise request so we can assess it without collecting unrelated data.

Get answers about Privacy Policy access

These Privacy Policy answers address the questions we expect before you open an account or connect an Indonesian wallet. They cover the data used at sign-in, payment references, cookies, account requests and contact steps. If your case involves eligibility or access, the outcome depends on local law. Keep your request specific so we can respond using the correct account record.

The ares 118 Privacy Policy covers account details, phone verification, sign-in sessions, device context, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can request access, correction or removal where applicable.

We may use a DANA or QRIS transaction reference to match a payment status with your account action. We do not need your wallet PIN for that check. OVO, GoPay, bank transfer and virtual account records follow the same purpose-based approach.

Yes. Send a request through the signed-in account support path and include the phone number linked to your profile plus the exact data category you want. We may ask for an account step to confirm identity before responding to the request.

Contact support with the incorrect field, the corrected value and the phone-verified account detail that identifies your profile. We will assess the request against the Privacy Policy and update the relevant record when the request can be applied.

Yes. It covers cookies and session data used when you access the lobby from a mobile browser or desktop. These records can help keep sign-in working and investigate access faults. Ask support about a cookie purpose if you need a more specific account-level answer.

Retention depends on the operational purpose described in the Privacy Policy, including payment status checks, account support and required record handling. Ask us about a particular DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference for a focused response.

Use the account support route and state whether you want access, correction, deletion or clarification. Include your phone-verified account detail, but never send a wallet PIN or full credential. If access is discussed, it depends on local law.