Reference

loket88 Privacy Policy For Your Account

loket88 Privacy Policy explains what we collect when you open an account, use the mobile lobby, or check DANA and QRIS status, and why each record is needed.

Clear data purposesWallet record contextCookie choicesAccount request path
loket88 loket88 Privacy Policy For Your Account
HELP WITH RECORDS

Where Your Privacy Questions Go

A clear support route matters when a privacy request meets an account or wallet record. Open the support path from your account area and include the phone number or account identifier connected to the request, plus a payment reference when your question concerns DANA, OVO, GoPay, or QRIS. We use those details to locate the right record, avoid asking you to repeat the same explanation, and keep the request tied to your account.

Team online

Account data request

Ask us to explain the account details connected with your loket88 profile. Include your registered phone number and the specific record you want checked, such as a login event or phone verification entry.

Wallet record question

For a DANA, OVO, GoPay, or QRIS query, add the payment reference and approximate date shown in your account. We can then separate our record from the wallet or bank record.

Change request

Use the privacy support route when you want to correct an account detail, ask about retention, or request a policy explanation. We may ask for an account step that confirms you are making the request.

HANDLING DETAILS

What We Do With Your Account Data

We handle privacy as part of the account path, not as a separate page you must decode.

Account records

We keep information you submit for your account, including contact details and phone verification status, alongside the account actions needed to operate access. We do not ask for unrelated details to answer a normal privacy request.

Cookies and browser data

Cookies and similar browser signals can help maintain sign-in state, remember a selected setting, and identify technical errors. You can manage browser permissions, although changing them may affect the route from mobile login to the lobby.

Account security

Login events, device details, and phone verification help us investigate access concerns. If a sign-in or wallet status looks unfamiliar, contact support through the account route and do not send a password in your message.

Retention periods

We retain records only for as long as they serve account operation, payment matching, security checks, dispute handling, or an applicable obligation. A request about a DANA or bank transfer reference may need a longer record trail than a browser setting.

Corrections and access

You can ask what account data we hold or request a correction when a detail is wrong. To protect your account, we may confirm the registered phone number and ask you to identify the affected record before making a change.

Contact ownership

Send privacy questions through the support path shown in your account area. Tell us whether the request concerns cookies, phone verification, Dragon Tiger activity records, or a QRIS reference so the request reaches the right handling queue.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet record is checked. We keep the examples close to the actual account path: phone verification, mobile browser access, payment references, and lobby activity such as Dragon Tiger or Valorant. If your situation is different, use the privacy support route and describe the record in question.

The loket88 Privacy Policy covers account details, phone verification, login and device events, cookies, support messages, lobby activity records, and payment references. It explains why we use each category, how long records may remain, and how you can ask for access or correction.

We use your phone number to create and identify the account, complete the phone verification step, and connect a privacy request to the correct record. It can also help us investigate an unfamiliar login. We will not ask you to place a password in a support message.

Yes. The Privacy Policy covers payment references generated when you use DANA, QRIS, OVO, GoPay, bank transfer, or a virtual account. We use those references to match status with your account; the selected wallet, bank, or payment processor may hold separate records under its own terms.

You can request details connected to your account through the privacy support path. Include your registered phone number and describe the record, such as a login event, cookie setting, Dragon Tiger activity entry, or QRIS reference. We may verify account ownership before responding.

Send a correction request through the account support route and identify the inaccurate field. For example, you can point to a contact detail or phone verification status. We may ask for a confirming account step so a change is made only for the right profile.

Our Privacy Policy explains that cookies and related browser signals can preserve sign-in state, remember settings, and help diagnose a mobile access issue. You can change permissions in your browser. Some settings may then require you to repeat the login path before reaching the lobby.

Account access and eligibility depend on local law and are available where local law permits. The Privacy Policy describes our data handling for that access, but it does not replace rules that apply in your location. If you need clarification, contact us through the privacy support route.