Reference

Privacy Policy for Your bulan89 Account

Our Privacy Policy explains what we collect when you open a bulan89 account, sign in from a mobile device, use DANA or QRIS, and contact our account help…

Account recordsWallet referencesDevice sessionsYour privacy choices
bulan89 Privacy Policy for Your bulan89 Account
CONTACT PATHS

Get Privacy Policy Help From Your Account

A clear contact path helps you act on this Privacy Policy without repeating your account history.

Account access If you cannot enter your account, tell us whether the problem concerns phone verification, a forgotten sign-in detail or a device session. We use the account path already on file rather than asking you to send sensitive credentials. This helps us separate an access request from a general privacy question.
Wallet records For a DANA, OVO, GoPay or QRIS privacy request, share the transaction reference and approximate date shown in your account. We can then check the linked status record without requesting your wallet password or PIN. Bank transfer and virtual account references can be handled through the same account-linked route.
Correction requests To ask us to correct an account detail, state which field is wrong and provide the replacement value through the support path connected to your account. We may ask for phone verification before making a change. That step protects your account from a request made by someone using your device.
HANDLING DETAILS

What We Do With Your Account Data

We keep this policy practical by linking each data use to an account task: access control, wallet matching, session protection or support.

Registration details

When you open an account, we collect the details needed to create and maintain that account, including your contact information and phone verification state. We use them to associate sign-in activity with the correct account and to respond to account-specific requests. Please keep those details accurate so our privacy checks reach you.

Device sessions

Our records may include device type, browser or app-session signals, approximate sign-in time and security events. These details help us spot an unusual session and explain why access changed between a mobile phone and desktop browser. Clearing browser data can end a session, but it does not erase account records.

Cookies and storage

We may use cookies or similar storage to keep a sign-in session, remember a language or region choice and protect pages from repeated invalid requests. You can manage browser storage through your device settings. Blocking some cookies may require you to verify your account again when returning to the lobby.

Payment references

DANA, OVO, GoPay and QRIS activity can produce a reference, amount status and timestamp connected to your account. Bank transfer and virtual account records can serve the same matching purpose. We use these references to reconcile a payment question, not to request your wallet password, card secret or banking login.

Retention controls

We retain records only for the period needed for account operation, security checks, dispute handling and legal duties that apply to the request. Retention can differ by record type, such as a support message, phone verification event or payment reference. Ask us which category applies when you request deletion or a retention explanation.

Account security

Phone verification before account access helps us distinguish you from someone attempting to use a saved browser or shared device. Never send a one-time code, password or wallet PIN in a support message. If you suspect an unwanted session, contact us through the account route and mention the device involved so we can assess the event.

Privacy Policy Answers for bulan89

These Privacy Policy answers cover the questions we expect you to ask before opening an account or requesting a data change. They explain account records, wallet references, device activity, cookies, retention and contact steps in plain terms. If your situation is specific, use the account-linked support route and tell us which part of this Privacy Policy you are asking about.

The bulan89 Privacy Policy covers account details, phone verification, sign-in and device-session records, cookies, support messages and payment references. It explains why we use those records, how they support account security and how you can request access, correction, deletion or clarification where local law permits.

We do not need your DANA, OVO, GoPay or QRIS wallet password or PIN to match a payment. Our records may contain a transaction reference, status and timestamp linked to your account. Never send a wallet secret in a support message, even when asking about a payment.

When you sign in on mobile, we may record device and session signals such as browser type, access time and security events. These records help us protect the account and explain a session change. Browser storage controls can affect sign-in persistence, while account records remain subject to this Privacy Policy.

Yes. Use the support route connected to your account and identify the field that needs correction, such as a contact detail or verification record. We may ask you to complete phone verification before changing it. This Privacy Policy request is handled with the minimum information needed to confirm ownership.

Retention depends on the record and the legal duties that apply. A support message, device security event, phone verification record and payment reference may have different periods. Ask us to identify the category involved and explain its retention basis. Where local law permits, you may also request deletion.

You can ask what personal data we hold by using the account-linked support path. Include the account phone number and describe the records you want, such as sign-in events, wallet references or support messages. We may verify your identity before responding so private account details are not disclosed to another person.

Contact us through the support route shown after account sign-in and label your request as a Privacy Policy question. If access is blocked, provide the account phone number and a short description without passwords or one-time codes. We will direct the request to the team handling account data, security or payment references.