Reference

Privacy Policy for online 138 Accounts

Our Privacy Policy explains how we collect, use and protect the details connected with your online 138 account, including login records and wallet activity.

Account clarityWallet recordsCookie choicesData requests
online 138 Privacy Policy for online 138 Accounts
CONTACT YOUR WAY

Get Privacy Policy Help Near Login

A clear contact path matters when you want to ask about personal data rather than a wallet balance.

Data request Ask us which account details we hold, why they are used and which service step created them. Include your verified phone number and a clear request so we can confirm ownership before discussing personal data.
Wallet question For a DANA, OVO, GoPay or QRIS question, send the payment reference and approximate time shown in your cashier record. We compare the receipt with the account event before replying about stored transaction details.
Access concern If login access changes after a device switch, tell us the account phone number and device path you used. We can explain the security check and the relevant Privacy Policy process without requesting your password.
OUR DATA PRACTICE

Privacy Policy Details We Apply

We handle account data as part of specific operating tasks: confirming access, recording wallet events, protecting sessions and answering a request.

Account data

We may store your account name, phone verification result, login events and support messages. These records connect the account step to the person requesting access and help us detect an unusual sign-in before account details are disclosed.

Payment records

Cashier activity can include DANA, OVO, GoPay, QRIS, bank transfer or virtual account references. We use those references to reconcile a status or receipt, not to request unrelated wallet credentials from you.

Cookies

Cookies can remember a session choice and help us see whether a page loads correctly on your device. You can manage browser cookie settings, although changing them may affect login continuity or saved preferences.

Device security

A phone verification check and login event can be used together when you move from mobile to desktop. We may ask for account details already linked to you, but you should never send a password or wallet PIN.

Retention

We keep account, support and payment records for the time needed to provide the requested service, resolve a dispute, protect the account or meet a valid legal duty. When a record is no longer needed, we remove or isolate it under our internal process.

Policy changes

If the Privacy Policy changes, we place the updated wording on this page and identify the effective date. Check this page before opening a new account or using the lobby, especially when access depends on local law.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the account data, payment references, cookies, device checks and contact steps that matter when you use online 138 from Indonesia. If your situation is unusual, contact us with the verified account details and we will direct the request through the applicable policy path.

It covers details linked to your account, phone verification, login events, cashier activity, cookies and support messages. It also explains how we use payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity for account and status checks.

We use your phone number to create the account path, complete the access check and help distinguish your request from another account. The Privacy Policy explains how verification records are used for security and support, and you should keep the number and login details private.

The Privacy Policy allows us to retain transaction references, status results and receipt details needed to match a DANA or QRIS event with your account. We do not need your wallet PIN. For a query, send the reference through the stated support path.

Yes. You can request a description or copy of the personal data connected with your account. We first verify ownership using the account phone number or another account step, then explain the stored fields, their purpose and any reason a record must remain.

Cookies may remember your session and help us diagnose page loading on mobile or desktop. Browser controls let you manage them, but refusing some cookies can interrupt login continuity. The Privacy Policy describes the cookie purpose so you can make a clear browser choice.

We retain account, payment and support records for the period needed for service delivery, security, dispute handling or a valid legal duty. The exact period can differ by record type. When the purpose ends, we remove or isolate the record under our retention process.

Contact us through the account support path, state whether you want a correction or deletion, and include the phone number linked to your account. We verify the request, check any payment or security reason for retention, then respond under the Privacy Policy process.