Reference

Privacy Policy For Your bulan89 Account

Our Privacy Policy shows how bulan89 handles the account details, device signals and payment records connected with your access.

Account dataWallet recordsCookie choicesContact requests
bulan89 Privacy Policy For Your bulan89 Account
CONTACT ROUTES

Get Privacy Policy Help Without Guesswork

A clear contact path matters when a Privacy Policy question affects your account or wallet record. We ask you to contact the support route shown inside your account, include the email or phone detail tied to your profile, and describe the specific request. That helps us locate the right record without asking you to send a full payment credential. From Denpasar or elsewhere in Indonesia, use the same account support path for access, correction and deletion questions where local law permits.

Team online

Account privacy request

Use the support path inside your bulan89 account and state whether you want a copy, correction or deletion of personal data. Include the account identifier used during phone verification so we can distinguish your request from another profile.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference and date through account support. We use those details to locate the relevant payment record without requesting your wallet password or full security code.

Login privacy concern

When a mobile-browser login creates an unfamiliar device entry, tell us the sign-in time and device type through the account support route. We can check the event, explain the data involved and guide the next account-security step.

HANDLING DETAILS

How Privacy Works Inside bulan89

We apply this Privacy Policy to the practical moments around your account: opening access, checking a wallet status, moving between casino and sports pages, and asking support to correct a record.

Account data

When you open an account, we handle the contact details and phone-verification result needed to identify your profile. We do not ask you to place wallet passwords in support messages. Access depends on local law and the details needed for that permitted account path.

Device signals

A sign-in from your phone or desktop browser can create technical records such as browser type, session time and security events. These signals help us investigate an unfamiliar login or a stalled account step, rather than describing your personal identity by themselves.

Cookies

Cookies and similar browser storage can keep a session connected and remember limited choices. You can manage cookie settings in your browser, although turning them off may affect the account path from login to the lobby and may require another sign-in.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can be linked to an account activity record. We use the reference, status and time to reconcile a payment question, while the wallet provider remains responsible for its own account data.

Account security

We use phone verification, sign-in event checks and restricted account access to help protect profile records. If you see an unfamiliar device or cashier status, contact support through your account route and avoid sharing a password, PIN or complete wallet credential.

Retention requests

We retain account, payment and support records only for stated account, security, dispute or legal purposes, then remove or anonymise them when no longer needed. You can ask what remains, request a correction or ask about deletion where local law permits.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we expect from someone deciding whether to open a bulan89 account in Indonesia. They cover the first account step, mobile access, wallet references, cookies, security checks and requests to change stored data. If your situation is not listed, use the support route inside your account and describe the exact record or event you want us to check.

It covers data linked to your account, phone verification, sign-ins, mobile-browser activity, cookies, support messages and payment references. It explains why we handle each category, how account security uses technical signals, and how you can ask about, correct or delete data where local law permits.

We may collect the contact details you submit, the phone-verification result, login events, device and browser signals, and records needed to connect account activity with a payment status. The Privacy Policy explains each purpose, and you can ask support to confirm the data linked to your profile.

Yes. It covers the payment references, status details and timestamps that may accompany DANA, OVO, GoPay or QRIS activity, along with bank transfer and virtual account references. We use these details to reconcile your account record, while each wallet or bank handles its own separate data.

Send a request through the support route inside your account, identify the phone or email connected to your profile, and state whether you want a copy or correction. We may need to verify account ownership before responding, so do not include a password or complete wallet credential.

Yes. The Privacy Policy applies when you sign in through a phone or desktop browser. We may record browser type, session time, cookies and security events so the account path remains connected. Your browser settings control many cookies, and access remains where local law permits.

We use phone verification, restricted account access and checks on sign-in events to help protect profile and payment records. We do not need your wallet password in a support message. If a device or cashier event looks unfamiliar, contact us through the account support route.

We keep account, payment and support records for the account, security, dispute or legal purpose that requires them, then remove or anonymise them when they are no longer needed. The period can depend on the record and local requirements; ask support what applies to your request.