Reference

Open petirzeus88 Privacy Policy Details

DANA, OVO, GoPay and QRIS records are explained clearly in the petirzeus88 Privacy Policy, alongside the account details needed to reach Live Baccarat, The Great Icescape and other…

Account dataWallet recordsCookie choicesPrivacy requests
petirzeus88 Open petirzeus88 Privacy Policy Details
PRIVACY SUPPORT

Find Privacy Help Near Your Account

A clear contact path matters when a record looks wrong or a wallet status needs checking.

Account help Use the account help path for access, verification or profile-data questions. We may ask you to confirm the registered phone before discussing records linked to your account.
Wallet status For DANA, OVO, GoPay or QRIS records, include the transaction reference and date in the cashier status request. We use those details to locate the relevant payment entry.
Privacy request Ask for a copy, correction or deletion assessment through the privacy contact route. We check account ownership first, then explain what can be changed under local requirements.
DATA PRACTICES

See How petirzeus88 Handles Account Data

We keep this policy practical by linking each data use to an account action you can recognise, from phone verification before access to a QRIS status check after payment.

Collected details

We may record your contact details, verification result, login events, device signals and selected lobby actions. These details help connect your account activity with the request you send us.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries can carry a reference, amount status and timestamp. We use the record to match an account action without requesting your wallet password.

Cookie settings

Cookies can retain sign-in preferences and measure page loading on mobile or desktop. You can adjust browser controls, although changing them may affect how account pages remember your choices.

Account security

Before discussing personal records, we may ask for a registered phone confirmation or another account step. Never send a wallet PIN, password or one-time code in a support message.

Retention periods

We retain records only for the period needed for account operation, payment reconciliation, security checks or legal duties. A deletion request receives a response explaining any remaining retention reason.

Change requests

You can ask us to correct inaccurate account data, access a copy or assess removal through the privacy contact route. Include your registered contact so we can verify ownership safely.

Browse Privacy Policy Answers

These answers focus on the questions you may have before opening an account or connecting an Indonesian wallet. They explain how the Privacy Policy relates to account access, payment references, device details and contact requests. If your situation is not listed, use the privacy contact route and mention the relevant account step or transaction reference.

It covers account details, verification records, login and device information, cookies, lobby activity and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps us confirm that the person asking about an account record is authorised to receive an answer. We may request this step before changing or disclosing personal details.

We do not ask you to send a wallet password, PIN or one-time code through support. The policy concerns payment references and status details needed to match an account action.

Send a privacy request through the account help route with your registered contact and a clear description of the records sought. We verify ownership before preparing a response.

Yes. Tell us which account detail is inaccurate and provide the corrected value through the privacy contact route. We assess the request and explain the next step under local law.

Retention depends on the purpose, such as account operation, payment reconciliation, security checks or legal duties. If you request deletion, we explain any record that must remain and why.

Yes. It covers information from the mobile browser or desktop path, including device type, login time, cookies and page loading signals when you access the account where local law permits.