Reference

Privacy Policy for Your polabet Account

Our Privacy Policy explains how polabet handles the details you provide when opening an account, verifying your phone, checking wallet status or entering the lobby.

Clear data purposesWallet-aware handlingAccess request pathIndonesia policy scope
polabet Privacy Policy for Your polabet Account
REQUEST SUPPORT

Get Help With Privacy Policy Requests

A clear support route helps when you need to ask what data we hold, correct an account detail or question a wallet record. Start from the account support path and include the phone number linked to your account, the relevant date and the type of request. We may ask for an account step or verification detail before discussing private records. This protects your account while giving our team enough context to locate a DANA, OVO, GoPay, QRIS, virtual account or bank-transfer reference.

Team online

Account privacy request

Use the support path connected to your account to ask for a copy of personal data, a correction or clarification about how a record is used. Include your registered phone number and a short description so we can separate your request from a general login question.

Wallet record question

When your question concerns DANA, OVO, GoPay or QRIS, send the transaction reference and date rather than a wallet password or secret code. We use the reference to locate the status record and avoid requesting details that are not needed for the Privacy Policy request.

Account access concern

If you suspect another device has reached your account, tell us through the support route and complete the requested phone verification step. We can review access records, explain the security action and help you understand which information was used during the check.

DATA HANDLING

See How polabet Handles Your Details

We keep this policy practical: account data supports login, phone verification, transaction matching and security checks, while usage records help us diagnose access problems.

Data collected

We may receive your phone number, account details, verification result, device type, browser signals, login times, support messages and transaction references. We do not need your DANA, OVO, GoPay or QRIS password to match a payment record or explain its status.

Why we use it

The same data can serve a defined account purpose: phone details support verification, device signals help detect unusual access, and transaction references help match a QRIS, wallet, bank-transfer or virtual account event to your account.

Cookies and devices

Cookies may keep your login session available or help us understand a failed sign-in on mobile or desktop. Clearing browser data can remove session markers, so you may need to complete the account access step again before reaching the lobby.

Account security

We use phone verification and access checks to reduce the chance of an unauthorised person entering your account. If a device or sign-in pattern needs review, we may pause the request until the account holder completes the matching verification step.

Retention choices

We retain account, support and transaction records only for the period needed for account operation, security checks, disputes or legal duties. When a record is no longer needed for those purposes, our handling process removes it or separates it from direct account identification where practical.

Changes and contact

You can request access, correction or clarification through the account support route. State the Privacy Policy request clearly, identify the relevant record and use your registered phone number so we can verify the request before sharing private account details.

Find Privacy Policy Answers Quickly

These Privacy Policy answers focus on the questions you may have before opening an account or checking an existing record. We explain the practical path for Indonesian account access, device sessions, wallet references and data requests. If your situation is not covered, contact support from the account path and describe the specific record or access event you want us to examine.

It covers account details, phone verification, device and login records, cookies, support messages and payment references linked to your account. It also explains why we use those details, how we protect access, how retention works and how you can request a correction or data copy.

We use the transaction reference and status needed to match an account event. DANA, OVO, GoPay and QRIS records can help us investigate a pending or failed step, but we do not need your wallet password. Bank transfer and virtual account references are handled for the same limited purpose.

Yes, where local law permits. Send a request through the account support route using your registered phone number and explain that you want access to your personal data. We may complete an identity check before providing records so private information is not disclosed to another person.

Ask support to correct the specific detail and include the reason it is inaccurate. A phone verification step may be required before we change account information. For a transaction reference, provide the date, rail and reference rather than sending a wallet password or security code.

Yes. Cookies and device markers can keep a session active, remember limited access settings or help identify repeated sign-in attempts. If you clear browser storage on an Android or iPhone browser, the next account visit may require phone verification again before the lobby opens.

We retain information for the time needed to operate the account, resolve support or payment questions, protect access, handle disputes or meet applicable legal duties. The period can differ by record type. When the purpose ends, we remove or separate the record where practical.

You can submit a deletion request through the account support path. We assess which records are eligible and whether a limited record must remain for security, dispute handling or legal duties. We will explain the outcome and any reason a specific record cannot be removed.