Reference

Open bro333 Privacy Policy for Your Account

bro333 Privacy Policy explains what we collect when you create an account, verify your phone and move from login to the lobby on mobile or desktop.

Account dataWallet recordsCookie choicesPolicy access
bro333 Open bro333 Privacy Policy for Your Account
HELP PATH

Contact Us About Your Privacy Policy

A direct account route helps when you need an answer about the Privacy Policy rather than a general lobby question.

Account privacy request Use the account support path to ask what personal details we hold, why a…
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, tell us the…
Access and cookie help If a mobile browser keeps an old session or cookie choice, contact us through…
DATA PRACTICE

Explore Privacy Controls Beside Wallet Status

We keep this Privacy Policy practical: each data category connects to an account step, a payment check, a device session or a support request.

Account details

We use the details you enter during account creation and phone verification to establish the correct account record. Please keep them accurate, because matching identity details helps us handle later privacy requests.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us reconcile account activity. We keep the reference needed for status checks, receipts and questions about a specific transaction.

Cookies and sessions

Cookies can remember a sign-in session and your policy choices on the device you use. Clearing them may require another login, while your account records remain handled under the Privacy Policy.

Device signals

Browser, device and sign-in signals help us identify an unusual session or reconnect your mobile path to the lobby. They are considered for account protection and service troubleshooting, not as a reason to request your password.

Retention requests

We retain records for the period needed for account administration, payment reconciliation, security checks and legal duties. Ask through account support if you want us to explain a particular record's retention.

Changes to details

You can request correction or clarification of account-linked data through the same support route. We may confirm ownership first, then explain what can be changed and what must remain for records.

Browse Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the searches you may make before creating an account or checking a wallet record. We keep the route specific: account support, phone verification, cookie settings and payment references are the practical starting points. Read the relevant answer, then contact us through the signed-in support path when you need a record-level response.

It covers account details, phone verification, payment references, cookies, device signals, sign-in activity, retention and requests to correct or clarify data. It applies to handling connected with your account where local law permits.

Phone verification helps us connect the right person to the right account before access. It also gives us a matching account detail when you ask about stored data or request a correction.

Yes. We may retain DANA and QRIS references, along with OVO, GoPay, bank transfer or virtual account details, to match payment status, receipts and account activity during support checks.

Cookies can remember a session and the policy choices made on your browser. If you clear cookies, you may need to log in again, but clearing them does not itself remove account-linked records.

You can request a correction through the signed-in account support path. Include the verified phone or email attached to the account and describe the field; we may confirm ownership before making a change.

Retention depends on the purpose: account administration, payment reconciliation, security checks and legal duties may require different periods. Ask support about a named record, such as a QRIS receipt or sign-in event.

Use the account support route and provide the relevant account detail, device path or payment reference. We can then address your Privacy Policy question directly, subject to access where local law permits.