Reference

Privacy Policy for Your gucibet Account

Our gucibet Privacy Policy explains how we handle the details connected with your account, including phone verification, device access, and payment choices such as DANA and QRIS.

Account and phone detailsDANA and QRIS recordsCookies and device accessData requestsLocal-law access
gucibet Privacy Policy for Your gucibet Account
DIRECT HELP

Ask About Your Account Data

A clear contact route matters when a phone check, wallet status, or data request needs attention.

Account data request Ask us to confirm which account details we hold, such as your registered phone…
Wallet record question If a DANA, OVO, GoPay, or QRIS transaction appears with the wrong status, share…
Correction and access You can contact us when a stored name, phone detail, or account record needs…
DATA PRACTICE

Account Data Across Your Devices

Our handling process follows the practical moments in your account journey: creating access, verifying a phone, opening the lobby on mobile, selecting a wallet, and contacting support.

What we collect

We may hold your account contact details, phone verification result, sign-in events, device and browser signals, support messages, and payment…

Cookies and devices

Cookies and similar device signals can keep a session connected, remember a language or display choice, and help us identify…

Account security

Phone verification and account checks help us distinguish your access from an unfamiliar sign-in.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we retain operational references such as status, time, and…

Retention period

We keep personal data only for the period needed for account operation, support investigation, security checks, and applicable legal duties.

Changes and contact

To request access, correction, deletion, or clarification, use our account support path and describe the specific record.

Privacy Policy Questions for gucibet

These answers address the privacy searches we expect before account access: what is collected, how wallet records are handled, what happens on a phone, and how to request a change. The Privacy Policy remains the controlling page for your circumstances. If your question depends on location or eligibility, the answer depends on local law.

The gucibet Privacy Policy covers account registration, phone verification, device and cookie signals, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains retention, security checks, data requests, and circumstances where local law affects access.

We do not ask you to send a DANA or QRIS password through support. Our records can include a payment method, reference, status, amount, and timestamp so we can match an account transaction. Keep wallet credentials inside the relevant payment service and never place them in a message.

Opening an account can involve contact details, a phone verification result, sign-in events, device signals, and information needed to respond to your support request. We collect these details to connect access and requests to the correct account, subject to the requirements that depend on local law.

Use the account support path and state whether you want access to, correction of, or clarification about a specific record. Include a safe account identifier, not a password or wallet code. We may verify your identity first, then explain the outcome, timing, or any local-law restriction.

Yes. The Privacy Policy covers device and browser signals used to keep a session connected, remember display choices, and investigate a mobile page problem. Your browser can manage cookies, but blocking some of them may affect login continuity, account preferences, or the way a page loads.

Retention depends on the type of record and the reason it is needed. Account, security, support, and payment references may be kept for different periods to operate access, trace a DANA or QRIS status, resolve a dispute, or meet applicable legal duties.

A request may need an identity check, may concern data we cannot safely disclose, or may be limited by a legal duty to retain a record. We explain the reason through the support path. Your eligibility and any access condition depends on local law.