Reference

ares 118 Privacy Policy For Your Account

The ares 118 Privacy Policy explains how we collect, use and protect the account details behind your casino, sports and wallet access.

Clear data purposesWallet record controlsAccess request path
ares 118 ares 118 Privacy Policy For Your Account
GET POLICY HELP

Choose A Clear Privacy Contact Route

A privacy question should not become a cashier problem, so we keep the request route tied to your account details and the exact record you want checked.

Account data request Use the account help path when you want to ask what personal data we hold, why it was collected or which account step created the record. Include your registered contact detail so we can identify the correct account without asking for your password.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, describe the date, status and account action rather than sharing sensitive wallet credentials. We can check the payment record connected to your account and explain whether the issue is a privacy matter.
Correction or deletion Ask us to correct an inaccurate detail or consider deletion through the privacy contact route. We may need to verify account ownership first, and some records may need to remain for security, dispute handling or where local law permits.
HOW WE HANDLE DATA

Browse The Controls Behind Your Privacy

The Privacy Policy is practical: it describes the information we use, the reason for each use and the choices available to you.

Data we receive

We may receive account contact details, phone verification results, login timestamps, device and browser signals, selected account actions and payment references. These details help connect the correct account to a cashier status without requiring us to collect your wallet password.

Why we use it

We use account data to provide access, confirm security steps, display wallet status and answer a receipt question. A record connected with Live Baccarat Elite or Slot Tournament Hub is handled for account and service purposes, not as a reason to collect unrelated details.

Cookies and devices

Cookies and similar device signals can keep a session working, remember practical preferences and help us detect unusual login behaviour. Your mobile browser may create a different security event from desktop access, so we may ask which device path produced the alert.

Account protection

Phone verification comes before account access, and security checks can compare a new device with earlier login activity. If a login or wallet status stalls, use the account help path instead of sending a password, wallet PIN or complete payment credential.

Retention choices

We keep information only for the period connected with the stated purpose, account security, dispute handling or a legal requirement. When you request deletion, we assess the record first because some transaction or access evidence may need to remain where local law permits.

Your policy request

You can ask for access, correction, explanation or deletion through the privacy contact route. Give us your registered contact detail and a precise request; after ownership checks, we can explain the action taken and any record that cannot be removed.

Find Answers About Privacy Policy

These Privacy Policy answers cover the questions we expect before an Indonesian account is opened or a wallet record is checked. They explain the practical connection between account access, device activity, local payment references and your data requests. If your situation is not covered, use the policy contact route with the smallest useful detail and do not include a password or wallet PIN.

The ares 118 Privacy Policy covers account details, phone verification, login and device records, payment references, cookies, retention and requests to access or correct data. It also explains how we handle records linked with DANA, OVO, GoPay and QRIS when checking account status.

Phone verification helps connect account access with the correct contact detail and supports security checks when a new device signs in. We record the verification result rather than asking for your wallet PIN. If access or eligibility is discussed, it depends on local law.

Yes. The Privacy Policy covers the payment references and status details connected with your account when you use DANA or QRIS, as well as OVO and GoPay. We use those details to check a receipt or cashier status, not to request your private wallet credentials.

Use the privacy contact route and provide your registered contact detail plus a specific request for the data you want to see. We verify account ownership before responding, then explain the available record, its purpose and any reason a particular detail must remain.

You can request a correction when an account detail is inaccurate and ask us to consider deletion when the stated purpose no longer applies. We first verify the request. Security, dispute or legal records may need to remain where local law permits.

The Privacy Policy covers practical device and browser signals used for session continuity, preference handling and unusual-login checks. A mobile visit to Slot Tournament Hub can create different security details from desktop access. We use those signals for account protection and service operation.

Describe the account action, date and status shown for DANA, OVO, GoPay, QRIS, bank transfer or virtual account, without sending a password or full credential. We can then separate a data request from a cashier-status question and direct it to the correct account path.