Reference

aci138 Privacy Policy For Your Account

aci138 Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby and use DANA, OVO, GoPay or QRIS.

Account recordsWallet activityCookie choicesSupport requests
aci138 aci138 Privacy Policy For Your Account
ASK ABOUT PRIVACY

Reach Our Privacy Support Path

A clear support route helps you resolve a privacy question without sending sensitive details through an open game chat. Start from the support link on the login page or inside your account, then include the phone number linked to your profile and the subject of your request. If your question concerns a DANA, OVO, GoPay or QRIS receipt, attach only the transaction reference shown in the cashier status screen. We use that reference to locate the record while limiting the personal details shared in a message.

Team online

Account privacy request

Use the support route beside login when you want to ask what account data we hold, correct a phone detail or request a copy of records tied to your aci138 profile.

Wallet record question

For DANA, OVO, GoPay or QRIS data, send the cashier reference rather than a PIN. We can trace the status and explain which transaction details remain in our records.

Access concern

If a privacy request is blocked by account access, tell us through the login support path. We may ask for phone verification before discussing records or changing account details.

DATA HANDLING

Browse Our Account Data Practices

We keep this policy practical by tying each data category to a visible account action. Login records help us detect unusual access, wallet references help us reconcile receipts, and cookie settings help…

Phone verification

Before we discuss account records or change key details, we may check the phone number connected to your profile. This step helps prevent another person from receiving or changing your data.

Login and device records

We may record login time, browser details, device signals and security events. These records help us identify unusual account access across a mobile browser, tablet or desktop session.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount and status record. We use those fields to match the cashier event to your account.

Cookie controls

Cookies can remember session choices and help keep the login path working. You can adjust browser controls, although blocking required cookies may interrupt account access or remove saved preferences.

Retention checks

We retain records for the purpose that created them and review whether storage is still needed. Transaction and security records may remain when legal, fraud-prevention or account-reconciliation duties require them.

Request changes

Send a request through support with your account phone number and the precise change you want. We may ask for verification, then confirm what can be corrected, exported or removed.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the searches we hear most often before account access. You can use them to understand phone verification, wallet records, cookies, retention and contact steps without guessing which support route applies. If your case involves a legal restriction or an account you cannot open, reach us through the login support path and we will explain the next check.

It covers account details, phone verification, login and device records, cookies, wallet references, support messages and retention. It also explains how we use those records for access, security, receipt matching and requests made under applicable law.

We use your phone number to create and verify the account, support account recovery and confirm sensitive requests. Before changing key details or discussing stored records, we may ask you to complete phone verification.

Yes. The Privacy Policy covers transaction references and status data linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions. We use these details to match a cashier event and do not ask for your wallet PIN.

Open the support route from the login page or your account and state that you want a copy of records linked to your profile. Include your account phone number; we may verify it before sharing any personal data.

You can request a correction through account support and describe the exact field that is wrong. We may confirm your phone number first, then assess the request against account security, transaction matching and applicable legal duties.

Required cookies help keep your login session and selected settings working as you move from the mobile login page to the lobby. Browser controls can remove or block cookies, which may require you to sign in again.

Retention depends on why the record was created and whether legal, security or transaction duties still apply. Login events, wallet references and support requests can therefore have different storage periods. Ask support for a request-specific explanation.