Reference

bekasibet Privacy Policy For Your Account

Your account data stays connected to clear choices when you open Lightning Roulette, Rocket Crash or another lobby title through bekasibet.

Account dataWallet recordsCookie choicesSupport requests
bekasibet bekasibet Privacy Policy For Your Account
CONTACT PATHS

Reach Support About Privacy Requests

A clear contact path helps you ask about account data without explaining the same issue twice. Use the support channel shown inside your bekasibet account for a privacy request, and include the email or phone detail attached to the account so we can locate the correct record. If you are in Bandung or elsewhere in Indonesia, the same account-based route applies where local law permits.

Team online

Account data request

Ask for a copy of the personal data connected with your account through the available support channel. We may ask you to confirm an account step before releasing details.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, send the transaction date and account identifier. We use those details to trace the relevant wallet record without requesting your wallet password.

Access or correction

Tell us which detail needs correction or which policy question you have. Our support route can review login, cookie and account-record concerns while access depends on local law.

HANDLING DETAILS

Check How We Handle Account Data

Our privacy process follows the account journey rather than treating every record alike. Login details, device activity, wallet references and support messages serve different purposes, so we keep their use tied to…

Account security

We use account identifiers, login records and verification steps to protect access. Never send us your password or wallet PIN; if a sign-in looks unusual, contact support through the account path.

Device behaviour

Your phone or computer may store a session cookie so you remain signed in while moving between account pages. Clearing browser storage can end that session and prompt another account check.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference data in your account record. We use it to match status and answer payment-related privacy requests.

Retention period

We keep personal data only for the account, support, security or legal purpose that requires it. When a record is no longer needed, our retention process removes or separates it where applicable.

Your requests

Where local law permits, you can ask to access, correct or delete personal data. Include the account contact detail and a clear description so we can assess the request accurately.

Policy contact

Privacy questions belong in the support channel available from your account. We may verify account ownership before discussing records, helping prevent disclosure to the wrong person.

Find Privacy Policy Answers For bekasibet

These answers address the searches we hear most often about the bekasibet Privacy Policy. They focus on account data, wallet references, cookies, access requests and contact steps, so you can understand the policy before deciding whether to open an account.

It covers personal data used for account access, verification, device sessions, wallet references, support messages, cookies, retention and requests to access, correct or delete records.

We may collect contact details, login activity, verification results, device signals, account actions and support correspondence. We use these details for stated account, security and service purposes.

Yes. The policy explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may appear in your account record, while each provider manages its own data.

Use the support channel shown inside your account and identify the email or phone detail attached to it. We may complete an ownership check before sharing records.

Where local law permits, you can request correction or deletion through account support. State the record concerned and provide your account contact detail so we can assess the request.

Cookies can preserve a sign-in session and help us understand page performance. You can clear or restrict them in your browser, though some account pages may require another sign-in.

Retention depends on the account, support, security or legal purpose for each record. We remove or separate data when that purpose no longer requires it, where applicable.