Reference

Open with lek123 Privacy Policy

Baccarat, 288slot and Royal Fishing sit behind one account, while our Privacy Policy explains how we handle the details connected to your access.

Clear data purposesWallet record clarityRequest paths
lek123 Open with lek123 Privacy Policy
POLICY HELP ROUTE

Switch to policy support when needed

A clear contact path helps when you want to understand a Privacy Policy section rather than guess what an account record means.

Data request Ask us to confirm whether we hold a particular account record, such as a…
Correction path If your account name, phone detail or contact preference is inaccurate, contact support through…
Wallet question For an unclear OVO, GoPay or QRIS reference, use the support path beside the…
DATA HANDLING PRACTICE

Browse lek123 data handling choices

The Privacy Policy is supported by practical controls rather than broad promises. We limit account details to stated purposes, use session cookies for access functions, and connect wallet records to the account…

Data collected

We may collect your phone number, account details, session signals and payment references tied to activity on the site. The Privacy Policy explains why each category is needed, including phone verification before access and a reference check when a wallet status needs matching.

Cookie use

Cookies help preserve your signed-in session and selected account settings while you move between a lobby page and the cashier path. You can manage browser cookie controls, but restricting necessary cookies may interrupt access or require you to verify your account again.

Account security

We use the phone verification step and account checks to reduce unauthorised access. Keep your sign-in details private and contact support if a login or wallet status looks unfamiliar. We will use the request details to investigate the relevant account event.

Record retention

We retain account and payment references for as long as needed for the stated purpose, account administration, dispute checks or legal duties. The retention period can differ by record type, so ask support which category applies instead of assuming every entry follows one timetable.

Your requests

You can ask whether we hold your account data, request a correction, ask about use, or seek removal where applicable. Send the request through the account support route with enough detail to locate it; we may verify ownership before making a change.

Policy contact

Questions about the Privacy Policy belong with our support team through the contact route displayed in your account area. Mention the relevant section, such as cookies, phone verification or QRIS records, so the response addresses your actual concern rather than a general account query.

Check Privacy Policy answers for your account

These Privacy Policy answers cover the searches we hear before an Indonesian customer opens an account. They focus on the records created by access, cookies, phone verification and local wallet activity, with a direct route for questions that need an account-specific check. If your case involves eligibility or access, the applicable position is where local law permits.

The lek123 Privacy Policy covers account details, phone verification, device and connection signals, cookies, lobby activity records and payment references. It also explains purposes, retention, security measures and request routes. DANA, OVO, GoPay and QRIS references are handled as records connected to a relevant account action.

Phone verification helps us confirm account ownership before access and before discussing account-specific data. It can also help us investigate an unfamiliar login or wallet status. We use the verified phone detail for the stated account purpose, and you can ask support how it relates to your record.

Yes. The Privacy Policy covers the payment reference needed to match QRIS, bank transfer or virtual account activity with your account. We use that reference to check status or answer a receipt question, not to request your wallet PIN, full password or unrelated financial details.

You can contact support through the route shown in your account area and ask what account data we hold about you. Include your linked phone number and the record category, such as verification or wallet reference. We may complete an ownership check before releasing account-specific material.

Send a correction request through account support and identify the inaccurate field, such as a phone detail or contact preference. Explain the requested change clearly. We may verify your identity first, then update the record when the request is supported by the account details we hold.

Retention depends on the record purpose, account status, dispute checks and applicable legal duties. A DANA, OVO, GoPay or QRIS reference may remain while it is needed for account administration or a status question. Ask support about the specific category rather than a general estimate.

Use the support contact route displayed in your account or near the cashier path and mention Privacy Policy in your request. Include the relevant topic, such as cookies, phone verification or deletion. If access is part of the question, the answer applies where local law permits.