Reference

pobet Privacy Policy For Your Account

pobet Privacy Policy explains how we collect, use and protect the account details that let you move from phone verification to the lobby.

Account dataWallet referencesCookie choicesAccess requests
pobet pobet Privacy Policy For Your Account
CONTACT OUR TEAM

Three Ways To Ask About Privacy

A clear contact path helps you control the details attached to your account. We keep privacy questions separate from general lobby requests, so you can ask what we hold, why a payment…

Account access If phone verification blocks your account, contact our account support route and state that your request concerns Privacy Policy access. We may ask for a verification step before discussing personal data, rather than sending account details to an unverified contact.
Wallet status For a DANA, OVO, GoPay or QRIS reference that looks incorrect, use the payment-status support path and include the transaction reference, date and rail name. Do not send a wallet PIN or full banking password; we do not need either for a privacy check.
Data request To ask for a copy, correction or deletion review, write through our privacy contact route from the email or phone linked to your account. We assess identity first, explain any legal reason for keeping a record, and confirm the next step in the same conversation.
SIX DATA CHECKS

Six Privacy Controls Behind Your Login

Our privacy process follows the account journey you actually take: phone verification, device login, wallet status checks and support contact.

Collection

We collect account details when you submit them, including contact information needed for phone verification. Required fields support account access, while optional details are used only for the stated purpose. You can ask support to explain a field before deciding whether to provide it.

Device signals

Your browser and device can produce login time, operating-system and security signals. We use these details to identify unusual account activity and protect the session. Clearing cookies may remove a remembered device, so the next login can ask you to verify again.

Cookies

Cookies help keep a signed-in session connected to the correct account and remember selected settings. You can manage them in your browser, although blocking required cookies may interrupt the path from phone verification to the lobby or payment-status page.

Account safety

We do not ask for your wallet PIN, card password or full banking password when checking a privacy request. Keep your login details private, sign out on shared devices, and contact us if a login notification or account change does not match your activity.

Retention

We keep account, support and payment-reference records for the period needed to provide access, resolve disputes, meet legal duties or prevent repeated misuse. When that purpose ends, records are deleted or anonymised through our retention process, subject to local requirements.

Changes

You can request correction of an incorrect phone detail, contact record or account preference through the privacy contact route. We compare the request with your verified account information, record the decision, and tell you if a lawful reason means part of the record must remain.

Privacy Policy Answers For Indonesian Accounts

These answers focus on the questions you may have before opening an account or submitting a wallet-status request. We explain what the pobet Privacy Policy covers, how identity checks work, and which details you should never share. If your situation is unusual, use the privacy contact route so we can assess the record rather than guessing from a general answer.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains use, retention, correction and deletion requests where local law permits.

We use your phone number to create and verify account access, help distinguish your account from another record, and respond to account requests. If the number is wrong, contact us through the privacy route after verification; do not send a wallet PIN or banking password.

No. A payment reference can show that a DANA, OVO, GoPay or QRIS status was submitted, but we do not need your wallet PIN or full banking password for a privacy request. Send only the reference, date and payment rail when support asks.

Use the privacy contact route from the email or phone linked to your account and ask for a data copy. We first confirm that you control the account, then identify the records covered, explain any lawful exclusions and provide the next step.

Yes. Tell us which phone detail, contact record or account preference is incorrect and provide the account verification requested by support. We check the source record, make an appropriate correction where possible, and explain any reason a historical entry must stay unchanged.

We retain records for account access, payment-status checks, support history, dispute handling, security work or legal duties. The period depends on the record and applicable requirements. After the purpose ends, we delete or anonymise it through our retention process where permitted.

You can submit a deletion request through the privacy contact route. We verify your identity, review which records can be removed, and explain any data that must remain for legal, dispute or security reasons. Eligibility for account actions depends on local law.