Reference

poa 88 Privacy Policy for Your Account

The poa 88 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet activity through DANA, OVO, GoPay…

Clear data purposesWallet record controlsAccount access requestsCookie choices
poa 88 poa 88 Privacy Policy for Your Account
PRIVACY CONTACT

Where to Ask About Your Data

A direct privacy question should begin with the account and payment context that helps us locate the right record. If you contact us from Yogyakarta, Jakarta or elsewhere in Indonesia, include your registered phone number only through our account support route, never in a public message. We use the request details to confirm ownership before discussing account data, wallet references or a correction. Where local law permits, we explain the next step and any limits that apply to your request.

Team online

Account access

If you cannot reach your account after phone verification, use the account support route and describe the device path you followed. We may ask for limited details to confirm ownership before discussing stored profile data or changing an access record.

Wallet records

For a DANA, OVO, GoPay or QRIS privacy question, share the payment date and reference shown in your account rather than sending a wallet password. We use that reference to check the status record and explain what data remains connected.

Policy requests

To ask for a copy, correction or eligible removal of personal data, identify the account contact and state the request clearly. We verify the requester first, then confirm the action, any required clarification and the applicable local-law position.

DATA HANDLING

What We Do With Privacy Requests

Privacy controls work best when each request is tied to a specific account event. We separate account verification from payment reconciliation, limit internal access to the records needed for a task and…

Account details

We collect details needed to create and maintain your account, including contact information and the phone verification step before access. We use them to identify your account, respond to requests and keep the login path connected to the correct record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can create a reference in our records. We use that reference to match status and receipts, while your request should never include a wallet password or full authentication secret.

Cookies

Cookies can remember settings and help us understand whether a session remains active on your phone or desktop. You can manage cookies through your browser controls, although removing them may affect saved preferences or require you to verify access again.

Account security

We use phone verification, session checks and security-event records to reduce the chance of an account being accessed by someone else. If a login looks unusual, we may request an account check before changing contact details or discussing private records.

Retention

We retain different records for different operational reasons, such as account access, payment reconciliation, dispute handling and security review. When a record is no longer needed for those purposes, we assess it for deletion or continued storage under the applicable local-law position.

Changes and contact

You can ask us to correct inaccurate account data, request access to eligible records or question how a detail is used. Send a clear request through account support; we confirm ownership first and explain the outcome, timing and any restriction that depends on local law.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we expect when you are deciding whether to open an account or asking how a record is handled. We keep the examples close to the actual account path, including phone verification, mobile cookies and local payment references. If your question is not covered, contact us through the account support route with the smallest amount of personal detail needed to identify your request.

The poa 88 Privacy Policy covers account details, phone verification, device and session data, cookies, payment references, security events and support messages. It explains why we use each category, when we may retain it and how you can request access or correction where local law permits.

Phone verification connects the account to the contact detail you provide and helps us check ownership before access or a privacy response. If you ask about stored data, we may repeat that check so another person cannot obtain account or wallet records.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those references to reconcile status and receipts, not to request your wallet password. Include only the visible reference when asking for a check.

We may handle device, browser, session and security-event details linked to your account access from a phone or desktop. These details help identify unusual login activity, maintain a session and investigate an access issue. They do not replace the account verification step.

Contact our account support route and state whether you want access to an eligible record or correction of a specific detail. Include your registered contact and a precise description, but do not send passwords. We verify ownership, assess the request and reply according to local law.

You can submit a removal request through account support. We first confirm that you control the account, then check whether a record must remain for payment reconciliation, dispute handling, security or another permitted reason. We explain what can be removed and why if limits apply.

Cookies may remember a preference or help maintain your session while you move from login toward the lobby. Browser controls let you remove or restrict them, but this can clear settings or trigger another phone verification. The Privacy Policy explains the purpose of each cookie category we use.