Reference

Privacy Policy for Your pisau4d Account

Our Privacy Policy explains how pisau4d handles the account details you submit before you enter titles such as Live Blackjack Diamond or Badminton Sudirman Cup Bet.

Clear data purposesWallet record handlingAccount access requests
pisau4d Privacy Policy for Your pisau4d Account
HELP WITH DATA

Get Privacy Help Near Your Account

A clear support path matters when your privacy question is tied to a real account event.

Account access If you cannot reach your account after phone verification, use the account help path and describe the sign-in device. We check the access event and may ask for details already connected to your profile before discussing private account data.
Wallet records For a DANA, OVO, GoPay or QRIS record, contact us through the cashier-related help path and include the transaction reference shown to you. We use that reference to separate a payment status question from a wider data request.
Privacy requests To ask for a copy, correction or eligible removal of your data, state the request plainly through account support. We verify the requester first, confirm what can be changed, and explain any record that must remain for legal or security reasons.
DATA HANDLING

Keep Your Privacy Choices Understandable

We keep this policy practical by connecting each data use to an account action you recognise.

Login protection

Phone verification is used before account access so we can distinguish your sign-in from an unfamiliar attempt. Device and session signals may be checked for this purpose, while the support path helps you address an access issue without exposing your account to another person.

Cookie choices

Cookies and similar storage can remember your session, selected language and security state on mobile or desktop. Clearing them may sign you out or require phone verification again. Our policy explains this effect so you can make a clear browser choice.

Payment references

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer entry can create a reference in your account history. We use that reference to match status and receipts; we do not need your wallet password to answer a payment question.

Retention decisions

We retain account, security and transaction records only for the period needed for stated operations, dispute handling, fraud checks or legal duties. When a record no longer has a valid purpose, our handling process moves it toward deletion or de-identification.

Correction requests

If your phone number, contact detail or account record is inaccurate, ask us to correct it through the verified support route. We compare the request with your account details first, then confirm the amended field or explain why a record cannot be changed.

Policy contact

Privacy questions belong with our account support team, especially when they involve a sign-in, wallet status or device session. Include the relevant account reference rather than sending passwords or full payment credentials, and we will keep the request focused.

Find Answers About Privacy Policy

These Privacy Policy answers cover the questions we expect you to ask before opening an account or requesting a data change. They explain the practical link between your account, device session, local wallet records and our support route. If your situation is different, contact us from the verified account path and mention the exact record or request you want us to check.

The pisau4d Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, virtual account or bank transfer. It also explains retention, security checks and ways to request access or correction.

We use phone verification to confirm that the person requesting account access matches the account record. It can also help us investigate an unfamiliar sign-in. If verification fails, use the account help route and do not send your password or wallet PIN.

Yes. Privacy Policy coverage includes payment references connected with DANA and QRIS, as well as OVO, GoPay, virtual account and bank transfer records. We use these references to check status or receipts, not to request or store your wallet password.

You can ask for access to eligible account data through the verified support path. Tell us which record you mean, such as a login event or wallet reference. We confirm your identity first and explain any part that cannot be released for security or legal reasons.

Send a correction request through account support after signing in where possible. Identify the field that needs attention, such as a phone or contact detail. We compare the request with your account record, make an eligible change, and confirm the result or reason for refusal.

We keep account, security and transaction records for as long as needed for the stated service purpose, dispute handling, security checks or legal duties. Retention can differ by record type. When there is no valid reason to keep data, we move it toward deletion or de-identification.

The core handling described here applies to your account, but access and eligibility depends on local law. A request from Makassar, Denpasar or another Indonesian location may require a local restriction check. We explain any limitation through the verified support route.