Reference

abu188 Privacy Policy For Your Account

abu188 Privacy Policy explains what account, wallet, device and support details we use when you open an account and move through our lobby.

Clear data purposesWallet status checksPolicy contact pathIndonesia access
abu188 abu188 Privacy Policy For Your Account
CONTACT OPTIONS

Get Privacy Help Through Your Account

A privacy question should not require you to explain your whole account history. We keep the contact path close to the account area so you can identify the relevant login, wallet reference…

Account access request Ask us to confirm the account details connected with your phone verification or login record. We may request an account identifier before responding, so the request reaches the correct account without exposing another person's data.
Wallet reference check For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the payment reference and date rather than wallet credentials. We use that narrow detail to trace status and answer a privacy request safely.
Correction or concern Tell us which account detail, cookie choice or retention point you want reviewed. We can explain the handling step, record a correction request and ask for further proof only when account security requires it.
DATA PRACTICE

How abu188 Handles Privacy Details

Privacy work starts with using each detail for a defined account or service purpose, then limiting access to the people and systems that need it.

Account data

We use your account details to create access, send account-related replies and maintain the sign-in path. Phone verification can be used to confirm that a request comes from the person connected with the account, especially after an unusual device session.

Payment references

A DANA, OVO, GoPay or QRIS reference lets us match a wallet event with the correct account. Bank transfer and virtual account details support reconciliation and status checks; we do not ask for a wallet password through support.

Device signals

When you move from a mobile browser to desktop, we may record session, browser and connection signals for account security. These details help us investigate access trouble around the lobby without treating device data as your full identity.

Cookies

Cookies can keep your session active, remember a selected page and show whether a policy page loads correctly. You can adjust cookie controls in your browser, although removing required cookies may interrupt login or the account path.

Retention

We retain account, support and payment-reference records only for the period needed for the stated service, security, dispute and legal purposes. A deletion or access request may have limits when a record must remain for an ongoing check.

Policy requests

You can ask what personal details we hold, request a correction or raise a handling concern through account support. Include the request type and account identifier; never send your password, wallet PIN or full payment credentials.

Privacy Policy Questions About abu188

These Privacy Policy answers address the account situations you are most likely to meet, from a new phone login to a wallet reference or cookie choice. We keep each answer tied to an actual handling step, and we will ask for only the proof needed to protect your account. Where local law permits, you can use the same support path for access or correction requests.

The abu188 Privacy Policy explains how we handle account, phone verification, device, cookie, support and payment-reference details. It also describes why we use them, how retention works and how you can request access, correction or clarification where local law permits.

We may handle details needed for account access, such as your phone contact, login records, device signals, support messages and account activity. We use these details for access, security and service handling rather than asking for unrelated personal material.

We may retain a payment reference, amount status and related account record for DANA, OVO, GoPay or QRIS reconciliation. We do not need your wallet password or PIN for a support request, and you should never send either through the contact path.

When you sign in from a new mobile browser or desktop, we may record session and browser signals to help protect the account. If access needs confirmation, phone verification or an account identifier may be requested before we discuss details.

Yes. Send an account access or correction request through support with the relevant account identifier and a clear description of the record. We may verify ownership first, then explain what can be supplied or changed under local law.

Retention depends on the purpose: account security, support history, payment reconciliation, dispute handling or a legal requirement. We keep records for the period needed for that purpose, and a deletion request may be limited while an active check remains.

Use the account support path and state that your request concerns the Privacy Policy. Include the account identifier, request type and any DANA, QRIS or bank transfer reference involved, but leave out passwords, PINs and full payment credentials.