Reference

Privacy Policy for Your petir36 Account

Our Privacy Policy explains how petir36 handles the details connected with your account, including contact data, login activity, device signals and payment records from DANA, OVO, GoPay or…

Account dataCookie choicesWallet recordsContact requests
Browse Our Lobby Read FAQ
petir36 Privacy Policy for Your petir36 Account
CONTACT ROUTES

Ask About Your Privacy Policy

A direct privacy question should reach the same support path used for account and wallet concerns, so you do not need to explain the issue twice.

Account privacy request Send your request through the account support channel and include the contact detail attached to your petir36 account. We may ask for a simple account step to confirm that the request comes from you before discussing stored data.
Wallet record question For a DANA, OVO, GoPay or QRIS record, share the date and reference shown in your receipt rather than your wallet password. We can use that reference to locate the payment entry and explain its handling under this Privacy Policy.
Correction or deletion Ask us to correct an inaccurate account detail or explain whether a record can be removed. We will assess the request against active account needs, transaction reconciliation and retention duties where local law permits.
HANDLING DETAILS

What We Do With Account Data

Our handling process follows the account journey rather than collecting unrelated details. We use contact data for account access, phone verification and replies; device signals help us recognise unusual login activity; and…

Account creation

When you open an account, we collect the details needed to create your profile and complete the phone verification step before account access. We use those details to connect your login with the correct account record, not to create an unrelated marketing profile.

Login protection

Login events can include device and session signals used to spot an unusual access pattern. If a sign-in needs checking, we may ask you to confirm an account detail. Keep your password private and contact support if a device entry looks unfamiliar.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet action with your account. Bank transfer and virtual account entries can be retained for reconciliation, receipt checks and questions about a transaction status.

Cookie choices

Cookies can remember a session, language setting or page preference on the device you use. You can manage cookies through your browser controls, although removing some of them may require another login or affect account page functions.

Retention checks

We review whether stored account, support and payment records are still needed for the purpose that brought them into our systems. A request to remove data may not erase records required for security, dispute handling or transaction reconciliation.

Your requests

You can ask what account data we hold, request a correction or ask about deletion through the support route. Include your account contact detail and the specific record, such as a phone entry or QRIS receipt, so we can respond accurately.

Privacy Policy Questions Before Account Access

These answers address the Privacy Policy searches we expect before an Indonesian account is opened. They explain the practical records behind login, cookies, wallet references and support requests without asking you to share sensitive credentials. If your situation involves a local eligibility question, access depends on local law and we may need to assess the request under the rules that apply to you.

It covers data connected with your account, including contact details, phone verification, login events, device signals, cookies, support messages and payment references. It also explains our purposes, retention approach and the steps for asking about access, correction or deletion where local law permits.

Yes. The Privacy Policy includes records needed to match DANA, OVO, GoPay or QRIS activity with your account. A reference, amount or status may be retained for receipt checks and reconciliation, while your wallet password should never be sent to support.

Use the account support channel and identify the contact detail attached to your account. State that you are making a data request and name the record you want checked, such as login history, phone verification or a QRIS receipt. We may confirm your identity first.

You can ask us to correct an inaccurate contact, verification or account detail through support. Include the existing entry and the correction you believe is accurate. We review the request against account security and transaction records before applying a change where local law permits.

We retain data while it serves the account, security, support or transaction purpose for which it was collected. Payment references and related messages may remain needed after a wallet action for reconciliation. We assess continued retention when that purpose ends, subject to local law.

You can adjust cookie controls in the browser on your phone or computer. Some cookies support session continuity and page preferences, so refusing or removing them may require a fresh login or change how account pages behave. The Privacy Policy explains these uses in context.

Yes. Requests and account eligibility can depend on local law. Where local law permits, we will assess access, correction or deletion requests using the account detail and record reference you provide, while protecting security checks and transaction information from unauthorised disclosure.

Related Pages

petir36 Indonesia petir36 Casino Access guide Indonesia Football Reels 506 FAQ