Reference

petirslot168 Privacy Policy For Your Data

Our petirslot168 Privacy Policy explains what we collect when you open an account, verify your phone, browse from mobile, or use DANA and QRIS.

Account recordsWallet activityCookie choicesContact requests
petirslot168 petirslot168 Privacy Policy For Your Data
HELP WITH DATA

Where To Ask About Your Data

A clear contact path matters when a phone check, login record, or wallet receipt needs attention.

Account data request Ask us to confirm the account details connected with your registered phone number. We may request an account step or identity check before releasing, correcting, or discussing personal records.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account queries, include the receipt reference and status shown in your account so we can match the correct payment record.
Cookie or device help Tell us whether you are using a mobile browser or desktop browser and what changed after clearing cookies. This helps us separate a session issue from an account-data request.
SIX DATA PRACTICES

Six Privacy Controls For Your Account

We keep this policy practical by linking each privacy decision to an account action you can recognise.

Data collected

We may store your registration details, phone verification result, login timestamps, browser and device signals, selected lobby activity, and transaction references needed to operate account support.

Cookie handling

Essential cookies keep your session and account path working. Clearing them can remove saved preferences and require another login, but it does not erase records already held for your account.

Account security

We use phone verification, login events, and device signals to identify unusual access. Never send a wallet PIN or password through a support request about DANA, OVO, GoPay, or QRIS.

Retention approach

We retain account and transaction records while needed for account operation, receipt matching, disputes, security checks, or legal duties. Some records may remain after closure for those purposes.

Correction requests

If your phone detail or another account record is wrong, contact us through the account support path. Include the requested correction and the account step that confirms it belongs to you.

Policy contact

You can ask what data we hold, why it is used, or how a request is handled. We may need to verify account control before changing or disclosing personal details.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to notice: phone verification, mobile sessions, wallet receipts, cookies, and requests to change personal records. If your situation is not covered, send the account support request with the relevant reference so we can examine the correct data.

It covers account details, phone verification, device and browser records, cookies, lobby activity, and transaction references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

Phone verification helps us connect an account request to the correct account holder, reduce mistaken access, and handle data changes safely. We record the verification result rather than asking for your wallet password.

Yes. We may retain the payment reference, amount, time, and status needed to match a DANA or QRIS receipt with your account and investigate a missing or delayed status.

We may record device type, browser details, session timestamps, and technical access signals. These records help us distinguish a normal mobile login from an unusual session requiring an account check.

Use the support path connected to your account and state which record needs correction. Include your registered phone detail and the requested change; we may verify account control before editing it.

Yes, you can clear cookies through your mobile or desktop browser settings. This may sign you out or remove session preferences, while stored account and transaction records remain subject to the Privacy Policy.

We keep records for as long as needed for account operation, wallet receipt matching, security checks, disputes, or legal duties. A closure request does not always remove records required for those purposes.