Reference

Privacy Policy for Your pt 89 Account

Our Privacy Policy explains what we collect when you open a pt 89 account, sign in from a phone or desktop, use DANA, OVO, GoPay or QRIS, and…

Account dataWallet activityCookie choicesPolicy requests
pt 89 Privacy Policy for Your pt 89 Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A direct contact route helps you ask about your Privacy Policy rights without guessing which team handles the request.

Account contact Send a Privacy Policy question through the account support path when you need to…
Wallet status If a DANA, OVO, GoPay or QRIS reference appears in your account, include the…
Access help When a phone or desktop session cannot open the policy page, contact support from…
DATA PRACTICE

What We Do With Your Account Data

We keep our Privacy Policy practical: each data category has a service reason and an access boundary.

Phone verification

Before account access, we use the phone detail you provide to complete the verification step and connect the session to the right account. If that detail is wrong, ask support to explain the correction process rather than opening a second account.

Session protection

A sign-in from a new phone, desktop or browser can create device and login records. We use those signals to investigate unusual account access and help you identify a session you do not recognise, without asking for your private wallet credentials.

Cookie controls

Cookies can keep your policy page, login path and account preferences working across a session. Your browser settings can restrict them, although some account or policy functions may then require another sign-in or may not display the same way.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be retained with the related account event. We use the reference to answer status questions and reconcile the record, not to request your wallet PIN.

Retention checks

We review whether account, device, cookie and payment records remain needed for service delivery, support questions or required recordkeeping. When a record no longer has a purpose, our process addresses it according to the applicable retention requirement.

Change requests

You can contact us to request access to your stored details, correction of inaccurate account data or clarification about a processing purpose. We may verify your identity through the account phone path before discussing private records or applying a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the searches we hear most often from people opening or using an account in Indonesia. They cover the data connected with sign-in, local wallets, cookies, device access and requests sent to support. If your situation is not listed, use the account contact path and describe the exact record or account step you want us to check. Access and eligibility remain where local law permits.

It covers data linked to account opening, phone verification, sign-in, device sessions, cookies, wallet references and support messages. The policy explains why we use each category, who may handle it for service operations, how retention is assessed and how you can ask about records connected with your account.

We may collect the contact details you enter, phone verification records, login events, device signals, cookie preferences, payment references and support messages. The exact record depends on the account step you take, such as signing in, checking QRIS status or asking about a DANA receipt.

You can contact support through the account path and ask what personal data is linked to your account. Include your account phone detail and the category you want checked. We may verify your identity first, then explain the available access process and any applicable limits.

Send a correction request through account support and identify the inaccurate detail, such as a phone record or contact field. We may ask for verification before changing it. Do not send a password, wallet PIN or full payment credentials in your message.

Yes. The Privacy Policy covers payment references and related status records created when you use DANA, OVO, GoPay or QRIS through the account path. We may use a receipt reference and date to locate an event, while wallet passwords and PINs should remain private.

Cookies can remember session settings, keep the policy page working and support the path from sign-in to account areas. You can restrict cookies in your browser. That choice may require another sign-in or affect how some account and policy functions appear.

We retain account, device, cookie, payment and support records while they have a service, security, request-handling or required recordkeeping purpose. We review whether records are still needed and address them through the applicable retention process when that purpose ends.