Reference

ares 118 Privacy Policy for Indonesia Accounts

Clear account-data choices come first in the ares 118 Privacy Policy. We explain what we collect when you open an account, verify your phone, use DANA or QRIS…

Account dataWallet recordsCookie choicesPhone verification
ares 118 ares 118 Privacy Policy for Indonesia Accounts
CONTACT PATH

Ask About Your Account Data

A clear contact path helps when you want to ask about the Privacy Policy, correct a phone detail or check a wallet reference.

Account data desk Use our support route for access, correction or deletion questions about your account details.
Wallet reference check For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the receipt…
Device access route If a mobile or desktop session shows an unexpected privacy prompt, contact support through…
DATA PRACTICE

Inside ares 118 Data Handling

We keep this policy practical by linking each data use to an account step you can recognise. Phone verification supports account security; cookie settings help a mobile session remember essential choices; and…

Account opening

We collect the details needed to create and maintain your account, including contact data and the account step connected to phone verification. We do not ask you to place passwords inside a support message or payment receipt.

Phone verification

A phone check helps connect the right person to the right account during access requests. We record its status and related security events, while keeping the verification detail separate from wallet credentials used through DANA or GoPay.

Cookies and sessions

Cookies may remember essential sign-in and privacy choices between pages. On mobile, they help keep the path from login to the lobby consistent; you can adjust non-essential cookie choices through the available browser or site controls.

Payment references

We use transaction references, amounts and status details to match an account action involving QRIS, OVO, bank transfer or a virtual account. We do not need your wallet password to investigate whether a receipt reached the correct account.

Security records

Login time, device type, browser details and connection signals can help us identify unusual account access. These records support account protection and investigation, not a request for your private files or unrelated device content.

Retention and changes

We keep personal data only for the operational, security or legal purpose that requires it, then remove or anonymise it when appropriate. To request a correction or ask how a record is retained, contact us through the stated support path.

Privacy Policy Questions for Your Account

These Privacy Policy answers cover the searches we expect from an Indonesian account holder before opening an account. We focus on the records created by phone verification, mobile access, cookies and local payment rails, with each request assessed under the law that applies to your account and location.

It covers account details, phone-verification status, login and device records, cookies, support messages and payment references. It explains why we use each category, how we protect it, when retention ends and how you can ask for access, correction or deletion where local law permits.

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may receive a reference, status, date and amount linked to your account action. We do not need your wallet password or full wallet access to check a receipt.

We store the verification status and related account-security events so we can tell whether the phone step was completed. If you ask about a particular record, contact support with your registered contact; we will assess the request under applicable local law.

Essential cookies can keep sign-in and privacy choices working as you move between pages. Other cookies may support site measurement or session functions. You can adjust available choices through your browser or the site control, though disabling essential cookies may affect account access.

Yes, send the request through our account-data support route and identify the contact attached to your account. Tell us whether you want a copy, correction or deletion. We may need to verify the request, and the result depends on local law and retention duties.

We retain records for the operational, security or legal reason that requires them, including payment-status checks and account protection. When a record is no longer needed, we remove or anonymise it where appropriate. Support can explain the purpose connected to a requested record.

Use the support route linked near the cashier path and describe your privacy request without sending a password, wallet PIN or unrelated document. Include your registered contact and any DANA, QRIS or device reference needed to locate the relevant account event.