Reference

petir388slot Privacy Policy For Your Account

Our Privacy Policy explains how petir388slot handles the account details you provide before you reach Auto Roulette, Fish Hunter or another lobby area.

Account dataWallet recordsCookie choicesContact rights
petir388slot petir388slot Privacy Policy For Your Account
CONTACT ROUTES

Get Help With A Privacy Request

A clear contact path helps you control your personal data without explaining your concern twice. Use the support route shown inside your account when you need a copy of your stored details, a correction to your phone number or clarification about a DANA or QRIS transaction record. Include the email or phone detail linked to your account so we can match the request safely.

Team online

Account privacy request

Send your request through the account support path and state whether you want access, correction or removal of a particular detail. We may ask for a matching account step before releasing personal data to you.

Wallet record question

For DANA, OVO, GoPay or QRIS references, include the visible receipt number and date rather than sharing a password. We use those details to locate the relevant record without asking for unnecessary wallet credentials.

Sign-in concern

If a phone verification prompt or mobile sign-in looks unfamiliar, contact us through the account support route before changing payment details. We can check the session context and help protect the correct account.

HANDLING DETAILS

What We Do With Your Personal Data

We keep privacy decisions close to the actions that create data: opening an account, confirming a phone, choosing a cookie setting and checking a wallet record.

Account collection

We collect details such as your phone contact and sign-in identifiers when you open an account or complete phone verification. These details let us associate a session with your account and respond to a privacy request from the correct person.

Cookie controls

Cookies and similar browser signals can keep a session active, remember a selected setting and help identify repeated sign-in errors. You can manage browser permissions, though restricting them may affect account continuity on mobile or desktop.

Device signals

We may receive device type, browser version, language and basic connection signals when you open the lobby. These details help us investigate an unusual session or a failed phone-verification step without reading unrelated files on your device.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may create a reference, amount and status record. We use that limited transaction context to match your account activity and answer a receipt or status question.

Retention choices

We keep personal records for as long as they support account administration, dispute handling, security checks or a legal requirement. When a record no longer serves one of those purposes, we remove it or separate it from direct account identifiers.

Change requests

You can ask us to correct an inaccurate phone detail, explain a stored record or request deletion where applicable. We may need account confirmation first, and access remains subject to local law and where local law permits.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening or continuing an account. They explain what we collect, why a device may be recognised, how transaction references are handled and where to send a request. If your situation is unusual, use the support path connected to your account.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, account-security checks and how you can request access or correction.

Phone verification helps us connect account access with the contact detail you provided and reduces confusion when a session or wallet-status request needs checking. We use the verification result for account administration and security, not to read unrelated content from your phone.

Yes. The policy covers the transaction references, dates and status details associated with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use this information to match a receipt or status request with your account, while avoiding unnecessary wallet credentials.

You can send a correction request through the support route shown inside your account. Tell us which phone, contact or account detail is inaccurate and provide enough matching account context for verification. We assess the request under this Privacy Policy and where local law permits.

We retain data while it is needed for account administration, support, security checks, disputes or a legal requirement. After that need ends, we remove the record or separate it from direct identifiers when practical. A specific retention request can be sent through account support.

Yes. Ask through the account support path if you want clarification about cookies or browser signals used during mobile sign-in. You can also change cookie permissions in your browser settings, although blocking them may interrupt session continuity or require another phone-verification step.

Use the support contact displayed inside your account and label the request as a Privacy Policy concern. Include your linked phone detail, the relevant date and a short description, but do not send passwords or full wallet credentials. We use the supplied context to route your request safely.