Reference

Privacy Policy for pajaktoto slot

pajaktoto slot Privacy Policy explains what we collect when you open an account, use the mobile lobby, or check DANA, OVO, GoPay and QRIS status.

Account dataWallet recordsCookie choicesPrivacy requests
pajaktoto slot Privacy Policy for pajaktoto slot
PRIVACY CONTACT ROUTE

Where to ask about your policy data

Privacy questions should reach us through the account support path linked near the cashier area, so we can connect your request with the correct account record.

Account support Use the account support path when you want to ask how your phone verification…
Cashier privacy check For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, mention the payment…
Access recovery If a mobile browser session blocks your account, contact us through the same support…
DATA HANDLING DETAILS

What we do with your privacy choices

We keep this Privacy Policy practical by tying each data use to an account action you can recognise.

Account security

Before we discuss private account details, we may compare your request with the phone verification step used at account access. This helps us avoid exposing a record to the wrong person while keeping the check connected to the account you actually control.

Cookie controls

Our mobile and desktop pages may store cookies or similar browser signals for session continuity, sign-in behaviour and fault diagnosis. You can clear site data through your browser settings, although doing so may require the phone verification step again.

Payment references

A DANA, OVO, GoPay or QRIS action can create a reference, status and timestamp linked to your account request. Bank transfer and virtual account records follow the same matching purpose, so support can separate an incomplete status from a completed one.

Device signals

When you move from login to the mobile lobby, we may receive basic device and browser details such as type, session state and language settings. These signals help identify a broken session and are not a request for access to unrelated files on your device.

Retention questions

We retain account, security and transaction records only for the period connected to their stated purpose or a necessary account matter. Ask through account support which category applies, why it remains stored and whether a deletion or restriction request can be handled.

Change requests

You can ask us to correct inaccurate contact details, explain a data category, or clarify how a cookie or wallet reference is used. Include the account contact and request type; do not send a password, wallet PIN or full payment credential.

Privacy Policy questions about your account

These Privacy Policy answers address the account and device questions you may have before opening access to the Indonesia lobby. We keep each answer tied to a concrete action, including phone verification, wallet status, browser cookies and contact requests. If your situation is not covered, use the account support path and describe the record you want us to locate.

It covers account contact details, the phone verification step, device and browser signals, cookies, wallet references and support requests. It also explains why we retain a record, how you can ask for correction, and how access is handled where local law permits.

We use your phone number for the clear verification step before account access and to connect a privacy request with the correct account. It is not a request for your wallet PIN. If the number is wrong, ask support to explain the correction path.

Yes. A DANA or QRIS action can produce a payment reference, status and timestamp linked to your account request. OVO, GoPay, bank transfer and virtual account records follow the same matching purpose, allowing us to answer a status question without requesting your wallet password.

Cookies and similar browser signals can keep a mobile or desktop session connected and help us diagnose a failed login. You can clear them in your browser settings. After clearing site data, you may need to complete phone verification again before account access.

You can request correction when an account contact detail or another stored record is inaccurate. Send the request through account support with the relevant account contact and the category to change. We may complete an account check before discussing or editing private details.

Retention depends on the reason for the record, such as account security, phone verification, wallet matching or an open support matter. Ask us which category applies and why it remains stored. Any access or processing question depends on local law and the applicable account context.

Use the account support path near the cashier area and state whether you need access, correction, deletion clarification or a cookie explanation. Mention the relevant DANA, QRIS or device detail when useful, but never send a password, wallet PIN or full payment credential.