Reference

Privacy Policy for gucibet Accounts

gucibet Privacy Policy explains how we handle the account, wallet and device details you provide when you access Baccarat, Rocket Crash or other lobby areas.

Account clarityWallet recordsDevice controlsCookie choices
gucibet Privacy Policy for gucibet Accounts
CONTACT WHEN NEEDED

Get Privacy Help Beside Account Support

A privacy question should not require you to search through the lobby. We give you a direct route through account support, where our team can check the request type, confirm the account…

Account support Use the support contact shown in your gucibet account area when you want to ask about stored details, a correction or a copy request. We first match your request to the account record so another person cannot receive private account data.
Payment record check If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the date, amount and reference code through support. We can trace the account-side status without asking you to reveal your wallet password or full banking credentials.
Access concern For an unfamiliar sign-in or device, contact us promptly through the account support route and change your password from the sign-in page. We can review recent access markers, pause a verification step and explain which records relate to your account.
HOW WE HANDLE DATA

Practical Controls for Your Privacy

Privacy depends on small account habits as much as policy wording. We separate contact details from wallet credentials, limit internal access to records needed for support or transaction handling, and use device…

Account details

We use your name, phone or email and verification status to create the account path, send account messages and respond to requests. Before changing these details, we may ask you to confirm an existing account step so the request comes from you.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep payment references, status and related timestamps. These records help match a deposit or withdrawal request without storing the private PIN used inside your wallet.

Device signals

When you sign in from a phone or desktop browser, we may record device and connection signals such as browser type, time and approximate network location. These markers help us investigate unusual access and are not a request for your device files.

Cookies

Cookies can remember sign-in preferences, security checks and your cookie choice. You can clear or block them in your browser settings, although removing required cookies may send you back through account verification before access continues.

Retention

We keep account, support and payment records only for the period needed to operate the service, resolve disputes, protect accounts or meet applicable duties. When a record no longer serves one of those purposes, we delete or anonymise it.

Your request

You may ask for access, correction or deletion where the request is allowed under applicable rules. Send the request through support with your account contact details; we may verify ownership before releasing, changing or removing a record.

Answers About Privacy Policy Access

These Privacy Policy answers cover the questions we hear most often from Indonesian customers before opening or using an account. They explain the records connected with sign-in, local wallet activity, cookies and support requests. If your situation is not listed, contact us through the account support route during the stated Jakarta-time service window.

The gucibet Privacy Policy covers account details, verification records, device signals, cookies, support messages and payment references. It explains why we use each category, how long selected records may remain and how you can request access, correction or deletion where applicable.

No. When you use DANA or QRIS, we receive the transaction reference and status needed to connect activity with your account. Your wallet PIN and private wallet login remain with the payment service, so do not send them to support.

Contact account support from the email or phone linked to your account and ask for a personal data access request. Include enough detail to locate the account, then complete any ownership check we request before records are released.

Yes. Send a correction request through the account support route and identify the field that needs changing. We may ask you to confirm an account step before making the change, particularly for phone, email or verification details.

The Privacy Policy covers cookies used for preferences, security checks and account continuity. You can clear or block cookies through your mobile browser settings. Required cookies may be needed again when you sign in, so a fresh verification step can appear.

We retain payment and support records for the period needed to process activity, investigate disputes, protect accounts or meet applicable duties. After that need ends, we delete or anonymise the record according to our retention process.

Yes. Privacy requests, account eligibility and access depend on local law. We handle requests through the account support route, explain any limit that applies and ask for ownership confirmation before sharing or changing personal account records.