Reference

Open the pinus55 Privacy Policy

pinus55 Privacy Policy gives you a clear view of how we handle account details, mobile-browser activity and payment references linked to DANA, OVO, GoPay and QRIS.

Account dataCookie choicesWallet referencesContact route
Explore Our Lobby Read FAQ
pinus55 Open the pinus55 Privacy Policy
CONTACT THE TEAM

Reach support about Privacy Policy questions

A clear contact path helps when you want to ask about a Privacy Policy point, correct an account detail or check a wallet reference. Start from the support route connected to your signed-in account, and include the phone number on the account plus the relevant date. We may ask for enough detail to locate the record, but we will not ask for your wallet password or full security code. The same route can help when a QRIS receipt or transfer status needs to be matched.

Team online

Policy support panel

Use the account support panel for questions about collection, cookies, retention or a Privacy Policy clause. Include the subject of your request and the phone number tied to the account so we can locate the right record without asking for your wallet password.

Cashier status check

When a DANA, OVO, GoPay or QRIS reference does not match your account history, send the receipt reference through the available support path. We use that reference to check the payment record and explain what data was used for the status check.

Account data request

For a correction, access request or removal question, state exactly which account detail you want us to examine. We may verify ownership through the phone verification step before changing or disclosing account-linked records.

HANDLING YOUR RECORDS

Explore pinus55 data controls

Our Privacy Policy is supported by practical controls rather than a vague promise. We separate account details from the payment references needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer and virtual…

Account collection

We collect details needed to create and protect your account, including your phone number, verification result and sign-in events. Optional details are treated separately from the core fields required to connect your account with a payment status or support request.

Cookie choices

Cookies and similar browser storage can keep a session active, remember a selected language or help us understand a sign-in error. You can clear site data in your browser settings; doing so may require phone verification again before account access.

Mobile security

Our mobile path uses the browser session on your device rather than requiring a separate app download. Sign out after using a shared phone, avoid saving passwords there and contact support if a login event or device signal looks unfamiliar.

Payment matching

A payment reference helps us connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event with the correct account. We use the reference for reconciliation and status checks, not to request your wallet password or private wallet code.

Retention timing

We keep account, security and transaction records only as long as needed for the purpose described in this Privacy Policy or a legal requirement. When a record is no longer needed, our handling process moves it toward deletion or restricted access.

Change requests

You can ask us to correct account details, explain a data use or consider a deletion request through the support route. We verify the request against the account before making a change, and we explain any record that must remain for a valid legal reason.

Check Privacy Policy answers before opening

These Privacy Policy answers cover the points you are most likely to check before creating an account from Indonesia. We keep the wording practical: what data is collected, how wallet references are used, what happens on a mobile browser and where to send a request. If your situation is not listed, use the account support route and describe the exact record or section you want us to address.

It covers account creation, phone verification, sign-in events, device and cookie signals, support conversations, payment references and retention. It also explains how to request access, correction or deletion, subject to verification and any record we must keep for a valid legal reason.

Yes. The Privacy Policy explains that DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be used to match a payment event with your account. We use the reference for status and reconciliation checks, not your wallet password.

We may collect your phone number, verification result, account activity, device signals and payment references connected to a transaction. We use these details to provide account access, investigate unusual events, answer support requests and maintain records for the stated purpose.

You can contact us through the account support route and specify whether you want access to a record or correction of an account detail. We verify ownership before responding, then explain the scope, timing and any lawful reason a record cannot be removed.

The mobile browser may store a session token or cookie to keep your account path active between login and the lobby. Clear browser storage or sign out on a shared device. You may need phone verification again when the stored session is removed.

We retain account, security and transaction records for as long as they serve the purpose described in the Privacy Policy or a valid legal requirement. Retention can differ by record type. When the period ends, we delete the record or restrict access.

Account access and eligibility depends on local law. The Privacy Policy describes our data handling for supported Indonesian access, while your location and applicable rules determine whether you may open or use an account. Contact support if you need a policy clarification before proceeding.

Related Pages

pinus55 Indonesia FAQ Basketball NBA Bet Live Blackjack Gold pinus55 Casino