Reference

c3bet Privacy Policy For Your Account

The c3bet Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use wallet options in Indonesia.

Clear data purposesWallet access contextAccount contact path
c3bet c3bet Privacy Policy For Your Account
CONTACT OUR TEAM

Privacy Help For Account Questions

A direct support request gives you a practical way to ask about the c3bet Privacy Policy without posting account details in a public channel.

Account data request Ask us to confirm which personal details are connected with your account and why…
Wallet privacy query If a DANA, OVO, GoPay or QRIS reference appears incorrectly, contact support with the…
Access and correction When you believe an account detail is outdated, ask us to review the relevant…
DATA HANDLING DETAILS

What We Protect And Retain

Privacy work is tied to everyday account actions rather than a separate screen. A login from a mobile browser can create device and security records, while a payment receipt may connect to…

Account security

Phone verification is used before account access so we can connect the sign-in attempt with the correct account. We may record login time, browser type, and device signals to identify unusual activity. Never share your password or wallet PIN through a support message.

Payment references

We retain the reference needed to match a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account event with your account. This does not require us to request your wallet password. If a receipt does not match, send the visible reference rather than private payment credentials.

Cookies and sessions

Cookies may keep a session active, remember a language or device choice, and show whether an account page loads correctly. You can manage cookies in your browser settings, although changing them may affect sign-in continuity or the way account privacy controls appear.

Mobile device signals

When you use the mobile path from login to the lobby, we may receive technical details such as browser version, operating system, and connection signals. These details help protect the account and diagnose page errors; they are not a request for contacts, photos, or wallet PINs.

Retention choices

We keep records only for as long as their account, support, security, dispute, or legal purpose requires. A request to remove data may be limited when a transaction record or security log must remain. We explain the applicable reason instead of silently ignoring your request.

Policy contact

For a copy, correction, access request, or question about this Privacy Policy, use our account support path and state the request clearly. We may ask for phone verification or another account check before sharing personal details, so the response reaches the right account holder.

Privacy Policy Answers For c3bet

These Privacy Policy answers focus on the account and payment questions you are most likely to have before opening access from Indonesia. We keep the process practical: identify the account step, protect private credentials, and use the support route for a request. If a question concerns access or eligibility, the answer depends on local law and the checks required for your account.

The c3bet Privacy Policy covers account details, phone verification, login and device records, cookies, support messages, and payment references. It explains why we use these details, how we protect them, how long records may remain, and how you can request access or correction.

Phone verification helps connect an account access request with the correct account holder and helps us identify unusual sign-in activity. It may be required before we share account details or change a contact field. We do not need your wallet PIN for this step.

Yes. The Privacy Policy covers payment references linked with DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account checks. We use the visible reference to match an account event or investigate a receipt, not to request your private wallet password.

You can contact support to ask which personal details are linked with your account and how they are used. We may verify your phone or account contact before responding. The scope and timing of a request depends on local law and any required security review.

Send a clear correction request through the account support path and identify the field that needs changing. Include only details needed to locate the account. We may complete a phone verification check first, then explain whether the change can be made under the Privacy Policy.

Retention depends on why a record exists. Account, support, device, and payment references may remain while needed for access, security, dispute handling, or a legal requirement. When you ask us to remove data, we explain any record that must remain and the reason.

Yes. Cookies can support an active session, remember a device or language choice, and show whether pages work correctly. You can manage them through browser settings on your phone or desktop. Disabling some cookies may affect sign-in continuity or privacy controls.