Reference

balada123 Privacy Policy for Your Account

Our Privacy Policy explains what account data we collect, why we use it, and how you can ask about it before opening an account.

Account dataWallet checksCookie choicesPolicy requests
balada123 balada123 Privacy Policy for Your Account
CONTACT PATHS

Three Ways To Ask About Privacy

Questions about our Privacy Policy should be specific so we can route them to the right account record. You can ask about a phone verification entry, a wallet reference or a cookie choice without describing your wider activity. For a faster response, include the account email or phone detail already attached to your profile, but never send a password or wallet PIN. If your account is not yet open, you can still ask a policy question through the public contact route.

Team online

Account support

Open the support path from your account menu when you need a copy of the Privacy Policy, a data-access request or help identifying the phone detail linked to your profile. We use the account record to confirm that the request comes from you.

Wallet status

For a DANA, OVO, GoPay or QRIS reference, send the payment date, route name and visible status through support. We can then connect the request to the matching account record without asking you to share a PIN or full wallet password.

Public policy contact

If you have not opened an account, use the contact option linked beside this Privacy Policy. Tell us whether your question concerns cookies, retention, phone verification or correction, and we will explain the next identity check before handling the request.

SIX DATA CHECKS

What Our Privacy Process Covers

We handle policy requests as account tasks rather than as general lobby questions. That means we first identify the relevant record, then explain the purpose, access route and retention position in plain…

Collected data

We may hold the account details you submit, phone verification results, sign-in timestamps, device session signals and payment references. These details help us connect a request such as QRIS status checking to the correct account without treating every device as the same person.

Cookie controls

Cookies and similar browser records can keep your session connected while you move from login to the lobby. You can manage browser cookie settings on your device, though switching them off may require another sign-in or prevent a saved session from working.

Account security

Phone verification and sign-in checks help us distinguish your account from an unfamiliar session. If you use a shared device, sign out after checking the lobby and avoid saving credentials in the browser. We will not ask for your password through a policy request.

Retention handling

We retain records only for the period needed for account operation, payment reconciliation, security checks or a legal request. A DANA receipt reference and a phone verification record can therefore follow different retention steps, depending on their purpose.

Request changes

You can ask us to correct account data that is inaccurate or incomplete. Include the field you want changed and the reason, such as an old phone number. We may request a matching account check before applying the change so another person cannot edit your profile.

Policy contact

For a copy of your data, a correction, a cookie question or a retention query, contact us through the account support path or public policy contact. If access is discussed, eligibility depends on local law, and we will explain any required check.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. They explain how we connect device activity, phone verification and payment references, plus the steps for asking about your data. If your situation is not listed, use the support route and include only the details needed to locate your request.

The balada123 Privacy Policy covers account details, phone verification, sign-in and device session records, cookies, support messages and payment references. It also explains why we use each category, how we protect it, how long records may remain and how you can request access or correction.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS actions, including a visible status or receipt detail. We use those references to match a wallet request to your account and resolve payment questions without asking for your wallet PIN.

You can request a copy through account support or the public policy contact route. Tell us that you want data access and provide the account email or phone detail already attached to your profile. We may complete an identity check before sending account-related records.

Send a correction request through the support path and name the field that is wrong, such as an old phone number. We may compare your request with the existing account record before changing it. This step protects your profile from an unauthorised edit.

Cookies can keep a browser session connected after login and help us recognise a returning device session. Your browser settings control many cookie choices. If you remove or block them, you may need to sign in again or lose saved session functions.

Retention depends on why a record exists. A bank transfer, virtual account or QRIS reference may remain while we reconcile the account action, handle a security question or meet a legal need. Ask support about a specific reference for a clearer retention response.

Yes. Account access and policy rights depend on local law. Where local law permits, you can ask for access, correction or clarification through our support route. We will explain the identity check and any limits that apply to the specific request.