Reference

gucibet Privacy Policy for Your Account

Our Privacy Policy explains how gucibet handles the details you provide when opening an account, confirming your phone, and using wallet options such as DANA or QRIS.

Clear data purposesWallet privacy detailsAccount contact steps
gucibet gucibet Privacy Policy for Your Account
PRIVACY CONTACT ROUTES

Contact Paths For Privacy Questions

A privacy question should reach a clear route, not disappear beside a payment status. Use the support form linked from your account area and include the phone number or account identifier connected with your request. If a DANA, GoPay, or QRIS reference is relevant, add only the transaction details needed for us to locate the record. Access depends on local law.

Team online

Account support form

Open the support form from your signed-in account and select the privacy subject. Include your request, account identifier, and the specific record you want us to check.

Payment record query

For DANA, OVO, GoPay, or QRIS questions, provide the payment reference and status shown to you. We use those details to trace the relevant record without asking for an unnecessary wallet password.

Correction request

Ask us to correct an account detail through the same support route. We may request a phone verification step before changing personal data or discussing protected account records.

SIX DATA CONTROLS

Six Controls Behind Our Data Handling

We apply the Privacy Policy at the points where data is created: account opening, phone verification, wallet status checks, mobile sessions, and support contact.

Purpose-based collection

We collect account and payment details for stated operational purposes, such as confirming your phone, matching a QRIS reference, protecting login, or responding to a privacy request.

Cookie choices

Cookies can preserve session settings and help detect suspicious sign-in behaviour. Your browser controls can limit cookies, although changing them may affect account access or saved preferences.

Account security

Phone verification supports account protection before sensitive changes. We may review device and session signals when access looks unusual, while keeping the check connected to account security.

Retention periods

We keep personal and payment records only for operational, security, dispute, and legal needs. When a record is no longer needed for those purposes, our process moves it toward deletion or restriction.

Correction requests

You can ask us to correct inaccurate account data through support. Give the affected field and account identifier, then complete any phone verification needed to prevent an unauthorised change.

Data access requests

You can ask what personal data we hold and why it is used. We may confirm your identity first, then respond with the relevant account, cookie, or payment record details.

Privacy Policy Answers For gucibet Accounts

These Privacy Policy answers address the account and wallet questions we expect from Indonesian customers before they open an account. They cover phone verification, cookies, payment references, device signals, correction requests, and local access. If your situation is not listed, use the support form and describe the exact record or processing purpose you want us to explain.

It covers personal data collected during account opening, phone verification, sign-in, wallet status checks, mobile sessions, cookies, and support contact. It also explains purposes, retention, security steps, and requests for access or correction.

We use transaction references and payment status details to match DANA or QRIS activity with your account. Do not send a wallet password through support; our process does not require that credential for a status query.

Your phone number helps create and protect the account, support phone verification, and connect a privacy request to the correct record. We may ask you to confirm it before discussing or changing protected details.

Cookies may remember session preferences and help identify unusual sign-in behaviour. You can manage them through your browser, but restricting required cookies may affect login continuity, saved settings, or account security checks.

Yes. Send a data access request through the account support form, identify the account, and state which records you want explained. We may verify your phone first before releasing protected account or payment details.

Use the support form and name the incorrect field, such as a phone number or account detail. We will assess the request and may require phone verification before applying a correction.

We retain payment references, account records, and related support details for operational, security, dispute, and legal needs. The period depends on the record and applicable requirements; you can ask us to explain its purpose.