Reference

banteng 69 Privacy Policy for Your Account

Your account details, DANA and QRIS records, and mobile login activity are explained in the banteng 69 Privacy Policy.

Account data clarityWallet record useCookie choicesRequest a change
banteng 69 banteng 69 Privacy Policy for Your Account
REQUEST PATHS

Where Privacy Questions Meet Account Help

A clear request route helps when you want to see, correct, or remove personal details. Open account help beside the cashier path, describe the Privacy Policy question, and use the phone number linked to your account so we can match the request with the correct record. In Bandung and across Indonesia, the same route handles wallet status and policy requests.

Team online

Account access

If phone verification blocks access, send an account-help request from the login path. We use the linked phone detail to confirm ownership before discussing private account records.

Wallet status

For a DANA, OVO, GoPay, or QRIS receipt question, include the payment reference and date. We use those details to locate the relevant record without asking for your wallet password.

Policy request

Ask to view, correct, or delete eligible data through the policy request route. We may request account verification first, protecting your records from a third-party request.

HANDLING DETAILS

How We Protect Your Account Record

Privacy controls work alongside the account steps you already use: phone verification, sign-in checks, wallet reference matching, and device review.

Data collection

We collect details you provide during account creation and phone verification, plus technical signals from your browser or device. Payment references help us match DANA, OVO, GoPay, QRIS, and bank transfer activity.

Cookie choices

Cookies can remember sign-in preferences, maintain account security, and help us understand whether a page works correctly. You can manage browser cookie controls, though some account functions may then require another sign-in.

Account security

We use phone verification, sign-in event checks, and device signals to identify unusual access. Never send us your password or wallet PIN when asking about an account or payment record.

Retention window

We retain account, payment, and support records for service delivery, security checks, disputes, and applicable legal duties. When a record is no longer needed for those purposes, our process removes or de-identifies it.

Policy changes

When this Privacy Policy changes, we update the page and its date so you can compare the current wording before using account access. Material changes may also appear through the account contact route.

Request route

To request access, correction, or deletion, contact account help with your linked phone number and a clear description. We verify ownership before releasing or changing personal data connected with your account.

Privacy Policy Questions for Indonesia

These Privacy Policy answers cover the account and wallet questions you may search before opening an account. We keep the wording practical: what we collect, how mobile access works, which payment references appear in records, and how you can contact us for a change.

It covers account details, phone verification, device and browser signals, cookies, support messages, payment references, security events, retention, and requests to access or correct data connected with your account.

We use the linked phone number for account verification, sign-in protection, and request matching. It helps us confirm that a person asking about private records controls the relevant account.

Yes. The policy includes payment references and wallet status connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account routes. We do not ask for your wallet PIN.

You can ask for access through account help beside the cashier path. Include your linked phone number and request details; we may verify ownership before preparing records that can be shared.

Send a correction request through the policy route and identify the incorrect field, such as a contact detail or payment reference. We check the account first, then update eligible records.

A mobile browser may store different cookie choices or device signals than a desktop session. Review browser controls after signing in, especially when moving between the lobby and account pages.

You may request deletion through account help, but some records can remain for security, dispute handling, service accounting, or legal duties. We explain the result after verifying your account.