Reference

bro500 Privacy Policy For Your Account

Our Privacy Policy explains what account, device and wallet data we use when you open bro500, sign in and move between the lobby and cashier.

Account dataWallet recordsDevice accessPolicy requests
bro500 bro500 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Your Privacy Policy Rights

A clear contact route matters when you need to understand, correct or limit the use of account data. From your signed-in account, use the support path shown near account and cashier help, and include the email or phone linked to your profile. We can then match the request to the right record without asking you to send wallet credentials or a full payment password.

Team online

Account data request

Ask us what account details are held for your bro500 profile and why they are used. Include your registered phone number so we can verify the request before discussing records.

Wallet record query

For a DANA, OVO, GoPay or QRIS receipt question, send the payment reference shown in your account. Do not send your wallet PIN; we only need enough detail to locate the transaction record.

Access correction

If your phone, email or sign-in details are wrong, contact support through the account route before opening another profile. We will explain the verification step needed to update the record safely.

DATA PRACTICE

What We Do With Your Account Data

The practical side of our Privacy Policy is visible in the account flow: we separate sign-in checks from wallet references, use device signals to protect sessions and keep requests tied to the…

Account security

Phone verification helps us connect account access to the contact detail you supplied. We may record sign-in time, device markers and security events to identify a session that does not match your usual account pattern.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets our team match a cashier status with your account without needing your wallet PIN. Bank transfer and virtual account records are handled for the same matching purpose.

Cookies and sessions

Cookies and similar session tools can keep your sign-in state, remember basic preferences and help protect the path from mobile login to the lobby. You can control browser storage, though some account steps may then need repeating.

Game context

We may associate lobby activity with an account session so a request about Live Blackjack Turbo, Aviator Quick Arena or Esports PUBG Mobile can be investigated. This does not make unrelated game activity part of a payment request.

Retention period

We keep account, security and payment records only for as long as needed for the stated service purpose, dispute handling or a legal duty. When a record is no longer needed, our handling follows deletion or restriction procedures.

Change request

To request access, correction, deletion or a use explanation, contact us through the signed-in support path with your registered contact detail. We may ask for an account check before changing or disclosing personal records.

Privacy Policy Questions About bro500

These Privacy Policy answers focus on the account steps Indonesian customers ask about most: what is collected at sign-in, how wallet references are handled, how device sessions work and how to request a change. If your situation is not covered, use the account support route with your registered contact detail.

The bro500 Privacy Policy covers account details, phone verification, sign-in events, device session data, support requests and payment references. It explains how we use those records for account access, payment matching, security, legal duties and responses to your data requests.

Yes. Our Privacy Policy covers the DANA or QRIS reference needed to match a cashier status with your account. It may also cover OVO, GoPay, bank transfer and virtual account records, but we do not ask for your wallet PIN.

Phone verification helps us confirm that the person requesting account access is connected to the registered profile. Under the Privacy Policy, the verification event can be retained as an account security record and used when you ask to change contact details.

We may record technical session details such as device markers, browser settings, language choice, sign-in time and security events. The Privacy Policy uses these details to maintain a mobile session, detect unusual access and investigate an account request.

Use the support route shown inside your signed-in account and state whether you want access, correction, deletion or an explanation of use. Include your registered phone or email, while leaving out wallet PINs and full payment passwords.

We retain records for the period needed for the stated account, security, payment or support purpose, plus any dispute or legal duty that applies. The Privacy Policy allows you to ask why a category is retained and whether restriction is available.

Yes. Account access and eligibility depend on local law. Our Privacy Policy is intended for the account and data handling available where local law permits, including supported Indonesian access paths and the payment records linked to them.