Reference

Privacy Policy for prima89 Accounts

Our Privacy Policy explains how prima89 handles the details you provide when opening an account, verifying your phone, using DANA or QRIS, and entering the lobby from a…

Account clarityWallet dataCookie choicesPhone verification
prima89 Privacy Policy for prima89 Accounts
CONTACT ROUTES

Ask About Your Privacy Policy

A clear contact path matters when you need a copy, correction or explanation of your personal data. Start from the signed-in account support route and include the phone number linked to your account, the request you are making and any relevant receipt reference. We use those account details to locate the correct record without asking you to send a password or full wallet credentials. If access is unavailable, use the support entry beside the cashier path and state that your request concerns the Privacy Policy.

Team online

Account data request

Ask us to confirm the account details connected with your phone verification step. We may check the signed-in account path before responding, so a request about your own data is not mixed with another account.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment rail and receipt reference. Please hide passwords and full wallet credentials; we only need enough detail to locate the relevant status.

Policy change request

If a name, phone detail or other account field is incorrect, tell us what should change and why. We can ask for an account check through the support route before applying an amendment.

DATA PRACTICES

How prima89 Handles Your Data

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We handle the details needed for your account path, including your phone verification record and sign-in identifiers.

Payment references

A DANA, OVO, GoPay or QRIS receipt reference can help us trace a wallet status question.

Device and cookies

We may use device and browser signals to keep a signed-in session working from the mobile login path to the…

Account security

Phone verification is part of the account access check.

Retention approach

We retain account, payment and support records for the period needed for their stated purpose and any applicable local requirements.

Your requests

You can ask for access, correction or an explanation of data use through the signed-in support route.

Privacy Policy Questions for prima89

These Privacy Policy answers focus on the account actions you are most likely to check before opening access. They explain what may be connected to a phone verification step, how wallet references are handled, why cookies appear on a device and where to send a request. If your question concerns a specific account record, use the support route while signed in and mention the relevant payment rail or receipt reference.

It covers data linked to account creation, phone verification, sign-in, device use, cookies, support requests and payment references. This includes activity connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account paths where access is permitted by local law.

Phone verification helps connect account access to the correct account and supports sign-in protection. It also lets support identify your record when you request access or correction. We do not need your password for a Privacy Policy request.

Yes. The policy covers payment references used to check DANA, QRIS, OVO, GoPay, bank transfer and virtual account status. Send the payment rail and receipt reference through support, but do not send a password or full wallet credentials.

You can request access to the account data connected with your phone verification, sign-in and support history. Use the signed-in account support route, describe the categories you want, and complete any account check needed to protect your record.

Send a correction request through the account support route and identify the field that is wrong, such as a phone detail. We may verify account ownership before changing it, and we will explain if a record must be retained.

Essential cookies can keep your session connected from mobile login to the lobby and help remember necessary access settings. Check the cookie controls shown on the site for available choices; device and browser signals may also support session security.

You may ask support whether removal is available for a particular data category. Send the request through your signed-in account path, and we will explain what can be removed, what must be retained, and why the distinction applies.