Reference

Privacy Policy For Your petir800 Account

Our Privacy Policy explains what we collect when you open a petir800 account, verify your phone, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
petir800 Privacy Policy For Your petir800 Account
REQUEST HELP DIRECTLY

Get Privacy Help Near Your Account

A clear contact route matters when your personal data needs correction, access or removal.

Account support path Use the support route after signing in and identify your account with its linked…
Payment record request For a QRIS, bank transfer or virtual account question, include the receipt reference and…
Access correction request Tell us whether you want to see, correct or remove a specific detail.
DATA HANDLING DETAILS

What Our Privacy Process Covers

Privacy is handled through practical account steps rather than a single setting. We separate sign-in details from cashier references, use cookies to remember useful session choices and check…

Account information

We may hold your chosen account details, linked phone, verification result and sign-in history.

Cookie controls

Cookies can remember a session choice, language setting or security state on your browser.

Device signals

Browser type, device signals and connection details may be assessed when a login or wallet status changes unexpectedly.

Payment matching

A QRIS receipt, bank transfer reference or virtual account record can be linked to your account so cashier status is…

Retention choices

We keep personal records while they support account access, security checks, dispute handling or legal duties.

Policy changes

If this Privacy Policy changes in a way that affects your account data, we will place the updated wording on…

Privacy Policy Answers For petir800

These questions focus on the searches we hear most often about the petir800 Privacy Policy. Each answer points to a real account action, payment record or contact route, so you can decide what to share and how to ask for a change before opening the lobby.

It covers account details, phone verification, login and device signals, cookies, payment references and privacy requests. It also explains why we use DANA, OVO, GoPay, QRIS, bank transfer or virtual account records when matching a cashier action.

We may collect the details needed for account access, including your linked phone or email, verification result, session data and support messages. When you use QRIS or another listed rail, we may also receive a transaction reference rather than your wallet password.

Phone verification helps us connect the person entering the account with the account record and reduce mistaken access after a device change. It can also support a privacy request when you ask us to correct or remove linked account data.

We use DANA or QRIS references to match a payment event with the right account and check a status query. The reference can show timing and amount context, while wallet credentials remain with the payment service and are not requested by us.

Yes. Send an access request through the support path connected to your account and name the record you want to see, such as login history, phone details or a payment reference. We may verify your linked phone before sharing account-specific data.

Use the same support route and state whether you want a correction or removal request. Include the linked phone or email and the exact detail concerned. We assess the request against active security, dispute and legal retention needs before responding.

Our Privacy Policy is written for the account and payment paths used in Indonesia, including DANA, OVO, GoPay and QRIS. Access and eligibility depends on local law, and the policy applies where local law permits. Support can clarify a record-specific request.