Reference

petirjitu Privacy Policy for Your Account

Our petirjitu Privacy Policy explains how we handle the account, device and wallet details connected with your visit, from phone verification through access to casino, football, badminton and…

Account dataWallet recordsDevice choicesLocal access
petirjitu petirjitu Privacy Policy for Your Account
HELP PATH

Wallet Data Help Near Login

A clear support path helps you ask about Privacy Policy matters without explaining your whole account history. Start from the account help route beside login or the cashier area, then include the phone number on the account, the relevant DANA, OVO, GoPay or QRIS reference, and the device path you used. We use those details to locate the correct record and limit unnecessary questions.

Team online

Account access

If phone verification or a mobile sign-in leaves you unable to reach your account, contact us through the account help path. We use the registered phone detail to confirm which record your Privacy Policy request concerns.

Payment receipt

For a DANA, OVO, GoPay or QRIS data question, send the receipt reference and date through the cashier support path. We can check the matching status while avoiding a request for your wallet password or private security code.

Data request

To ask for a copy, correction or removal of eligible account details, state the request clearly and include your registered phone contact. We may ask for an account step that confirms you are the account holder.

CONTROL LAYER

How We Handle Account Data

Our data handling follows the account actions you choose rather than collecting unrelated details. Phone verification, wallet references and device signals serve different purposes, and we keep those purposes separate when checking…

Account details

We use your registered phone contact and verification result to create an account link, confirm sign-in requests and respond to account questions. We do not need your DANA, OVO, GoPay or QRIS password to trace a payment record.

Device signals

A mobile browser or desktop session can send device type, browser details, approximate session time and sign-in events. These signals help us spot an unusual account path, especially after a phone verification step.

Cookies

We use necessary cookies to keep a sign-in step, language choice and policy access working. You can manage browser cookie settings, but blocking necessary cookies may prevent the account page from remembering your current session.

Account security

We may compare phone verification, sign-in timing and device signals before discussing account data or a wallet receipt. This extra check helps prevent another person from changing details through an unverified request.

Retention choices

We keep account and payment references only for the period needed for account security, support tracing and applicable records. When a record no longer serves those purposes, we remove or separate it where practical.

Policy changes

If this Privacy Policy changes, we will place the revised wording on this page and identify the updated date. You can contact us through the account help route to ask what changed or request a data correction.

Privacy Policy Questions for Indonesia

These Privacy Policy answers cover the account steps most likely to raise a data question: phone verification, mobile access, wallet references, cookies, retention and requests for change. If your situation involves a DANA, OVO, GoPay or QRIS receipt, include its reference when you contact us so we can respond to the right record.

It covers account details, phone verification, device signals, cookies, wallet references and support requests connected with your access. It also explains retention, security checks and how to ask for a correction or eligible removal.

We use phone verification to connect an account action with the correct account holder and reduce mistaken access. It may be checked before we discuss a DANA, OVO, GoPay or QRIS record.

Yes. The policy covers payment references, status and receipt details from DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account references when those routes are used.

We may receive browser type, device category, sign-in timing and session signals from your mobile or desktop path. We use them for account security and support tracing, not to request your wallet password.

You can ask through the account help route by giving your registered phone contact and describing the requested copy or correction. We may complete an account check before discussing or changing personal details.

We retain records for account protection, support tracing and applicable record needs. Once a record no longer serves those purposes, we remove or separate it where practical under the handling rules described here.

Yes. Account access and eligibility depends on local law. Where local law permits, you can use the listed support path to ask about your account data, device record or wallet receipt.