Reference

pstbet Privacy Policy For Your Account

Our Privacy Policy tells you what account, device and wallet details we use when you open pstbet access in Indonesia.

Account dataWallet recordsPolicy requests
pstbet pstbet Privacy Policy For Your Account
HELP WITH DATA

Privacy Policy Support Near Your Account

A clear support route helps when you want to ask about the Privacy Policy or the data linked to your account. Use the account help path beside the cashier area and include the phone number on your profile, the relevant payment reference or the exact request you want us to check. We use those details to locate the right record without asking you to send a password. Requests concerning access or eligibility remain where local law permits.

Team online

Account data request

Ask us which account details we hold, such as your phone verification state, login records or wallet references. Include the account phone number so we can check identity before discussing personal data through the support path.

Wallet record query

For a DANA, OVO, GoPay or QRIS question, send the payment reference and approximate time shown in your cashier record. We can trace the status without requesting your wallet password or a full banking credential.

Policy clarification

If a Privacy Policy paragraph is unclear, quote the wording and tell us what you need explained. Our account help route can direct the question to the team handling privacy, access and account-security requests.

DATA HANDLING

What We Do With Your Privacy Choices

Privacy work is tied to practical account steps rather than broad claims. We separate login checks from payment references, record the device signals used to protect access and keep policy requests attached…

Account details

We use your phone number and verification result to identify the account during access checks. Profile details are connected to the account record, while your password should remain private and must not be sent to support.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile cashier activity. We use the reference needed for status checks rather than asking for your wallet password or complete bank login.

Device security

Browser, device and connection signals can help us spot an unfamiliar login or investigate an account-access issue. If a check interrupts access, contact support with your account phone number so we can compare the session details.

Cookie controls

Essential cookies can keep your session and account path working, while other cookies may remember settings. Your browser controls cookie removal and blocking; clearing them can sign you out or require phone verification again.

Retention approach

We retain account, payment and support records only for the operational, security or legal period that applies to the relevant record. When a retention period ends, records are removed or handled in a form that no longer identifies you.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used. Send the request through account support, identify the relevant field or record, and complete any identity check needed before changes are made.

Privacy Policy Answers For pstbet

These Privacy Policy answers address the account questions you are most likely to have before opening pstbet access. They cover the details used for login, payment matching, cookies, corrections and deletion requests. Where a request involves legal or regional eligibility, the outcome depends on local law and the records needed to protect the account.

The pstbet Privacy Policy covers details you provide for an account, records created during login and lobby use, payment references, device signals, cookies and support messages. It explains why we use each category, how we protect it and how you can ask about the record.

We may use your phone number, verification status, session details and security signals from your browser or device. These details help us connect you to the correct account and investigate unusual access. We do not need your wallet password for an ordinary account check.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a cashier event, check its status and answer a receipt question without requesting full wallet credentials.

Contact the account help route with the phone number on your profile and describe the field that needs correction. We may ask for an identity check before changing it. A correction request is handled where local law permits and subject to records we must retain.

Cookies can keep your session active and remember selected settings on your phone or computer. Your browser lets you remove or block them. Essential cookies may be needed for account access, and clearing them can sign you out or trigger phone verification again.

You can send a deletion request through account support and identify the account phone number. We assess the request under the Privacy Policy and applicable law. Some account, payment or security records may need to remain for the period required by local law.

Payment processing can require the relevant transaction details for DANA, OVO, GoPay, QRIS, bank transfer or virtual account handling. We share only what is needed for that payment path, account security or a legal requirement, subject to where local law permits.