Reference

bulan33 Privacy Policy: Your Data Path

Our Privacy Policy explains how bulan33 handles the account details, device signals and wallet records connected with your access to Live Roulette, Aviator and other lobby areas.

Account dataWallet recordsCookie choicesContact requests
bulan33 bulan33 Privacy Policy: Your Data Path
CONTACT THE TEAM

Privacy Questions, One Clear Route

A clear support route helps when your Privacy Policy question concerns a login, wallet reference or account record. Start from the support contact shown inside your account and include the phone number linked to your account, the relevant date and the request you want us to handle. Do not send a wallet PIN or full payment password. We use the account path to reduce confusion and direct privacy requests to the right check.

Team online

Account contact

Use the support contact inside your bulan33 account for a Privacy Policy request. Include your registered phone number and explain whether you need access, correction or deletion details.

Wallet reference

If your question concerns DANA, OVO, GoPay or QRIS, share the transaction reference and date only. We can check the status without asking you to disclose a wallet PIN.

Cashier path

For a privacy issue linked to bank transfer or virtual account records, use the account help route beside the cashier path. We will identify the relevant record before replying.

SIX DATA PRACTICES

Six Data Practices Behind Your Account

Our Privacy Policy is applied through ordinary account and security controls rather than broad promises.

Data collection

We collect account details you submit, phone verification results, device and session signals, and payment references needed to connect DANA, OVO, GoPay, QRIS or bank activity with your account.

Cookie control

Cookies and session storage help keep your login path working on mobile or desktop. You can adjust browser settings, although blocking essential storage may interrupt account access or require another sign-in.

Account security

Phone verification is checked before account access, while sign-in and account-change records help us investigate unusual activity. Never share your password, wallet PIN or verification code with a contact.

Payment records

We keep references for deposits, withdrawals and status checks rather than treating a wallet PIN as ordinary account data. A QRIS or virtual account reference lets support locate the correct transaction.

Retention periods

We retain records only for the period needed for account operation, security checks, dispute handling or legal duties. When a record is no longer needed, our process may remove or de-identify it.

Your requests

You can ask for a copy, correction or explanation through the account support contact. Where local law permits, you may also request deletion, subject to records we must keep for security or legal reasons.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the points most often raised before account access: what we collect, why wallet references appear, how cookies behave and where to send a request. If your situation involves a specific DANA receipt, QRIS reference or phone verification event, include that detail through the account support route so we can assess the correct record.

It covers account details, phone verification, device and session signals, cookies, payment references, security records and requests about access, correction or deletion. It applies to the account path and connected lobby access.

We use your phone number to create and identify the account, complete phone verification before access and help support locate the right record. Keep it current so account requests can be checked.

Yes. The policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS. We use those references to match account activity, while wallet PINs should remain private.

A mobile browser may create session and cookie records needed for login and lobby access. Browser settings can remove or block them, but essential storage changes may require another sign-in or interrupt access.

You can send an access request through the support contact inside your account. Include your registered phone number and the data category you want checked, such as verification or payment references.

You may request correction, and where local law permits, ask for deletion. We first verify the request, then explain any records that must remain for security, dispute handling or legal duties.

Use the support contact inside your account and describe the concern clearly. For a wallet matter, add the date and transaction reference from DANA, OVO, GoPay, QRIS or bank transfer, never your PIN.