Reference

bulan77 Privacy Policy For Your Account

Your account, wallet and device data are handled under this Privacy Policy before you enter our casino, sports or game areas.

Account clarityWallet recordsCookie choicesLocal access
bulan77 bulan77 Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Beside Account Support

A clear contact path helps when you need a copy, correction or explanation of your personal data.

Account request Ask us to correct account details after phone verification. Include the relevant account identifier so we can match your Privacy Policy request without exposing another person’s records.
Wallet record For DANA, OVO, GoPay or QRIS data questions, send the payment reference and date through our support route. We use those details to locate the correct record.
Access concern If a login alert or device change looks unfamiliar, contact support from your account path. We can review the security event and explain what data was involved.
HANDLING DETAILS

Six Ways We Handle Privacy

Our handling steps connect the Privacy Policy to actions you can recognise in your account. We separate identity details from payment references where practical, use cookies for session and preference functions, and…

Data collection

We collect account details you submit, phone verification results, support messages and transaction references. A visit may also create browser, device and login records used for session control and security checks.

Cookie controls

Cookies can keep a session active, remember a language choice or help us detect unusual access. You can manage browser cookie settings, though disabling essential cookies may affect account entry.

Account security

Phone verification is checked before account access, while login and device events may be recorded for protection. Do not share your password or verification code with anyone contacting you.

Payment separation

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to match payment status and account requests. We do not use a wallet reference for unrelated purposes.

Retention period

We keep personal data while it supports an active account, a support request, security checks or a legal duty. When the reason ends, records are deleted, restricted or anonymised where appropriate.

Change requests

You can ask for access, correction, restriction or deletion where applicable. Send the request through support with your account identifier; we may verify ownership before making a change.

Privacy Policy Questions About bulan77

These Privacy Policy answers focus on the account actions you are most likely to take before using the site. We keep the wording practical: what data is created, which payment references may appear, how device records work and how to contact us. If your situation is not listed, use the support route with the account step or payment reference involved.

The Privacy Policy explains how we collect, use, protect and retain account, device, cookie, support and payment data connected with your bulan77 account, where local law permits.

Yes. It covers payment references, status, date and related account details for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We record the account details you submit and the result of the phone verification step. Login, device and security events may also be retained to protect account access.

You can contact our support route with your account identifier and request a copy where applicable. We may confirm account ownership before releasing personal data.

Send the requested correction through support and identify the account field or payment record involved. We check the request against your account before updating the relevant data.

Cookies can support login sessions, language preferences and security checks on a mobile browser. Your browser settings can restrict them, although essential account functions may then change.

We review data after its account, support, security or legal purpose ends. Depending on the record, we may delete, restrict or anonymise it rather than retain it indefinitely.