Reference

poa88 Privacy Policy For Your Account

poa88 Privacy Policy explains how we collect, use and protect the details linked to your account, phone verification and wallet activity.

Account dataWallet recordsCookie choicesPolicy requests

Browse Our Lobby Read FAQ

How We Handle Account And Wallet Data

poa88 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy sets out which details we receive when you create an account, complete phone verification, sign in, contact support or use the cashier path. We may record account identifiers, device and browser signals, login events, selected lobby pages and transaction references needed to match

1
a wallet request. DANA, OVO, GoPay and QRIS may appear in those records when you choose them, while bank transfer and virtual account references help us reconcile a payment. We use this information to provide access where local law permits, check account security, answer policy requests
2
and investigate payment status. We limit access inside our operations to people who need it for these purposes, and we do not ask for your wallet PIN through support messages.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Ask About Privacy Beside Your Account

A clear contact path helps when you want to check a record, correct a detail or ask why a wallet event appears in your account history.

Account request Use the support path inside your signed-in account to ask for access, correction or removal of personal details. We will use the account contact already linked to your profile.

Wallet record If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include its date and status. Do not send a wallet PIN; we only need details that help locate the record.

Access concern For a login or phone-verification concern, tell us which device path you used and what appeared on screen. We may request identity checks before changing account information.

CONTROL DETAILS

Six Ways We Keep Policy Practical

Our approach is built around the actions you can take, not broad promises. You can read this Privacy Policy before account access, check cookie choices on your browser, and contact us when…

Collection at entry

We collect details when you open an account, enter a phone number, sign in, contact support or choose a payment route. This lets us connect an action with the correct account record.

Device signals

Browser type, device details and login events can help us identify unusual access. We use these signals for account protection and service records, rather than asking for your wallet PIN.

Cookie choices

Cookies can remember sign-in state, language settings and page preferences. Your browser controls can clear or restrict them, although some account screens may then need another sign-in.

Payment matching

A payment reference from DANA, QRIS, OVO, GoPay, bank transfer or virtual account helps us match a cashier event to your account without requesting private wallet credentials.

Retention approach

We keep records for as long as needed for the stated account, security, support and transaction purposes, then review whether continued storage remains necessary.

Change requests

You can ask us to view, correct or remove eligible details through account support. We verify the request first, then explain any limit that depends on local law.

Privacy Policy Questions Before Access

These Privacy Policy answers cover the account actions Indonesian customers ask about most often. If your situation involves a specific login, device or wallet reference, use the account support path so we can locate the relevant record. Access and any request outcome depends on local law.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with your use of poa88. It also explains purposes, retention and request paths.

Phone verification helps connect account access to the correct person and supports security checks. We may use the phone detail to confirm a request before changing profile or login information.

No. Our Privacy Policy does not require your DANA or QRIS wallet PIN through support. We may retain transaction references and status details needed to match a cashier event.

Records may relate to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use references, dates and statuses to reconcile account events and answer payment questions.

You can send an access request through account support using the contact detail linked to your profile. We may verify your identity, and the response depends on local law.

Contact support from your signed-in account and identify the detail that needs correction. We may ask for phone verification or another account step before applying a change.

Check your browser cookie controls and send us a policy request if you need clarification. Clearing cookies can remove saved sign-in state and may require another account login.

poa88 Privacy Policy For Your Account

Ask About Privacy Beside Your Account

Six Ways We Keep Policy Practical

Collection at entry

Device signals

Cookie choices

Payment matching

Retention approach

Change requests

Privacy Policy Questions Before Access

01 What does the poa88 Privacy Policy cover?

02 Why does Privacy Policy mention phone verification?

03 Does poa88 store DANA or QRIS wallet PINs?

04 What payment records can the Privacy Policy cover?

05 Can I request a copy of my poa88 data?

06 How do I correct details covered by this Privacy Policy?

07 How can I ask about cookies on my device?

Related Pages