Reference

Privacy Policy for Your browin Account

browin Privacy Policy explains how we handle the information connected to your account, wallet status and lobby access.

Account clarityWallet checksCookie choicesAccess requests
browin Privacy Policy for Your browin Account
CONTACT ROUTES

Ask About Your Privacy Policy

A clear contact path helps you act on the Privacy Policy without guessing which account screen to use. Start with the support route available inside your browin account when you need a data question checked. Include the phone number tied to the account and the subject of your request, but do not send a wallet PIN or full security credential. Our team can then identify the relevant account step, payment receipt or device session and explain what can happen next.

Team online

Data access

Ask us for the account information connected to your phone verification and sign-in record. Use the support path shown in your account, describe the request as a Privacy Policy matter, and we will explain the identity checks needed before sharing details.

Correction request

If your contact detail or wallet status is inaccurate, tell us which field needs attention and why. We may ask you to confirm the account step or provide a transaction reference, while keeping your DANA, OVO, GoPay or QRIS security code private.

Privacy contact

For a broader question about cookies, retention or account security, use the same account support route and mark the message for privacy assistance. Include your preferred reply path and enough context for us to locate the correct record without sending sensitive credentials.

HANDLING DETAILS

What We Do With Account Data

The Privacy Policy is applied to practical account tasks rather than kept as a separate statement.

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification. We use that information to connect your sign-in with the correct account area, not to ask you to repeat the same identity step across each lobby page.

Wallet status

A selected DANA, OVO, GoPay or QRIS route can create payment-status information linked to your account. Bank transfer and virtual account records may include a reference from BCA, BRI, Mandiri or BNI so we can investigate the matching cashier event.

Device sessions

We may record device and browser signals that help identify a login session, detect an unusual access attempt or keep the mobile path connected to the lobby. These signals support account security; they do not replace the phone verification step used for access.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a page is loading correctly. Your browser controls can limit or remove them, although changing cookie settings may affect sign-in continuity or the display of the cashier path.

Retention

We retain account, payment and support records only for the period needed for the stated service, security, dispute or legal purpose. The period can differ by record type. You can ask us which category applies when you submit a Privacy Policy request.

Changes and contact

You can ask to access, correct or remove eligible information by contacting support from the account route shown to you. We may verify ownership before acting, and we will explain any restriction when a record must remain available for a legal or transaction reason.

Privacy Policy Answers for browin

These Privacy Policy answers focus on the account questions you may have before opening the lobby or checking a wallet status. We explain the practical route for access, correction, cookies, security and contact so you can decide what information to provide. If your question concerns eligibility in Indonesia, the relevant access decision depends on local law, while this page explains how we handle the information connected with that decision.

The browin Privacy Policy covers information linked to account creation, phone verification, sign-in, device sessions, wallet status, payment references, cookies and support requests. It explains why we use those records, how security checks work and how you can ask about access, correction, retention or removal.

We may collect the details required to create your account, verify your phone and connect you with the correct lobby and cashier path. Depending on your activity, records can include device signals, selected DANA, OVO, GoPay or QRIS status, and a bank or virtual account reference.

Yes, you can send a data-access request through the support route available inside your account. Describe the Privacy Policy request and identify the phone number or account record involved. We may confirm ownership first, then explain which information can be provided and in what format.

Contact support from your account path and name the field that needs correction, such as a contact detail or wallet status. We may ask for an account step or transaction reference to locate the record. Never include a wallet PIN, password or full security credential in the message.

Yes. The Privacy Policy explains that cookies and related device signals may keep a session active, remember settings or show whether a page loads correctly. You can manage cookies in your browser. Restricting them may interrupt sign-in continuity or change how the cashier and lobby pages appear.

We use account checks such as phone verification and may assess device-session signals when access appears unusual. Support will not need your wallet PIN or password to begin a Privacy Policy request. Before discussing personal records, we may ask you to confirm that you own the account.

Use the privacy assistance route shown through account support and state whether you want a change, copy or deletion request. Include enough detail to identify the record, without sending sensitive credentials. We will explain the next check and any reason a transaction or legal record must remain available.