Reference

Privacy Policy for Your poa88 Account

Our Privacy Policy shows what data we collect when you open an account, enter the lobby, use DANA, OVO, GoPay or QRIS, and contact support.

Account data useDANA and QRIS contextCookie choicesSupport request records
poa88 Privacy Policy for Your poa88 Account
CONTACT ROUTES

Three Privacy Contact Paths

Privacy questions need a clear route, not a maze. We give you three contact paths so you can ask about stored details, payment records, cookie choices, or account changes without repeating the same issue across channels. Our team checks privacy requests every day from 09:00 to 23:00 WIB, then routes account-specific questions to verification before any change is made.

Team online

Live chat privacy desk

Use live chat from your account menu when you need quick help with profile data, device history or cookie settings. We ask for account checks first, then log the request under your support record.

Email data requests

Send longer privacy questions by email when you need a copy of account details, a correction, or clarification about payment records. Include your registered phone number, but never send wallet PINs or one-time codes.

Wallet issue routing

If your privacy question involves DANA, OVO, GoPay or QRIS, support links the case to the wallet request time and transaction reference. That helps us check data use without exposing unrelated account activity.

ACCOUNT CARE

Six Controls Around Your Data

We handle privacy as part of daily account operations, not as a hidden legal page.

Account collection

We collect registration details so your account can be opened, checked and supported. That includes contact fields, login credentials, device signals and selected payment rails, all tied to the account flow you start.

Payment context

DANA, OVO, GoPay and QRIS records are used to match wallet activity with your account. We keep transaction references, timing and status details so support can trace requests without asking for private wallet access.

Cookie handling

Cookies help keep you signed in, remember language and device preferences, and flag unusual access. You can clear them through your browser settings, but some account checks may run again after cookies are removed.

Security checks

Login activity, IP address, device type and failed password attempts help us spot account misuse. When a pattern looks unusual, we may ask for extra verification before changing details or processing a sensitive request.

Retention practice

We keep account and support records only as long as needed for operations, dispute handling, security checks and legal duties. If a record is no longer needed, we aim to delete or separate it from your profile.

Change requests

You can ask us to correct contact details, check stored data, or close an account record where local law permits. We verify ownership first so another person cannot change your profile through support.

Privacy Questions Before You Join

Before you open an account, you may want to know exactly what happens to your data. These answers focus on the Privacy Policy only: what we collect, why we use it, how payment records are handled, and how you can reach us if something needs attention.

We collect the details needed to create and manage your account, such as name, phone number, email, login credentials, device signals and account activity. Payment rail choices are recorded only as needed for wallet operations.

We record payment rail context so deposits, withdrawals and support checks can be matched to your account. This includes timing, status and reference details, not your private wallet PINs or one-time codes.

Yes, cookies support sign-in, device recognition, language preference and security checks. If you clear cookies, the site may ask you to log in again or repeat checks before sensitive account actions.

Yes, you can ask support to correct contact details or check stored account data where local law permits. We verify account ownership first, then record the request so the change has a clear audit trail.

Only the teams that need the case can access privacy support messages. For example, a wallet-related privacy question may be seen by payment operations, while login concerns may be routed to security staff.

We keep records for operational needs, dispute handling, security checks and legal duties. When data is no longer needed for those reasons, we aim to delete it or separate it from your account profile.

Use live chat inside your account for quick privacy questions, or email support for longer data requests. Our team checks privacy cases from 09:00 to 23:00 WIB and may ask for verification.