Reference

Privacy Policy for Your polabet Account

polabet Privacy Policy explains how we collect, use and protect the account details you provide before accessing casino tables, slots or sports markets in Indonesia.

Account dataWallet recordsDevice accessYour privacy choices
polabet Privacy Policy for Your polabet Account
PRIVACY CONTACT ROUTE

Get Help With a Privacy Policy Request

A clear contact path helps when you want to ask about data held on your account or a wallet reference connected to a payment. Use the support contact available through your signed-in account and include the phone number linked to access, the relevant date and the payment rail involved. We use those details to locate the correct record without asking you to send a password or full wallet credentials. If your account access is stalled, explain that your request concerns the Privacy Policy so our team can route it correctly.

Team online

Account contact

Send a Privacy Policy question through the support route shown after you sign in. Include your account phone number and a short description of the request; do not send your password, wallet PIN or complete bank credentials.

Wallet record

For a DANA, OVO, GoPay or QRIS query, add the transaction date, amount display and reference visible in your account. We can compare that reference with the stored payment event while keeping your private wallet login details out of the request.

Access concern

If a phone verification step prevents you from reaching the account area, tell us which step stopped and which device you used. We may ask for account-matching details, but we will not ask for a password or a wallet security code.

DATA HANDLING DETAILS

What We Do With Account Data

Privacy Policy choices are easier when each data use has a practical reason. We use account and verification details to provide access, payment records to trace wallet activity, and device signals to…

Account security

Your phone verification step helps us connect an account request with the right account holder. We may record sign-in time, browser or device details and security events so an unusual access attempt can be checked before account data or wallet activity is disclosed.

Cookies and sessions

Cookies can support the sign-in session, language setting and page movement between the lobby and account area. On a mobile browser, clearing site data may sign you out and remove those settings; you can then sign in again through the normal account path.

Payment matching

A QRIS or wallet reference lets us connect a payment event with your account record. For bank transfer or virtual account activity involving BCA, BRI, Mandiri or BNI, we use the reference and status needed to reconcile the request, not unrelated banking details.

Device access

We may receive technical details such as device type, browser version and network address when you open the site. These details help diagnose a failed session or suspicious sign-in on mobile and desktop without giving us access to files, contacts or other device content.

Retention period

We keep account, security and payment records for as long as needed for account operation, payment tracing, dispute handling and legal duties that apply to the service. When a record no longer serves one of those purposes, our process is to delete it or limit access.

Change request

To request a correction, copy or restriction, contact us through the signed-in support route and identify the account phone number plus the data category involved. We may verify ownership first, then explain the available action and any reason a record must remain stored.

Privacy Policy Answers for polabet

These Privacy Policy answers address the account and payment questions we hear most often from people preparing to use polabet in Indonesia. Each answer points you toward a practical account step, from checking a QRIS reference to contacting support about stored data. If your situation involves access or eligibility, it depends on local law, and our support route can explain which request path applies.

The polabet Privacy Policy covers account details, phone verification, device and session data, cookies, payment references and support messages. It explains why we use each category, how we protect it, how long records may remain and how you can ask about, correct or restrict eligible data.

We use your phone number to create and verify the account path before access is provided. It also helps us match a support request to the correct record. We do not need your wallet PIN or password when you ask about Privacy Policy data.

Yes. The Privacy Policy includes payment references connected with DANA, OVO, GoPay and QRIS activity. We use a reference, date and status to trace an account event. Wallet login details and security codes should stay with you and should not be sent to support.

When you open the site, we may record device type, browser version, network address, sign-in time and security events. These details help us diagnose a mobile session or check unusual access. We do not use this process to read your files, contacts or unrelated device content.

Use the support contact shown in your signed-in account and state whether you want a copy, correction or restriction. Include your account phone number and the relevant data category. We may verify account ownership before responding, and some records may need to remain stored.

We retain account, security and payment records while they are needed for access, payment tracing, dispute handling or applicable legal duties. After that need ends, our process is to delete the record or restrict access. A support contact can explain the status of a specific request.

Yes. You can read this Privacy Policy before opening an account and decide whether its data practices suit you. If you later request access, eligibility or account service in Indonesia, that availability depends on local law and the account checks required for the request.