Reference

petir777 Privacy Policy for Your Account Data

petir777 Privacy Policy explains how we handle your account details, phone verification, mobile browser activity and wallet records when you use our Indonesia service.

Account recordsWallet referencesMobile access
petir777 petir777 Privacy Policy for Your Account Data
CONTACT PATHS

Privacy Questions Near Your Account

A clear contact route helps when you want to ask about a record, correct a detail or understand a wallet reference.

Privacy contact Send a question about personal data through the account privacy path. Include your account phone number and the subject of your request, while leaving out passwords, wallet PINs and one-time codes.
Account access If you cannot reach the policy page after phone verification, use the support route beside the cashier path. We can check the account state and explain which access step is blocking the request.
Receipt status For a DANA, OVO, GoPay or QRIS receipt question, share the transaction reference and date through support. We use those details to locate the record without requesting your private wallet credentials.
DATA PRACTICES

How We Handle Cookies And Account Data

We explain our data handling in practical terms so you can make an informed account choice. The policy covers cookies, security checks, retention and requests to change your records.

Account details

We use the details you submit during account opening, including your phone number, to create the account, complete phone verification and connect account activity with the correct record.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create transaction references. We use status, timestamp and reference data to reconcile the account record.

Cookies

Cookies and similar browser storage can remember session settings and help the account menu load correctly. Our Privacy Policy explains their purpose and how they relate to your access.

Account security

Phone verification and login signals help us identify account access. Never send a password, wallet PIN or one-time code when asking us to check a privacy request.

Data retention

We retain records for the period described in the Privacy Policy, considering account service, transaction matching, dispute handling and legal duties that depend on local law.

Change requests

To request correction, access or removal where available, contact us from the account privacy path. We may ask for account details to confirm that the request is yours.

Privacy Policy Questions About petir777

These answers address the privacy searches we hear most often before an account is opened. They cover the data connected to phone verification, wallet references, browser access and requests for a copy or correction. If your situation is different, use the account privacy contact path and describe the record you want us to check.

It explains the account, device, cookie, login and wallet-reference data we handle, why we use it, how long we retain it and how you can contact us about access or changes.

Yes. The policy covers transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. It does not ask for your wallet password or PIN.

We use your phone number to create the account, complete the phone verification step and connect support or transaction questions with the correct account record. Access depends on local law.

Open the service in your mobile browser, complete the available account access step, then choose the privacy link from the account menu. The same path shows the current policy wording.

Yes. Send a correction request through the privacy contact path and identify the account detail that appears wrong. We may confirm your phone-linked account before changing or responding about the record.

Retention depends on the record and the purpose described in our Privacy Policy, including account service, transaction matching, disputes and legal duties. The applicable position depends on local law.

Include your account phone number, the type of request and any relevant transaction reference or date. Do not include passwords, wallet PINs or one-time codes in a message.