Reference

bombo606 Privacy Policy for Your Account

Our Privacy Policy shows what we collect when you open an account, verify your phone and move between the lobby and wallet screen.

Account dataWallet contextCookie choicesAccess depends on local law
bombo606 bombo606 Privacy Policy for Your Account
ASK ABOUT PRIVACY

Get Help With Account Data Requests

A clear support route matters when a phone check, wallet status or privacy request needs attention.

Account access If phone verification blocks access, contact support through your account path and include the registered phone number in masked form so we can locate the relevant privacy record.
Wallet status For a DANA, OVO, GoPay or QRIS status question, share the date, rail and receipt reference only; never send your wallet PIN, password or complete credential.
Data change request Ask us to correct account details, explain a retained record or clarify cookie use through the support route. We may request verification before changing information.
HOW WE HANDLE RECORDS

Privacy Controls Around Your bombo606 Account

The practical side of our Privacy Policy follows the account journey: we collect what helps you sign in, verify a phone, display wallet status and answer a support request.

Account details

We may use your registration details, phone verification result and account reference to create access, identify the right record and respond to a request about your data.

Device signals

Browser type, device information and login activity can help us detect an unusual access attempt. These signals support account protection and are handled within the policy purposes.

Cookies

Cookies can remember session choices and help us understand essential page use. Your browser settings provide a way to limit cookies, although some account paths may then work differently.

Wallet records

A selected rail such as QRIS or bank transfer may be linked with status, receipt and account references. We use that connection to reconcile your request and answer payment queries.

Retention

We keep records for account operation, dispute handling, security checks or applicable obligations, then remove or reduce them when they are no longer needed for those purposes.

Your request

You can ask for access, correction or clarification through account support. We verify the requester first and explain any limit where local law permits a different result.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often before account opening. We keep the wording tied to real account steps, mobile access and local wallet records, so you can decide what to share and where to ask for help. If your situation is unusual, use the support path rather than sending sensitive credentials in a message.

It covers account details, phone verification, device and browser signals, cookies, wallet status, transaction references, retention and requests to access or correct your personal data.

We use the verification result to confirm the account access step and connect a support request with the right account. We do not need your password or wallet PIN for this check.

Yes. It explains how a selected rail, account reference, status and receipt details may be handled when you use DANA, OVO, GoPay or QRIS.

The policy may cover browser type, device details and login activity used to maintain a session, identify unusual access and connect a privacy request with your account.

Use the support link inside your account and ask for access or correction. We may verify your identity, and the outcome depends on local law and the record involved.

We retain records for account operation, payment reconciliation, dispute handling, security checks or applicable obligations. When a record is no longer needed, we remove or reduce it.

Yes. Ask through account support or adjust your browser settings. Limiting cookies may change session behaviour, and we can explain which page function relates to the cookie question.