Reference

Privacy Policy For Your abl138 Account

abl138 Privacy Policy gives you a clear view of how we handle account details, device signals and wallet records when you use our Indonesia-facing service.

Account data explainedWallet records coveredYour access choicesPolicy contact path
abl138 Privacy Policy For Your abl138 Account
CONTACT ROUTES

Get Privacy Help Beside Your Account

A direct support route matters when a privacy request concerns the wrong account or an unclear wallet record. Start from the support chat linked to your account screen and include the phone number or receipt reference you want us to check. We ask for enough detail to locate the record, but not for your wallet password or full sign-in secret. For a request from Jakarta, Surabaya or another Indonesian location, access still depends on local law.

Team online

Account privacy request

Use the support chat attached to your signed-in account when you want a copy, correction or explanation of personal data. We check the account step first so a request about phone verification or a DANA record reaches the correct account.

Wallet record check

If an OVO, GoPay or QRIS reference appears incorrectly, send the receipt code and approximate date through support chat. We use that reference to trace the payment status without asking you to share a wallet password.

Access and deletion query

Ask us through the same account support route whether a requested record can be accessed, changed or removed. We may need to confirm phone ownership before discussing private details connected with your account.

HANDLING PRACTICES

What abl138 Does With Your Data

Privacy Policy decisions are tied to real account actions rather than a generic data label.

Account details

We may handle your phone number, verification result and account identifiers to open and protect your account.

Payment references

A DANA, OVO, GoPay or QRIS receipt reference can be retained to match a deposit status or resolve a cashier…

Device signals

Browser type, device indicators and sign-in timing may be used to spot unusual account access.

Cookies and sessions

Cookies can keep a signed-in session active, remember a selected setting and support the path from mobile login to your…

Retention decisions

We keep records only for as long as needed for the stated account, security, support or payment-reconciliation purpose, unless a…

Changes and requests

Contact our support chat to request access, correction, restriction or deletion of eligible personal data.

Privacy Policy Questions About abl138

These Privacy Policy answers address the account and payment questions that commonly arise before you open an account. We keep the wording practical: what is collected, how a request starts, how device activity is treated and what happens when local access rules apply. If your case involves a specific receipt or phone verification step, use the support route connected with your account.

The abl138 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm that the person asking about an account record is connected with that account. It also supports sign-in protection and reduces the chance that private details are sent to the wrong person.

No. Our handling of a DANA, OVO, GoPay or QRIS payment usually relies on a receipt or transaction reference, not your wallet password. Do not send a wallet password through support chat or any account message.

Open the support chat linked to your signed-in account and request access to your personal data. State the account phone number and the type of record you want checked. We may verify ownership before releasing private details.

Yes, you can request a correction when an account detail or payment reference is inaccurate. Send the existing value, the proposed correction and a supporting receipt where relevant. We review the request against the account record before making a change.

We retain personal data for the account, security, support or payment-reconciliation purpose that requires it, subject to applicable rules. When the purpose ends, eligible records may be deleted, restricted or anonymised according to our retention process.

The policy applies to account activity handled through our service, but access or eligibility depends on local law. If you are unsure whether access is available from your location, check the current account prompt or contact support before proceeding.