Reference

petir33 Privacy Policy for Your Account

Your petir33 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between Baccarat, Mahjong Ways 2 and other lobby areas.

Clear data purposesWallet record contextAccount access rightsCookie choices
petir33 petir33 Privacy Policy for Your Account
HELP WITH DATA

Get Help With Privacy Questions

A privacy question should not leave you guessing about your account. Use our support route when a phone verification record looks wrong, a wallet status does not match your receipt, or you want to ask how a device event was used. Include your account identifier and the specific request, but do not send a wallet PIN or password. We can then locate the relevant record without asking for unnecessary details.

Team online

Account data request

Ask us to explain, correct or provide the personal details connected with your account. We may request a phone verification step before discussing records linked to your petir33 access.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt reference and date through support. We use those details to check the payment record without requesting your wallet PIN.

Cookie or device query

Tell us if a cookie choice, phone change or device entry needs attention. We can explain the event shown in your account history and outline the next verification step.

DATA HANDLING

What Your Privacy Settings Cover

We keep the policy practical: each record has a purpose tied to account access, payment checking, fraud prevention or service operation.

Account details

We use contact and verification details to create your account, confirm access and respond to requests. Check every field before submission so corrections can be handled against the right account.

Payment references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer references help us reconcile account activity. We use the reference and status, not your wallet PIN, for this check.

Device events

Login time, browser or device signals can help identify an unusual session. If you change phones, contact support so we can explain the recorded access event.

Cookies

Cookies can preserve sign-in state, security checks and your page choices. You can adjust cookie controls in your browser, though some account functions may then require another sign-in.

Retention

We retain records only as long as needed for the stated purpose, account security, payment reconciliation or a legal requirement. A deletion request receives an explanation where retention still applies.

Policy changes

If this Privacy Policy changes in a material way, we will place the revised wording on this page. Keep a copy of the date shown when you submit a data request.

Privacy Policy Answers for petir33

These Privacy Policy answers focus on the actions you are most likely to take: opening an account, checking a payment record, changing a device or asking for a copy of your data. They also clarify what happens when a request meets a security or legal reason for keeping a record.

It covers account details, phone verification, device events, cookies, payment references and support requests connected with your use of petir33. It also explains correction, access and deletion requests.

We use clear phone verification before account access to reduce mistaken or unauthorised requests. It helps us confirm that the person asking about account data is connected with that account.

Yes. The policy covers DANA, OVO, GoPay and QRIS references, plus virtual account and bank transfer status used to reconcile your account. We do not ask for your wallet PIN.

Contact our support route with your account identifier and request a copy or explanation of your records. We may complete an identity check before releasing details linked to your account.

Yes. Tell us which field is inaccurate and provide the corrected detail through support. We verify the request, update suitable records and explain any information that must remain unchanged.

We keep information for the period needed for its stated purpose, account security, payment reconciliation or a legal requirement. If deletion is limited, we explain the reason connected with that record.

Yes, access and eligibility depend on local law. Where local law permits, we handle requests using the account and support paths described here, with verification before personal records are disclosed.