Reference

bulan33 Privacy Policy For Your Account

Our bulan33 Privacy Policy explains how we handle the details connected to your account, from phone verification before access to wallet records for DANA and QRIS.

Clear data purposesWallet records explainedAccount request pathMobile and desktop access
bulan33 bulan33 Privacy Policy For Your Account
REQUEST HELP

Where To Ask About Your Data

A privacy question should not require a search through your account. Use our support chat for questions about the Privacy Policy, or follow the account-help path…

Privacy questions Open the support chat and state that your request concerns the Privacy Policy.
Wallet record check If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, use the cashier support…
Change request Ask us to correct an account detail or close a data request through support.
DATA HANDLING

Six Account Data Practices We Follow

Our approach is practical: collect what an account action needs, explain the reason, restrict internal access and keep a trace of important requests.

Account details

We use your submitted contact and account details to create access, respond to support and connect activity to the correct account. Phone verification helps us confirm that a request comes from you.

Payment references

For DANA, QRIS, bank transfer and virtual account activity, we keep transaction references and status details needed for reconciliation. Wallet passwords, card PINs and unrelated wallet content are not requested.

Cookies

Cookies and local storage can keep you signed in, preserve language or page settings and help identify unusual sessions. You can clear browser storage, though this may sign you out and reset preferences.

Security checks

We review sign-in signals such as device and session details when account activity appears unusual. A phone check or additional account question may be required before we disclose or change private details.

Retention

We keep account, support and payment records for the period needed for service operations, security checks or legal duties. When a record is no longer needed, we delete it or remove identifying links.

Your request

You can ask what personal details we hold, request a correction, question a processing purpose or ask about deletion. Contact support with your account identifier; we will verify ownership before responding.

Privacy Policy Questions For bulan33

These questions focus on the decisions you may face before opening or using an account from Indonesia. Each answer points to a practical data step, whether you are checking a wallet reference, changing a phone detail or asking how cookies affect a mobile session. If your situation is not listed, our support chat can route the request to the right account path.

The bulan33 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS and bank transfers.

We use phone verification before account access and selected account changes to confirm ownership. This helps prevent another person from viewing private details or changing wallet-related records through a simple request.

Yes. The Privacy Policy explains that we may receive QRIS, DANA, OVO and GoPay transaction references, amounts and status details needed to match a payment, but we do not ask for wallet passwords.

Use the support chat and identify the account detail that needs correction. Include the relevant date or reference when helpful, and complete our ownership check before we change the record.

Cookies or local storage can preserve your session and page settings on a mobile browser. Clearing them may sign you out, remove saved preferences and require the phone verification step again.

Yes. Send a data access request through support with your account identifier. We verify ownership first, then explain the categories held, their purpose and any records linked to account security.

We retain records while they support account operations, security checks or legal duties. After that period, we delete them or remove identifying links where practical, subject to applicable local requirements.