Reference

bibit168 Privacy Policy For Clear Account Choices

Our bibit168 Privacy Policy explains what we collect when you open an account, verify your phone, browse Live Roulette Wheel or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
bibit168 bibit168 Privacy Policy For Clear Account Choices
CONTACT ROUTES

Three Ways To Ask About Your Data

A clear contact route matters when a wallet record or sign-in detail needs attention. We ask you to use the account help path and include the phone number or payment reference connected to your request. That lets us locate the relevant record without asking you to send unrelated personal details. We handle Privacy Policy questions about access, correction, cookies and retention through the same support path, subject to identity checks and where local law permits.

Team online

Account help

Use the account help route when you want to ask what personal details are linked to your bibit168 account. Include your verified phone number and request type; we may ask for an additional account check before discussing private records.

Wallet record

For a DANA, OVO, GoPay or QRIS question, send the payment reference and approximate date through support. We use those details to locate the relevant wallet event, while avoiding requests for your full wallet password or unrelated account data.

Privacy request

To request correction, access or removal where local law permits, state the exact change you want and the phone number on your account. We confirm that you control the account before responding, which helps keep another person from receiving your data.

DATA PRACTICES

How bibit168 Handles Account Privacy

Our handling process follows the account journey rather than collecting every detail by default.

Account collection

When you open an account, we collect the details needed for account access and phone verification.

Cookie controls

Necessary cookies can keep your signed-in session and selected account path working. Other cookie settings may depend on your browser.

Device signals

We may record browser type, operating system, approximate access time and security events when you sign in.

Account security

Keep your password private and complete phone verification only through your own account path.

Record retention

We retain account, support and payment-reference records only as long as needed for the stated service, security checks or legal…

Change requests

You may ask us to correct inaccurate account details, explain the records we hold or request removal where local law…

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before account access. They explain how bibit168 connects account data, device activity and local wallet references, plus the steps you can take when something needs correction. If your question concerns eligibility or access, the applicable position depends on local law and the account checks required for your request.

The bibit168 Privacy Policy covers details you submit for account creation, phone verification and support. It also covers sign-in events, device signals and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect account access to the person completing the account step and reduces confusion when support checks a sign-in. We use the result for account administration and security handling, subject to the rules that apply where local law permits.

We use a submitted DANA or QRIS reference to match a wallet event with the correct account and respond to a status question. We do not need your wallet password for that check. Payment records remain subject to operational and legal retention needs.

Yes. Use the account help route, identify the field that is wrong and provide the phone number attached to your account. We verify account control before changing details, and some requests may be limited by legal, security or record-keeping duties.

Send an access request through support with your account phone number and a clear description of the records you want explained. We may ask for another identity check, then respond with the available account details where local law permits.

Yes. The Privacy Policy covers necessary cookies and similar browser signals used for sessions, account paths and security checks. You can clear or restrict cookies in your mobile browser, but doing so may sign you out or affect pages that require an active session.

We keep records for the period needed to operate the account, investigate security events, answer support requests or meet applicable legal duties. After that period, we remove or restrict access where appropriate. You can ask support about a specific record category.