Reference

demo slot jili Privacy Policy

Our Privacy Policy explains how demo slot jili handles the details connected to your account, wallet activity and device access.

Clear data purposesWallet record checksCookie controlsAccount access requests
demo slot jili demo slot jili Privacy Policy
CONTACT PATHS

Get privacy help beside account support

A clear contact path matters when a privacy request and a wallet receipt concern arrive together. We ask you to use the support route connected to your account, include the email or phone number on file, and state whether you need access, correction, deletion or a clarification. This lets us verify the request without asking for a full wallet password or an unnecessary copy of your payment credentials.

Team online

Account data request

Send an access or correction request through account support and identify the account step involved, such as phone verification or a sign-in record. We compare the request with the details on file before sharing or changing account data.

Wallet receipt check

If a DANA, OVO, GoPay or QRIS receipt appears beside the wrong status, include its reference and date through the support route. We use the payment reference to investigate without requesting your wallet PIN.

Security concern

For an unfamiliar device or failed login pattern, contact us through account support and describe the time and device shown. We can review security events, protect account access and explain which records were used for the check.

HOW WE HANDLE DATA

Inside demo slot jili privacy controls

Our handling steps are tied to ordinary account actions rather than broad collection. Login events help us check access, cookies help remember selected settings, and payment references help reconcile a DANA or…

Account details

We use your account identifier and phone verification result to connect sign-in activity with the correct account. This supports access checks and helps us avoid sending a privacy response to the wrong person.

Cookies and settings

Cookies can remember choices made during a browser session, including selected display or access settings. You can manage cookies through your browser controls, although changing them may affect how the account page remembers your preferences.

Security records

Device type, sign-in time and failed access events help us identify unusual account activity. If you use a phone for the lobby and a desktop later, these records may show both access points during a security check.

Payment references

A QRIS, DANA, OVO, GoPay, bank transfer or virtual account reference can be retained to reconcile a payment status. We do not need your wallet PIN to investigate a receipt or explain a cashier record.

Retention requests

You may ask how long a particular account or payment record is kept and request deletion where available. Some records can remain when a legal, security or transaction-reconciliation duty requires their retention.

Corrections and access

To request a copy or correct an inaccurate detail, contact support from the account path and describe the field or event. We may confirm phone or email ownership before changing information connected to your account.

Privacy Policy answers for your account

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet receipt is checked. Each answer points back to a practical account action, from phone verification and cookie settings to a request for access or correction. If your case involves a specific receipt, include its reference so we can narrow the response.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains your routes for access, correction, deletion and privacy questions.

Phone verification helps us connect the account request to the person seeking access and reduces mistaken or unauthorised account changes. We may use the verification result during a privacy request, especially before releasing account details or changing a phone-linked record.

Use the support path connected to your account and ask for an access copy, naming the account email or phone number on file. We may confirm ownership first, then explain which account, security and payment-reference records can be provided under local requirements.

Yes, send the receipt reference, date and the account detail that appears incorrect through support. We compare the reference with the matching DANA or QRIS status and can correct an account record when the request is verified and the record is not required unchanged.

Cookies can retain browser choices and session settings, so the account page may recognise a selected preference when you return. You can remove or restrict them in your browser. If a setting stops being remembered, support can help separate a cookie issue from an account-access issue.

The period depends on the type of record and the reason it was created. Security events and payment references may need to remain for account protection, reconciliation or legal duties. You can ask support about a particular record and request deletion where local law permits.

The policy is written for account access in Indonesia, but availability and certain rights depend on local law. If you are in Bandung or another location, check the access wording shown for your account and contact support when a regional rule affects your request.