Reference

pinus33 Privacy Policy For Your Account

Your account details, wallet records and device signals stay tied to clear purposes: opening access, checking payments and protecting your session.

Account clarityWallet recordsDevice choicesContact route
pinus33 pinus33 Privacy Policy For Your Account
HELP WITH YOUR DATA

Reach Us About Privacy Questions

A clear contact path helps when your account record, wallet reference or device history needs attention.

Account privacy request Use the account support route to ask what personal details we hold, why a…
Wallet record check If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount…
Login and device concern Tell us when a login, browser or mobile session does not look like yours.
HOW WE HANDLE RECORDS

Privacy Choices Across Your Account

Our handling approach follows the account journey rather than treating every record the same way.

Account details

We use your submitted account details to create access, complete phone verification and connect your requests to the correct record. Keep your phone number current so we can distinguish a genuine account request from an unknown attempt.

Payment references

Cashier records can include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. We use those details to match status and investigate discrepancies, while asking you to keep wallet passwords and security codes private.

Cookies and storage

Cookies and similar browser storage can remember a session choice, support security checks and help the account page load correctly. You can adjust browser controls, although removing necessary storage may sign you out or interrupt account access.

Device security

We may receive signals such as browser type, operating system, approximate network details and session timing. These signals help us review an unfamiliar login, including a mobile switch from account access to the lobby.

Retention approach

We keep each category only for the period needed for account operation, payment tracing, security checks, dispute handling or legal duties. When a record no longer serves those purposes, our handling follows the applicable retention process.

Requests and changes

You can ask for a copy, correction, explanation or deletion of eligible personal details through account support. We may verify your phone or account step first, then explain any record that must remain for security or legal reasons.

Privacy Policy Questions For pinus33

These answers address the searches we hear most often before an account is opened. They focus on the records connected to pinus33 access, local wallets, mobile sessions and support requests, so you can decide what to share and how to contact us.

It covers account details, phone verification, payment references, support messages, cookies, device signals and related lobby activity. We explain how we collect and use these records for account access, security, payment tracing and legal duties where local law permits.

We use your phone number to complete the account step, connect you with the correct record and help identify an unusual login. If you contact us about private data, phone verification may be needed before we discuss account-specific details.

Yes. A DANA or QRIS payment reference may be handled as part of your cashier record, along with OVO, GoPay, bank transfer or virtual account details. We use references to check status and do not ask for your wallet password or security code.

We may use browser type, operating system, approximate network details and session timing to support login security and detect an unfamiliar session. This applies when you move from mobile account access into areas such as Basketball Live Bet or the lobby.

You can contact us through the support route inside your account and ask for access, correction or an explanation of eligible records. We may confirm your account step first, then respond about the data we can provide or change.

Retention depends on why the record exists. We keep account, payment, security and support records for the period needed to operate access, trace a transaction, handle a dispute or meet applicable legal duties, then follow the relevant removal process.

Yes. Access and eligibility depends on local law, and some requests may be limited where a record is needed for security, payment tracing or a legal duty. We will explain the reason through the account support route when that applies.