Reference

Legal terms for your gucibet account

gucibet Legal terms explain how your account, phone verification, wallet records and lobby access are handled before you open Baccarat, winlose or Rocket Crash.

Account termsData requestsLocal eligibilityPolicy contact
gucibet Legal terms for your gucibet account
POLICY HELP ROUTES

Get policy answers through account support

A clear contact path matters when a Legal question affects your account or wallet record.

Account access questions If you need to understand an account clause, send the question through the signed-in support route. We can point you to the relevant Legal wording and explain which account step, such as phone verification, applies before access.
Wallet record requests For a DANA, OVO, GoPay or QRIS record, include the payment name and receipt reference in your request. We use those details to separate a policy question from a pending provider status without exposing unrelated account data.
Correction and contact If your personal details need correction or you want to ask who handles a policy matter, use the account support route and state the exact change. We will assess the request against the applicable Legal terms and reply through the contact details on file.
DATA HANDLING

See how we handle your legal data

Legal clarity also means knowing what happens to the records connected with your account. We handle sign-in details, phone verification results, payment references and support messages for the purposes described in our…

Account records

We use the details you submit during account creation and phone verification to identify the account connected with a Legal request. Providing accurate details helps us avoid sending policy answers to the wrong contact or applying a change to the wrong record.

Payment references

A payment reference can connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event to your account history. We use that reference to check the specific record involved, rather than asking for unrelated wallet details.

Cookies and browser use

Cookies and similar browser storage may help retain account state or security preferences on the device you use. You can review browser controls on mobile or desktop, while certain account functions may require a fresh sign-in.

Account security

Keep your password and verification codes private, and contact us if an account detail looks unfamiliar. We may request an account check before discussing personal records, changing contact details or responding to a sensitive Legal request.

Retention of records

We retain account, payment and support records for the period described in the applicable policy or required for a legitimate operational purpose. A retention question should identify the record type, such as phone verification or QRIS receipt.

Requests and changes

To request access, correction or clarification, use the support route connected with your account and describe the exact record involved. We may need to confirm your account before acting, so the response reaches the correct person.

Answers to common Legal searches

These Legal answers cover the questions we expect you to ask before opening an account or sending a policy request. We focus on account identity, local eligibility, data handling and payment records because those areas usually determine what we can explain or change. If your situation is not covered, contact us through the account support route with the relevant account or receipt reference.

The gucibet Legal page covers account conditions, phone verification, data handling, cookies, payment references, retention and policy requests. It also explains that account access depends on local law and may require an account check before we discuss personal records.

You may open an account where local law permits and where the applicable account conditions are met. We may request accurate contact details and phone verification before account access. If eligibility is unclear, use the account support route before submitting payment details.

Phone verification helps us connect an account request with the correct contact detail before access or a sensitive policy response. Keep the verification code private. If the step fails, contact support from the account route and describe the message shown.

DANA and QRIS references may be used to identify a payment event connected with your account. Our policy concerns the account record we hold, while the wallet or payment provider may keep separate records under its own conditions.

Yes. Send a correction request through the account support route and name the exact detail, such as a phone number or contact field. We may confirm your identity first, then assess the requested change against the applicable Legal terms.

The applicable policy explains how long different records may be retained for operational, security or legal reasons. Ask about a specific record, such as a support message, phone check or GoPay receipt, so we can address the relevant retention rule.

You can check cookie controls in your mobile browser settings and review the policy wording connected with account access. If a cookie question affects sign-in or saved account state, contact us with your device path and the exact behaviour you noticed.