Reference

Open the bata46 Privacy Policy

The bata46 Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account accessWallet recordsCookie choicesRequest support
Explore Our Lobby Read FAQ
bata46 Open the bata46 Privacy Policy
REQUEST ROUTE

Choose a clear policy contact path

A direct request helps us locate the right account record without asking you to repeat the same details. Use the support route shown inside your account when you need a copy of your stored data, a correction to phone details or an explanation of a wallet reference. If you are in Bandung or elsewhere in Indonesia, keep your account identifier and relevant date ready so we can handle the request against the correct record.

Team online

Account request

Ask through the account support route for a copy of personal details connected with your bata46 access. Include your account identifier and the phone number used for verification so we can distinguish your request from another account.

Wallet question

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and date rather than a wallet password or security code. We use those details to check the status without requesting secret wallet credentials.

Access concern

If a cookie choice, device check or phone verification affects your account access, describe the screen and device path you used. We can route the concern to the team handling privacy and account security.

DATA PRACTICE

Browse bata46 privacy controls

We keep the Privacy Policy practical: it tells you why a data point is used, how account security affects access and where to send a change request.

Data handling

We use your account and contact details to provide access, complete phone verification, respond to support and connect a payment status with the right account. We do not need your DANA, OVO or GoPay password to check a transaction reference.

Cookie choices

Cookies and browser storage can keep a sign-in path consistent, remember a selected preference and help detect unusual access. You can adjust browser controls, although limiting required storage may interrupt account verification or policy-request routing.

Account security

Phone verification and device signals help us identify the account session being used. If you change device or browser, a new security check may appear before access continues. Never send a password, wallet PIN or one-time code in a support message.

Record retention

We retain account, support and payment-reference records for the period needed for the stated service, security and legal purposes. When a record is no longer needed, our handling follows the deletion or anonymisation process applicable to that record.

Change request

You can ask us to correct an inaccurate phone detail, clarify a stored record or request removal where the law allows. Send the request through the account support path with enough context for us to verify ownership.

Policy contact

Privacy questions belong in the support route linked to your account, especially when they concern a QRIS entry, bank transfer reference or device session. We may ask for verification before discussing personal data or making an account change.

Check bata46 Privacy Policy answers

These Privacy Policy answers focus on the account steps you are most likely to question before opening an account. We explain the records linked to phone verification, mobile cookies, local wallet references and requests for access or correction. Where a request depends on legal requirements, we will apply the rule relevant to your location and the service available there.

The bata46 Privacy Policy covers account and contact details, phone verification, device and login records, cookies, support messages and payment references. It explains why we use each category, how long records may be kept and how you can send a request about eligible personal data.

We do not need your DANA or GoPay password to match a payment status. Our records may contain a reference, amount status and date linked to your account. Never place a wallet password, PIN or one-time code in a support request.

Phone verification helps us connect an account request with the person who controls the registered contact detail. It can also trigger a security check when you move from a mobile browser to desktop access. We use that step to protect account data before discussing it.

Use the support route inside your account and ask for an access copy. Include your account identifier and the registered phone detail, but not your password or wallet security code. We may verify ownership before releasing records connected with your Privacy Policy request.

Yes. Send a correction request through the account support path and identify the field that needs changing, such as a phone detail. Explain the accurate value and provide the requested ownership check. We assess the request under the Privacy Policy and applicable law.

Cookies and browser storage help preserve sign-in continuity, page preferences and security checks on a phone. If you clear or block them, you may need to repeat account access steps. Your browser settings control optional storage, while required security storage may remain necessary.

Access to the service and handling of requests depends on local law. The Privacy Policy applies where local law permits, and some account or data actions may be restricted by the rules relevant to your location. Use our support route for a location-specific question.

Related Pages

bata46 Indonesia About Us Account information bata46 Casino GoPay Payout Help