Reference

lucubet Privacy Policy for Your Account

lucubet Privacy Policy explains how we collect, use and protect the account details connected with your lobby access, including payment records from DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
lucubet lucubet Privacy Policy for Your Account
CONTACT ROUTES

Help With Privacy and Wallet Records

A clear contact route matters when a privacy request overlaps with account access or a wallet receipt.

Account access If your phone verification or login is blocked, use the account support route rather…
Wallet receipt For DANA, OVO, GoPay or QRIS questions, include the wallet name, transaction reference and…
Privacy request Ask us to correct, provide or remove eligible account data through the same support…
SIX DATA CONTROLS

Six Privacy Controls Behind lucubet

We handle privacy as an account operation, not as a separate page that sits away from the cashier path.

Account creation

When you open an account, we collect the details needed to create your profile and provide the account path.

Device signals

Your browser and device may provide technical signals such as session details, language settings and access patterns.

Cookie controls

Cookies can keep a session active, remember selected settings and help us understand page errors.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may be stored with its reference and status.

Account security

We use phone verification, session checks and account review steps to reduce unauthorised access.

Retention requests

You can ask what personal data we hold, request a correction or ask whether deletion is available.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet record is queried. We keep the wording practical: what we collect, why a verification step appears, how cookies behave on mobile and how you can contact us. If your question concerns a particular DANA, OVO, GoPay or QRIS reference, use the account support route with the reference ready.

The lucubet Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment records. It explains why we use each category, how we protect account access, how retention works and how you can request correction, access or removal where that action is available.

Yes. The Privacy Policy covers records linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We may retain a reference, amount status and related account link so we can match a receipt, resolve a query and maintain accurate payment history.

Phone verification connects the account request to the person seeking access and gives us a security check before sensitive details are discussed. It can also help us protect a wallet record when you ask about a DANA receipt or request a change to account details.

Our Privacy Policy covers cookies used for session continuity, selected settings and page diagnostics. On your mobile browser, you can change cookie permissions through the browser controls. Restricting some cookies may interrupt login continuity or change how account pages behave on your device.

You can request a correction through the account support route. Tell us which detail is wrong and provide the account reference requested during verification. We may confirm ownership before making a change, then explain whether the correction is complete or whether another record must remain unchanged.

Send an access request through the support link inside your account and describe the records you need, such as phone details, cookie preferences or a QRIS transaction reference. We verify the request first, then explain the available copy, any limits and the expected handling step.

Any account access or eligibility described on this page depends on local law. The Privacy Policy still explains our data handling approach for supported Indonesia access, but the available service, request outcome or retention requirement may differ. Contact support when you need a case-specific answer.