Reference

Privacy Policy for Your bk2000 Account

Our Privacy Policy explains how we collect, use and protect details connected with your bk2000 account, including phone verification, device access and wallet activity.

Account clarityWallet recordsDevice controlsCookie choices
Explore Our Lobby Read FAQ
bk2000 Privacy Policy for Your bk2000 Account
CONTACT YOUR WAY

Get Privacy Policy Help Near Account Support

A direct support route helps you ask about personal data without explaining the same issue repeatedly. From your signed-in account, use the support contact path and include the phone number linked to your account, the subject of your request and any relevant wallet reference. We may ask for account details to confirm that we are speaking with the account holder. Do not send a wallet PIN, password or full security code. If you are in Denpasar or elsewhere in Indonesia, the same request path applies where local law permits.

Team online

Account contact

Use the signed-in support path for questions about your Privacy Policy rights, phone verification record or account details. Adding your registered phone number helps us locate the correct account without asking you to repeat unrelated payment or game information.

Wallet status

If a DANA, OVO, GoPay or QRIS reference appears connected to the wrong account activity, send the transaction reference through support. We use that reference to check the record while keeping your PIN and password out of the request.

Policy request

For a copy, correction or deletion request, state the exact action you want and the phone number attached to your account. We may request additional verification before discussing personal records or changing details linked with account access.

DATA HANDLING

What You Can Check In Our Privacy Policy

The Privacy Policy is designed to give you practical answers about the data trail created by an account, rather than broad statements about the lobby.

Account records

We may hold your phone number, account identifiers, verification result and sign-in events so we can provide account access and respond to account requests. These records also help us distinguish an authorised session from an unusual attempt.

Payment matching

A wallet or bank reference can show that a payment request belongs to your account, but it does not replace your password or PIN. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI details are handled for matching and status checks.

Cookies and sessions

Cookies and similar session tools can remember sign-in state, security preferences and page choices. If you clear them, you may need to verify your account again before reaching the lobby or checking a wallet status.

Device security

We can record device and browser signals, such as operating system, browser type and session time, to detect account misuse. Aviator Mobile Play may open through a mobile browser path, but the same account security checks still apply.

Retention decisions

We retain records only for the period needed for account operation, security checks, dispute handling or legal duties. A request to remove data may be limited where keeping a transaction or verification record is required.

Your requests

You can ask what personal data we hold, request a correction or ask about deletion through support. We verify the requester first, explain any limits, and record the response so the same request can be handled consistently.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening an account or connecting a local wallet. They explain the data needed for access, the records created by payment checks and the steps for asking us to act on your personal details. If your situation is not covered, use the account support path and mention that your request concerns the Privacy Policy.

It covers account details, phone verification, sign-in events, device signals, cookies, wallet references and support requests. It also explains why we use those records, how we protect account access, when retention may apply and how you can request access or changes.

Those payment rails can create references and status results that need to be matched with your account. We use that payment data to check whether a request belongs to you and to respond to a wallet question, without asking for your private PIN.

We may collect the phone number used for account verification and technical details from the device or browser used to sign in. These records support account recovery, session security and unusual-activity checks, including when you move between phone and desktop.

Send a request through the signed-in support path and identify the phone number linked with your account. Say whether you want access, correction or deletion. We verify your identity first, then explain what can be supplied or what legal retention limits apply.

Yes, you can request a correction through support. Include the detail you believe is wrong and the correct replacement, but do not send your password, wallet PIN or full security code. We may ask for account verification before changing access-related records.

We keep data for the time needed to operate your account, protect sessions, resolve payment questions, handle disputes or meet legal duties. When a record is no longer needed for those purposes, our handling process can remove or de-identify it.

Open the account menu in your mobile browser and select the policy link. On desktop, use the policy link in the footer. If the page does not load, contact support from the account path and mention your device and browser.

Related Pages

bk2000 Indonesia Live Roulette Prestige bk2000 Casino Access guide About Us