Reference

Privacy Policy for pusat lotre accounts

Our Privacy Policy explains how we collect, use, protect and retain data when you open a pusat lotre account or access the lobby from your phone or desktop.

Account dataWallet recordsDevice accessPolicy requests
pusat lotre Privacy Policy for pusat lotre accounts
POLICY CONTACT

Get Privacy Policy help beside your account

A clear contact path matters when a privacy question appears during phone verification or a wallet check.

Account access request If your phone verification stalls, tell us which account step failed and ask for…
Wallet data question For DANA, OVO, GoPay or QRIS records, include the transaction reference, date and rail…
Correction or deletion Ask through account help when a name, phone field or contact detail needs correction…
DATA PRACTICE

How pusat lotre handles policy requests

We keep this Privacy Policy tied to real account actions rather than broad statements. A phone verification event helps us connect a request to the right account; device signals help us spot…

Data collection

We collect data you provide during account creation and phone verification, plus records created when you sign in, contact support or request a wallet status check. A game selection, such as Aviator Mobile Play, is handled as activity connected to your account rather than a reason to gather unrelated data.

Cookies and devices

Cookies and similar device signals can help keep a signed-in session working, remember necessary settings and identify unusual access. On a phone, your browser may retain session data; clearing site data can sign you out and may require phone verification again before account access.

Account security

We use phone verification and sign-in records to help protect account access. Never send us your password, wallet PIN or one-time code. If your device changes before you open Fishing War Fast Round, contact account help so we can check the access event without exposing secret credentials.

Payment records

A payment request can create a record containing the selected rail, transaction reference, amount and status needed for reconciliation. DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries may be retained when needed to resolve a receipt question or meet a legal obligation.

Retention choices

We keep personal data only for the period needed to provide account service, protect the account, resolve disputes or satisfy legal duties. When a record no longer serves one of those purposes, we assess deletion or de-identification under our internal retention process rather than keeping it without a reason.

Request ownership

A request to see, correct or delete data must come from the account holder or an authorised person. We may ask for a safe account check before responding. Use the support route shown in your account, state the requested action and avoid attaching identity documents unless our support team specifically asks.

Privacy Policy answers for Indonesian accounts

These Privacy Policy answers cover the questions we expect before you open an account or ask us to change a record. They focus on account access, payment references, cookies, device use and contact steps for Indonesia. If your situation is not listed, send a focused request through account help and include only the minimum data needed to locate your record.

It covers data collected during account creation, phone verification, sign-in, support contact and payment status checks. It also explains cookies, device signals, retention, security steps and your routes to request access, correction or deletion, with handling shaped by local law.

Phone verification helps us connect account access with the correct contact detail and reduce mistaken or suspicious requests. It may be needed again after you clear browser data, change device or ask for a sensitive Privacy Policy action involving your account.

Yes. The Privacy Policy covers transaction references and status data connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records for reconciliation, receipt questions, account service and legal duties, not for unrelated collection.

You can request correction through the support route shown in your account. State which field is wrong, such as a phone or contact detail, and complete the account check we request. We will explain the outcome and any record that must remain.

Send a deletion request through account help and identify the account record you want assessed. We first confirm account ownership, then check whether retention is required for security, transaction reconciliation or legal duties. Access depends on local law and the result may be limited.

A mobile session can create sign-in, browser, device and cookie records needed for access, settings and account security. If you clear site data, you may be signed out and asked to complete phone verification again. We retain these records only for stated service or legal purposes.

Use the support contact displayed on our site or the account-help route near the cashier path. Ask for a copy, correction, deletion assessment or explanation of use. Include your registered contact detail and request type, but never send a password, wallet PIN or one-time code.