Reference

Open i3bet Privacy Policy Before Account Access

i3bet Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification, device signals and wallet activity.

Account dataCookie choicesWallet checksContact path
Explore Our Lobby Read FAQ
i3bet Open i3bet Privacy Policy Before Account Access
PRIVACY CONTACT

Switch To Help When Privacy Questions Stall

A clear contact route matters when you cannot tell why a phone check, cookie choice or wallet record appears in your account.

Account access If you need help reaching the Privacy Policy contact route, start from the account…
Wallet records For a privacy question about DANA, OVO, GoPay or QRIS activity, share the date…
Request changes When you ask us to correct, export or remove eligible account data, include the…
DATA PRACTICE

Browse How We Handle Your Account Data

Privacy work follows the same account path you use to reach the lobby: we identify the account, check the request and limit access to the records needed for the task.

Phone verification

Before account access is completed, we may use your phone verification details to connect the request with the correct account. This helps us avoid changing personal records for the wrong person; keep your one-time code private and enter it only on the account path.

Device signals

When you sign in from a mobile browser, we can record device and browser signals linked to security checks. These signals help us compare unusual access patterns with your normal account activity; they are handled as part of account protection rather than as a public profile.

Cookie choices

Cookies can remember session settings and choices made while you move between account pages and the lobby. Your browser controls whether some cookies remain, but changing that setting may affect sign-in continuity. Our Privacy Policy explains the purpose of these small files in plain terms.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, status and timestamp in your account history. Bank transfer and virtual account records follow the same matching need. We use these references to check account activity without requesting your wallet PIN or banking password.

Retention checks

We keep personal data while it supports account security, payment reconciliation, support handling or a legal requirement. When a record no longer serves one of those purposes, our retention process can remove or separate it. A request to explain retention can be sent through the account support route.

Request ownership

To protect your account, we may confirm ownership before providing a copy, correcting a detail or processing an eligible removal request. Use the registered phone number and describe the record involved. Where local law permits, we will explain the next step and any reason a request cannot be completed.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers address the account questions we expect you to ask before opening access. They cover the data collected during phone verification, cookies on a mobile browser, wallet references and the steps for requesting a copy or correction. If your situation is different, use the support path inside your account and include only the details needed to identify the issue.

The i3bet Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains why we use those details for access, security, reconciliation and support, plus how you can ask about correction, retention or eligible removal where local law permits.

We use phone verification to connect an account request with the correct account and to reduce mistaken access. The code should be entered only through the account page and never sent to support. The Privacy Policy describes this use as an account-security step, not a request for your wallet PIN.

Yes. The Privacy Policy explains that cookies can remember session settings and choices while you move through account pages on a phone or desktop browser. Your browser lets you change cookie settings, although blocking some cookies may interrupt sign-in continuity or remove saved page preferences.

When you use DANA or QRIS, the account may store a transaction reference, status and timestamp so we can match activity and answer a payment question. We do not need your wallet PIN for that check. OVO, GoPay, bank transfer and virtual account records follow the same privacy purpose.

Where local law permits, you can ask for an eligible copy or correction through the account support route. Include your registered phone number, identify the record and state the requested change. We may confirm ownership first, and we will explain the next step or any applicable restriction.

We retain personal data while it is needed for account security, payment reconciliation, support handling or a legal requirement. The exact period can depend on the record and local rules. You can ask support about retention for a particular account detail, payment reference or verification record.

Start from the support link shown after account sign-in and describe the Privacy Policy issue without including a password or one-time code. For a wallet record, provide its date and displayed status. Access to account details and request handling depends on local law and ownership checks.

Related Pages

i3bet Indonesia i3bet Casino New Member Offer Account information About Us