Reference

warnetslot Privacy Policy for Indonesian Accounts

Our Privacy Policy explains how warnetslot handles the details you provide when opening an account, checking wallet status, or entering the lobby where local law permits.

Account dataWallet recordsCookie choicesSecurity checks
warnetslot warnetslot Privacy Policy for Indonesian Accounts
PRIVACY SUPPORT

Get Privacy Policy Help Through Your Account

A clear contact path matters when a privacy question affects your login or wallet status. Start from your signed-in account and include the email or phone detail connected to the request, the relevant transaction reference, and the device path you used. We use those details to locate the right record while limiting unnecessary disclosure.

Team online

Account request

Ask us to check personal data linked to your account by sending the request from the signed-in account path. We may verify ownership before discussing account records.

Wallet record

For DANA, OVO, GoPay, QRIS, or bank transfer questions, include the payment reference and status shown in your cashier history so we can trace the matching record.

Access concern

If privacy controls affect access on mobile or desktop, tell us the device path and last account step completed. We use this context to separate security checks from data requests.

SIX CONTROL POINTS

Six Privacy Controls Behind Your Account

We apply this Privacy Policy through everyday account handling rather than a separate process you have to learn.

Data collection

We collect account, contact, payment-reference, device, and session details when they are needed for login, phone verification, cashier matching, security…

Cookie choices

Cookies and similar session tools help keep you signed in and remember the route from login to the lobby.

Account security

Phone verification, session signals, and device checks help us identify unusual access.

Retention process

We keep account and payment records for the time needed to operate services, resolve disputes, protect accounts, and meet applicable…

Data correction

If your contact detail or account record is inaccurate, request a correction from the signed-in account path.

Request handling

For access, correction, deletion, or processing questions, explain what you need and identify the relevant account step.

Privacy Policy Questions About Your Data

These Privacy Policy answers focus on the searches we hear most often before an account is opened or a wallet record is checked. If your situation is not covered, use the account contact path with the smallest useful set of details, and we will assess the request under the policy and local law.

It covers account details, phone verification, wallet and payment references, cookies, device signals, session activity, retention, security handling, and requests to access, correct, or remove personal data.

We record payment references, status, timing, and related account details so DANA or QRIS activity can be matched to the correct cashier record and investigated if a payment stalls.

Yes. The policy covers data gathered when you use a mobile browser or desktop browser, including session and device signals needed to keep login, phone verification, and account security working.

Send the request through your signed-in account path and describe the records you need, such as contact details, wallet references, or session history. We may verify account ownership first.

Yes. Tell us which account detail is inaccurate and provide the matching account context. We review correction requests carefully, especially when the change could affect phone verification or wallet matching.

We keep records for operational, security, dispute, and legal needs described in the Privacy Policy. When the relevant purpose ends, records are removed or anonymised through our retention process.

Use the signed-in account contact path and include your request type, relevant account step, and any payment reference. Processing and eligibility depend on local law, and identity checks may apply.