Reference

Privacy Policy for Your poka88 Account

poka88 explains how we collect, use and protect the details connected with your account, phone verification and wallet activity.

Account dataWallet recordsCookie choicesAccess requests
poka88 Privacy Policy for Your poka88 Account
HELP WITH PRIVACY

Where Privacy Questions Reach Our Team

A clear support route helps when a privacy request and an account issue arrive together. Start from your account help path and include the phone number or account detail you used for the request, without sending a wallet password or one-time security code. If your QRIS receipt, DANA status or phone check needs matching, we use the reference already shown in your account. Our support team can explain the request path and the next verification step.

Team online

Account request

Use the account help path to ask for a copy, correction or removal of personal data. We may ask you to confirm the phone detail attached to your account before discussing records.

Wallet reference

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date shown in your account. We use that detail to locate the relevant record without asking for your wallet password.

Access concern

If a privacy request follows a failed sign-in or phone check, tell us which device path you used and what appeared on screen. We separate identity checks from the details of your request.

DATA HANDLING

Account Data Behind QRIS Access

We handle privacy requests alongside the real account steps you take, from phone verification to a wallet status check.

What we collect

We may collect account details, phone verification results, sign-in events, device information and transaction references. The purpose is to provide account access, connect a wallet status with the right account and investigate security concerns.

How we use it

We use personal data to process account actions, check identity, answer support requests and keep records accurate. DANA, OVO, GoPay and QRIS references help us trace a payment status without requesting your wallet credentials.

Cookies and devices

Cookies can remember a sign-in state, language choice or security setting on the browser you use. Device signals help us notice an unusual access pattern; clearing cookies may require you to complete phone verification again.

Account security

Phone verification is part of the account access path, and security events may be recorded when sign-in details change. Never send us a password or one-time code; our team uses account checks rather than those secrets.

How long we retain

We keep records only as long as needed for account security, payment tracing, disputes, support history or legal duties. When a record no longer serves one of those purposes, we remove it or keep it in a form that does not identify you.

Changes you can request

You can ask which personal data we hold, request a correction, question a use or ask about deletion. Send the request through account support with enough detail for us to locate your account, and we may verify your identity first.

Privacy Policy Answers for poka88

These questions focus on the privacy decisions you are most likely to make before opening or using an account. Each answer relates to our data handling, account access and local wallet records, so you can choose the right support path without guessing.

The poka88 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support requests and wallet transaction references. It explains why we use each category, how we protect access and how you can ask about, correct or remove eligible data.

Phone verification helps connect account access with the person making the request and helps us respond to security events. We record the verification result rather than asking for your phone account password. A phone check may be required again after cookies are cleared or access details change.

Yes. The Privacy Policy covers the DANA, OVO, GoPay and QRIS references that appear when you check a wallet status or match a transaction. We use the reference, status and timing needed for account support, and we do not ask for your wallet password.

Use the account support path and clearly ask for a copy of your personal data. Include the phone detail or account reference connected with your request, but do not send a password or one-time code. We may complete an identity check before releasing records.

You can request a correction or ask whether deletion is available for a particular record. We first locate the account and assess any security, dispute, payment-tracing or legal reason for retention. Where local law permits, we complete the request or explain the reason a record must remain.

Cookies can keep a browser sign-in state, language choice or security setting available during your account path. If you clear or block them, some access steps may reset and phone verification may appear again. Our Privacy Policy explains the purpose of these cookie records.

The policy describes how we handle data when you access the service from Indonesia, including mobile access from Surabaya or another city. Account eligibility and access depends on local law. If you need a local-data answer, contact support with your account reference.