Reference

Your Privacy Policy for Indonesia Accounts

The bro jp Privacy Policy puts phone verification, wallet records and device data in one clear place, so you can understand what we collect before you open an…

Phone verification dataDANA and QRIS recordsCookie controlsPrivacy request path
bro jp Your Privacy Policy for Indonesia Accounts
REQUEST ROUTES

Three Paths for Privacy Requests

A clear request route matters when account data or a wallet record looks wrong.

Account Data Request Use the account-help path when you need access to, correction of or deletion consideration…
Payment Record Query Open help beside the cashier when a DANA, OVO, GoPay or QRIS record needs…
Cookie and Device Query Use the privacy request path for questions about cookies, browser identifiers or remembered sessions.
SIX DATA CONTROLS

Six Controls Behind Your Account Data

Six practical controls shape how we apply this policy from account opening to a later privacy request.

Purpose-Based Collection

We collect account data that supports phone verification, session access, wallet matching, security checks and service requests. Activity linked to Live Casino, zeuis138 or Fish Hunter may be recorded when needed to preserve a session or investigate a technical fault.

Cookie Choices

Cookies and similar browser records can keep your session active, remember permitted preferences and show whether account pages function correctly. You can adjust browser storage controls, although removing required session records may sign you out or reset remembered choices.

Account Security

Phone verification helps separate your account from an unauthorised access attempt. We also use session and device signals to detect unusual account behaviour; you should keep passwords and one-time codes private and close shared-device sessions after use.

Payment Record Access

Cashier access is limited to the records needed for receipt matching, status checks and payment support. A QRIS reference or DANA status can be linked to your account transaction without requiring us to ask for your full wallet credentials.

Retention Decisions

We keep records while they serve account, security, transaction, dispute or legal purposes. Retention periods can differ by record type, and a deletion request may not remove material that must remain for payment reconciliation, fraud prevention or applicable legal duties.

Correction and Deletion

You may ask us to correct inaccurate profile data or consider deletion through the privacy request path. We verify that the request comes from the account holder, explain any data we must retain, and record the action taken.

Seven Privacy Policy Answers Before Account Access

These answers cover the searches we see around account data, local wallets, cookies, retention and privacy requests. Read them before you open an account, especially if you share a mobile device or plan to use DANA, OVO, GoPay or QRIS. Each answer points to the specific record or account step involved rather than asking you to submit broad personal details.

The Privacy Policy covers account identifiers, verified phone details, device and session signals, cookie records, transaction references and service-request messages. We may also process lobby activity when it is needed to maintain access, investigate faults or protect your account.

Our Privacy Policy treats DANA, OVO, GoPay and QRIS references as transaction data connected to cashier activity. We use method, reference, amount, time and displayed status where needed to match a receipt, answer a query or meet legal duties.

Yes, you can submit a correction or deletion request through the account privacy path. We first verify that you control the account, then assess the requested record. Some transaction, security or dispute records may need to remain for legal or operational reasons.

Yes. The policy covers cookies and related browser storage used for sessions, permitted preferences, security and page operation. Changing browser controls can remove stored choices or sign you out, so confirm that you know your account credentials before clearing device data.

Retention depends on the record's purpose and any applicable legal duty. Account, payment, security and request records can follow different periods. We remove or anonymise data when it is no longer required, subject to transaction reconciliation, disputes and legal retention needs.

We use phone verification, session controls, access restrictions and device signals to reduce unauthorised entry. You should never share a password or one-time code in a privacy request. After using a shared device, sign out and clear any saved credentials.

Access depends on local law. The Privacy Policy still explains how data is handled when you create or use an eligible account, including phone verification, cookies and wallet records. You should check the rules that apply to your location before proceeding.