Reference

Privacy Policy for Your brovegas Account

Your account details, wallet records and device activity are handled for clear access and safer account checks.

Account dataWallet recordsCookie choicesPrivacy requests
brovegas Privacy Policy for Your brovegas Account
PRIVACY SUPPORT

Get Privacy Help Through Account Support

A direct support route helps you resolve a data question without sending sensitive details through an unsuitable channel. Start from the account support area and describe whether your request concerns login data, a wallet reference, a cookie choice or a correction. We may ask for your registered phone number and a payment receipt so we can identify the right account, while you should never send a wallet PIN or password. If you are in Yogyakarta or elsewhere in Indonesia, the same privacy request path applies where local law permits.

Team online

Account support chat

Use the account support chat for questions about your Privacy Policy rights, phone verification records or a device entry you do not recognise. We will ask for account identifiers only when needed to locate the request and will not ask you to disclose a wallet PIN or password.

Privacy request form

Send a correction, access or deletion request through the support request form linked from your account area. Include the registered phone number and a short description of the data issue; for DANA, OVO or QRIS matters, add the transaction reference rather than private wallet credentials.

Receipt status check

When a privacy question involves a payment record, attach the relevant receipt or reference so we can separate your account data from the payment provider's records. This helps us explain what brovegas stores, what a provider stores, and which party can amend a transaction detail.

DATA HANDLING

Your Data Path From Login To Wallet

Our privacy process follows the same account steps you see when signing in, verifying a phone and checking a wallet status.

Account collection

When you open an account, we collect details such as your registered phone number and verification result. We use these details to identify your account, send account-related replies and complete access checks, rather than to request your DANA, OVO or GoPay password.

Device signals

A mobile browser or desktop session can provide device type, browser version, connection details and security events. We use these signals to spot unusual login behaviour and investigate access questions; they also help support distinguish a new device from a repeated session.

Cookie controls

Necessary cookies support login sessions, language settings and security checks, while optional cookies may help us understand page use. Your browser settings can remove or restrict them. Removing necessary cookies may sign you out or prevent parts of the account area from loading.

Wallet references

For DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity, we may retain a reference, amount, status and time to reconcile your account. We do not need your wallet password to match that record, and payment providers may hold separate data under their own terms.

Retention choices

We retain account, security and payment references only as long as needed for the stated purpose, dispute handling, security checks or legal duties. If you ask for deletion, we assess which records can be removed and which must remain for a defined legal or operational reason.

Request changes

You can ask to access, correct or delete eligible personal data through account support. We may verify ownership using your registered phone and a recent account detail before acting, so a third party cannot change your records by sending an unsupported request.

Privacy Policy Questions About brovegas

These answers address the searches we hear most often about the brovegas Privacy Policy. They cover account creation, local wallet records, device activity, cookies, data requests and access conditions. If your situation involves a specific receipt or login event, use the support route above so we can examine the relevant record instead of giving a general reply.

It explains how we collect, use, secure and retain account, device, cookie and payment-reference data. It also describes your options to request access, correction or deletion. The policy applies to account activity such as phone verification and wallet status checks where local law permits.

We may collect your registered phone number, verification result, account settings, login events and device signals. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may also keep payment references needed to match account activity.

No. We use transaction references, status details and related account records to reconcile activity, but you should never send a wallet PIN or password to support. DANA, QRIS and other payment providers may hold separate records under their own privacy terms.

Contact us through the account support chat or privacy request form and state whether you want access or a correction. Include your registered phone number and the relevant record, such as a device event or payment reference. We may verify account ownership first.

You can submit a deletion request through account support. We assess each record separately because some account, security or payment references may need to remain for dispute handling, fraud checks or legal duties. We will explain the result and any remaining retention reason.

Necessary cookies support login sessions, security checks and selected settings, while optional cookies may help us understand page use. You can restrict cookies in your browser. If necessary cookies are removed, sign-in or parts of the account area may stop working.

You can read this Privacy Policy and send a data request from Indonesia where local law permits. Access or eligibility depends on local law. If a login, phone verification or wallet record needs clarification, contact support with your registered account details.