Reference

Privacy Policy for Your indo18 Account

Our Privacy Policy explains how indo18 handles the account details you provide before you enter the lobby, including your phone number, verification records, device signals and wallet references.

Account dataWallet referencesCookie choicesPolicy requests
indo18 Privacy Policy for Your indo18 Account
REQUEST A HAND

Get Privacy Help Beside Your Account

A clear support route helps when your account details, phone verification or wallet status needs correction. From your indo18 account, keep the relevant username, registered phone number and payment reference ready, then contact our support path shown near the account and cashier area. We use those details to locate the correct record without asking you to send a wallet password, card PIN or full banking login. If access is unavailable, include the device type and the last step you completed so we can assess the request where local law permits.

Team online

Account access

If your phone verification does not complete, contact us through the account support path and include your registered number, device type and approximate sign-in time. We use those details to locate the right record while avoiding requests for your wallet PIN or banking password.

Wallet reference

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, send the transaction reference shown in your account. We check the payment record attached to your profile and do not need your private wallet credentials to handle a status question.

Privacy request

To ask about a stored detail, correction or removal request, use the policy contact route and describe the record concerned. We may ask for account verification before acting, because changing personal data without confirming the account could expose your profile to another person.

DATA PRACTICE

How indo18 Handles Your Data

Privacy depends on practical controls, not broad promises. We separate account access details from payment references, limit internal use to a stated service or security purpose, and check identity before changing sensitive…

Account details

When you open an account, we handle details such as your phone number, login record and verification result so we can recognise your profile across the mobile login path. We use the minimum account context needed to provide access and investigate sign-in problems.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount status and time record linked to your account. Bank transfer and virtual account checks use the matching reference, not your banking password or wallet PIN, to confirm the request.

Cookies and devices

Cookies may keep your session active, protect the login path and remember browser settings. We can also record device or connection signals when needed for security. You can clear or restrict cookies in your browser, although some account functions may then require another sign-in.

Account security

Phone verification and sign-in events help us detect access that does not match your usual account pattern. Never send us a one-time code, wallet PIN or banking password. If your device is shared, sign out after checking the lobby and remove saved browser credentials.

Retention period

We keep account, security and transaction records only for the period needed for the purpose collected, account support, dispute handling or a legal duty where local law permits. When a record is no longer needed, we delete it or remove identifying links where practical.

Changes and requests

If your phone number or another account detail changes, use the account support route rather than opening a second profile. You may ask what personal data we hold, request a correction or ask about deletion, subject to identity checks and applicable local law.

Privacy Policy Answers for indo18

These Privacy Policy answers cover the searches we hear most often before account access: what data we collect, why wallet references appear, how cookies work, how long records remain and how to contact us. Read the relevant answer before opening an account, especially if you use a shared phone or need a correction to your registered details.

It covers account details, phone verification, device and connection signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains security use, retention, your request routes and access where local law permits.

We use your phone number to create and identify the correct account, complete the phone verification step and help recover access when a login stalls. We do not ask you to send a wallet PIN or banking password. Keep the number current through the account support path.

No. A wallet status or payment reference tells us about the transaction record attached to your account; it does not give us your DANA, OVO or GoPay password or PIN. The same approach applies to QRIS, bank transfer and virtual account references.

Use the privacy contact route beside your account support area and identify the detail that needs correction. We may ask you to confirm your registered phone number or another account step before changing it. This protects your profile from an unauthorised request.

Cookies can keep a mobile or desktop session active, support sign-in protection and remember selected settings. Your browser lets you clear or restrict them. If you block required cookies, you may need to sign in again or some account pages may not work as expected.

We retain records for the service, security, dispute or legal purpose for which they are needed, subject to local law. Account and payment references may remain after a transaction so we can trace a status question. We remove or de-identify records when retention is no longer needed.

Yes. Send a request through the Privacy Policy contact route with enough account detail for verification. We can explain the handling purpose and relevant record category. Access, correction or deletion requests may be limited where responding would conflict with security duties or local law.