Reference

bro555 Privacy Policy For Your Account

bro555 Privacy Policy explains how we collect, use and protect the details connected to your account, device and wallet activity.

Clear data purposesWallet record contextAccount access requests
bro555 bro555 Privacy Policy For Your Account
CONTACT PATHS

Contact Us About Privacy Policy

A direct request helps us locate the correct account record without asking you to repeat the same details. Use the support path connected to your account or cashier area, and describe whether your request concerns access, correction, deletion, cookies or a wallet reference. We will check the request against account security steps before sharing or changing personal data.

Team online

Account data request

Ask us to confirm which account details we hold, such as your phone verification record or login history. Include the account identifier shown in your profile so we can check ownership before discussing private data.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, send the receipt detail and the affected account path. We can check whether the record is pending, matched or retained for a payment dispute without exposing another person’s data.

Cookie and device help

Tell us if a mobile browser keeps an old session or if a cookie setting affects account access. We can explain the relevant data use and point you to the browser setting needed to clear local records.

DATA PRACTICE

Check How bro555 Handles Your Data

Privacy choices work better when each record has a clear reason and a clear route for questions.

Collection purpose

We collect account details to create and secure your profile, complete phone verification and respond to requests. Device and session records help us identify unusual login behaviour, while page activity such as Balloon Mobile Play may be used to keep the requested session available.

Cookie controls

Cookies can remember a session, support security checks and preserve selected settings on a mobile browser. You can clear or block them through your device browser controls, although a blocked cookie may require another login before account access continues.

Account security

Before we reveal, change or remove private account data, we compare your request with the account details and phone verification already held. Never send a wallet password or a full payment credential through a support message.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may remain with the related account record so we can check a receipt, investigate a mismatch or resolve a cashier status question.

Retention timing

We retain personal and transaction records only while they serve account security, dispute handling, operational needs or a legal request. When a record no longer has one of those purposes, our process removes it or separates it from direct account identification.

Change requests

You can ask us to correct an inaccurate profile detail, explain a data use, or request removal where local law permits. Send the request through the account support path, and we will confirm identity before making a change.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers address the questions we expect before an Indonesian account is opened. They cover what we collect, how wallet records are handled, what happens on a phone, and how you can contact us about your own data.

The bro555 Privacy Policy covers account details, phone verification, login and device records, cookies, support messages, and payment references. It explains why we use each category, how we protect account access, how long records may remain, and how you can ask about or correct your data.

Yes. The policy includes references connected to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These details help us match a receipt or status to your account; they are handled as transaction records, not as permission to access your wallet credentials.

Use the account support path and ask for a copy or explanation of the data linked to your profile. Include the account identifier, but do not send a wallet password. We verify ownership first, then explain what can be provided where local law permits.

Yes, you can request a correction when a profile detail, phone record or account contact entry is inaccurate. Tell us which field is wrong and what should replace it. We compare the request with your account security details before applying a change.

The Privacy Policy explains that mobile cookies can preserve a session, support security checks and remember selected settings. You control them through your browser. Clearing cookies may end the current session and require phone verification or another login before your account opens again.

We keep payment references only while they support account security, receipt matching, dispute handling, operational needs or a legal request. The exact period can vary by record and local requirement. When the purpose ends, we remove the record or separate it from direct identification.

Send your question through the support route connected to your account or cashier area and identify the policy issue: access, correction, deletion, cookies or a payment reference. We review ownership first, explain the available next step, and apply local-law limits where relevant.