Reference

Privacy Policy For Your bata123 Account

bata123 Privacy Policy explains what account details we collect, why we use them and how you can ask about your records before opening or using an account.

Clear data purposesWallet record contextAccount access stepsIndonesia policy scope
bata123 Privacy Policy For Your bata123 Account
CONTACT ROUTES

Get A Direct Answer About Privacy

A clear contact route helps you understand the Privacy Policy before you continue with an account step.

Account questions Ask us about account details, phone verification records or a login event linked to…
Wallet references When DANA, OVO, GoPay or QRIS appears in your account history, send the receipt…
Correction requests If a profile detail is inaccurate, contact us with the specific field and the…
DATA PRACTICES

See The Privacy Steps Behind Access

Your Privacy Policy questions usually connect to a practical account event: a new login, a phone check, a wallet reference or a request to correct a record.

Data handling

We use account contact details to provide access messages and support replies, and we use transaction references to reconcile payment…

Cookie choices

Cookies can keep a session active and remember basic page choices.

Account security

Phone verification and login-event checks help us distinguish a normal account step from unusual access.

Record retention

We keep personal and transaction records only while they support account operation, security checks, dispute handling or a legal need.

Access requests

You can ask which personal details are connected with your account and the purpose for using them.

Policy changes

When this Privacy Policy changes, we update the policy page and identify the revised subject.

Privacy Policy Answers For bata123

These Privacy Policy answers address the account and payment questions you are most likely to search before continuing. They explain how to request a copy, correct a detail, understand cookies and ask about wallet records without turning a policy question into a general lobby question. If your situation is specific, use the support path and describe the exact account step that created the concern.

It covers the personal details, account events, device signals, cookies and payment references we may handle when you create, access or contact us about an account. It also explains purposes, retention, security measures and the route for asking about or correcting your records.

Contact our support path and ask for an account data request. State whether you want access to contact details, login records, cookie-related data or transaction references. We may verify your phone or account details first so another person cannot receive your private records.

Our Privacy Policy concerns payment references and status details, not your private wallet password. DANA, OVO, GoPay and QRIS may appear as the selected rail or receipt reference. Do not send wallet credentials to support, even when asking us to check a transaction.

Device type, browser signals and login events help us investigate unusual access and protect the account path. A mobile login may create different technical signals from a desktop login. We use those details for security and service operation, not as a substitute for identity confirmation.

Yes, you can ask us to correct an inaccurate account detail. Name the field and where it appears, such as during phone verification or a support request. We may ask for limited confirmation before changing it, because an unchecked edit could expose your account.

We retain records while they support account operation, security review, payment reconciliation, dispute handling or a legal need. After that purpose ends, we remove or anonymise them where available. A support request can ask for the purpose connected to a particular record.

The policy is written for our Indonesia account path, including local payment references and device access. Eligibility and access depend on local law. If you are unsure whether an account step is available in your location, contact support before sharing additional personal details.