Reference

Terms & Conditions for Your lucubet Account

lucubet sets out clear Terms & Conditions for opening an account, using Live Baccarat Royal, and moving between the lobby and your wallet.

Account access rulesWallet verificationPolicy contact pathIndonesia conditions
lucubet Terms & Conditions for Your lucubet Account
POLICY HELP

Account Terms Help From the Cashier Path

A clear contact route matters when a policy question affects your account or wallet status.

Account policy request Use the support route inside your account to ask about a clause, an account…
Wallet status question If DANA, OVO, GoPay or QRIS status does not match your account record, send…
Access clarification For a question about account availability in Indonesia, tell us your account region and…
DATA AND RECORDS

How We Handle Terms and Account Records

The Terms & Conditions also explain how account data supports payment checks, security controls and policy administration.

Phone verification

Before account access is completed, we may use the phone detail you submit to confirm that the account request belongs…

Account security

You are expected to keep login details private and to tell us when you notice an unfamiliar session or account…

Cookies and sessions

Cookies and session records can help keep your account area connected while you move from login to the lobby.

Payment records

For DANA, QRIS, bank transfer or virtual account activity, we retain the reference needed to compare the cashier request with…

Retention requests

We keep policy, account and transaction records only for the period needed for account administration, security checks or an applicable…

Correction contact

If your name, phone detail or payment reference is inaccurate, contact us through the account support route and identify the…

Terms & Conditions Questions Answered

These answers address the policy searches we hear most often before an account is opened. The full Terms & Conditions remain the controlling text, including any wording shown during phone verification, payment confirmation or an account security check. If your question concerns a specific record, use the support path with your account reference.

You can open the Terms & Conditions from the policy link in the account area before completing account access. We may also show relevant wording during phone verification, cashier confirmation or a security check. Read the current version there, because that text applies to the action you are taking.

Account access depends on local law and the conditions shown for your region. We may ask for a phone detail and other account information before access is completed. If the page does not permit your request, contact support with your region so we can explain the applicable policy wording.

The Terms & Conditions require payment details and account records to match. DANA and QRIS may be available where local law permits, with the cashier showing the applicable confirmation steps. Keep your payment reference, because support uses it to check a receipt or status question.

Phone verification helps connect the account request with the phone detail you submit and supports account security. The Terms & Conditions explain when this check may occur and what happens if it cannot be completed. Keep the registered detail available before you continue through the account path.

Yes. Send a correction request through the account support route and name the record or field that appears wrong, such as a phone detail or payment reference. We may ask for evidence before changing it, and some transaction records may need to remain stored.

We may pause the related account action while comparing the cashier request with the payment reference and submitted account details. This can apply to OVO, GoPay, DANA, QRIS, bank transfer or virtual account activity. Support can explain the relevant Terms & Conditions clause.

We may update the Terms & Conditions when account processes, payment routes or applicable rules change. We place the current wording in the policy area and may present it before a relevant account action. Check that version before continuing, especially where local law permits access.