Reference

Privacy Policy For Your petimas88 Account

The petimas88 Privacy Policy explains how we collect, use, protect and remove information connected with your account in Indonesia.

Clear data purposesWallet record controlsAccount access requestsCookie choices
petimas88 Privacy Policy For Your petimas88 Account
CONTACT PATHS

Get Privacy Policy Help Through Account Support

A clear contact route helps when you need to ask about personal data rather than a game or cashier result.

Account contact Send a Privacy Policy question through the account support route and identify the email…
Wallet record query If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, tell us which account…
Access assistance When phone verification blocks access to your data request, contact support from the same…
DATA HANDLING

What We Protect Inside Your Privacy Policy

Privacy work is part of the account flow, not a separate promise placed beside it. We limit staff access to information needed for a stated task, record security events around account changes…

Collected account details

We handle information such as your contact details, phone verification result, login events, device path and messages sent to support. These details help us provide account access and investigate a sign-in problem without treating every device as the same.

Payment references

Our records may show a payment method, reference number, amount status and related account event for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not ask you to place a wallet password into a support message.

Cookie controls

Cookies can maintain a login session, remember a language or device preference and help us trace a broken page. You can adjust cookie settings in your browser, though blocking necessary cookies may interrupt account access or the route to the lobby.

Account security

Phone verification is used before account access and may be revisited when an account change looks unusual. Keep your phone, password and verification codes private; our support path will not require you to disclose a secret code in a message.

Retention decisions

We retain account and transaction records for as long as they support account operation, security review, dispute handling or a legal requirement where local law permits. After that period, we remove or anonymise the information according to the applicable record need.

Changes and requests

You can ask us to correct inaccurate profile information, explain a data use, provide available account details or remove information when no continuing need applies. We verify ownership first and respond through the contact route connected with your account.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions that arise before opening an account or when you need to check an existing record. We describe the practical route for account data, device access, cookies, wallet references and correction requests. If a request involves eligibility or access, the outcome depends on local law and the information we can verify.

The petimas88 Privacy Policy covers account details, phone verification, login and device events, support messages, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains our purposes, security controls, retention approach and request process.

We use phone verification to connect account access with the contact detail supplied during registration and to reduce unauthorised changes. A verification result can also be checked before we disclose private account information. Keep codes private, because support will not ask you to publish them.

Yes. Our Privacy Policy covers the payment references and account events we receive for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. The relevant wallet or bank may separately handle information under its own terms and privacy practices.

You can contact account support with the email address or phone number linked to your profile and ask what account information is available. We verify ownership before responding, and the scope or timing of a request depends on local law and any continuing security or legal need.

Send a correction request through the account contact route, identify the field that is inaccurate and provide the replacement detail. We may ask for an account check before changing it. Payment references are corrected carefully so the account history remains connected to the right transaction.

Cookies can maintain your session, remember a language or device preference and help us investigate a page problem. Your browser lets you adjust or block them. Necessary cookie changes may affect login, phone verification or the path from your account to the lobby.

Contact us through the account support route and request removal of the information you identify. We verify the request, check whether security, dispute or legal duties require retention, and remove or anonymise data when no continuing need applies where local law permits.