Reference

Privacy Policy For Your primabet Account

primabet Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account clarityWallet data careCookie choicesPhone verification
Browse Our Lobby Read FAQ
primabet Privacy Policy For Your primabet Account
CONTACT ROUTES

Get Privacy Help From Your Account

A clear contact path helps you ask about personal data without searching through unrelated pages. We handle Privacy Policy questions through the support route displayed after you sign in, where you can identify the account, describe the data request and attach a payment receipt when the question concerns DANA, OVO, GoPay or QRIS. If you cannot sign in, use the contact option shown on the access screen and include the account phone number without sending a password.

Team online

Account contact

Use the support contact shown inside your signed-in account to ask for a copy, correction or explanation of personal data. We use the account phone verification step to check that the request comes from the person connected with the record.

Access issue

If login is blocked, tell us which device path you used and whether the problem appeared before or after phone verification. We can then separate an account-access concern from a Privacy Policy request without asking you to disclose your password.

Wallet enquiry

For a privacy question linked to DANA, OVO, GoPay or QRIS, include the transaction reference and date shown in your account. Do not send a wallet PIN or full banking password; our team only needs the reference to locate the relevant record.

DATA PRACTICES

How primabet Applies This Policy

We apply this Privacy Policy at the points where account data is created or used, rather than treating privacy as a separate statement.

Account records

When you open an account, we collect the contact details needed for account creation and phone verification. We use those records to associate sign-ins, requests and payment references with one account, reducing the chance that a receipt or privacy response is sent to the wrong person.

Device signals

A mobile browser and a desktop browser can create different device and session signals. We use those technical details to protect sign-in activity and investigate unusual access. They do not replace the account identity check required before we discuss private account records.

Cookie choices

Cookies can remember sign-in preferences, language settings and page selections so you do not repeat the same step. Your browser controls can remove or restrict them, although some account functions may then require another sign-in or may not retain your selected setting.

Payment references

We record the reference, method and status needed to match a DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction. We do not ask you to place a wallet PIN or banking password in a support message about Privacy Policy.

Retention periods

We retain account, security and transaction records only for the period needed for the stated service purpose, dispute handling and legal duties. When a record no longer has a required purpose, our handling process moves it toward removal or secure restriction.

Change requests

You can ask us to correct, access or remove eligible personal data through the contact route shown in your account. We confirm your identity first, explain any lawful reason a record must stay, and tell you what action was taken on the request.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account and device questions you are most likely to have before opening an account with primabet. They cover payment references, cookies, phone verification, access requests and deletion requests in plain English. If your situation is not covered, the signed-in support route remains the right place to ask for a specific account response.

The primabet Privacy Policy covers contact details, phone verification, sign-in records, device signals, cookie choices and payment references. We use them to create and secure your account, match transaction status and answer data requests. We do not need your wallet PIN or banking password for these purposes.

Phone verification helps us confirm account ownership before access or a privacy request is handled. It also helps separate your account from another person using the same device. If you ask about a record, we may use the verified phone path to confirm your identity first.

We keep the payment method, transaction reference and status needed to match activity to your account. For DANA, OVO, GoPay and QRIS questions, send the reference shown in your account rather than a PIN. The Privacy Policy does not require you to disclose secret wallet credentials.

Yes. The Privacy Policy includes technical signals from the browser or device used for sign-in. A phone and desktop can create separate session records, which help us check unusual access. Those signals support security checks but do not replace your account and phone verification details.

You can request a correction through the support contact shown after signing in. Tell us which record is wrong and provide the corrected detail. We confirm the account first, review the request, and explain the outcome or any reason a particular record cannot be changed.

You may ask us to remove eligible personal data through the account support route. We first verify your identity and check whether the record is still needed for account security, dispute handling or legal duties. If it must remain, we explain the reason and restrict its use where appropriate.

Use the contact option shown on the access screen and describe the Privacy Policy request without sending a password. Include the account phone number and, for a wallet matter, the transaction reference. We use those details to locate the request while protecting the account from unauthorised disclosure.

Related Pages

primabet Indonesia Account information About Us FAQ Liga 2 Mix Parlay