Reference

Privacy Policy for bata124 Wallet Access

Our bata124 Privacy Policy explains how we handle account details, device signals and wallet records when you use the casino, sports and game areas.

Account clarityWallet recordsDevice choicesRequest access
Browse Our Lobby Read FAQ
bata124 Privacy Policy for bata124 Wallet Access
REQUEST HELP

Get Help With Your Privacy Request

A clear support route helps you ask what we hold, why we use it or how to correct an account detail.

Access request Ask us for the personal details connected with your account, such as your registered phone number, login history or payment reference. We may ask you to complete phone verification before sharing account-linked data, so a request reaches the person who controls the account.
Correction path If your account name, phone detail or wallet status is inaccurate, send the specific field and the reason for the correction through the account support path. We compare the request with the existing account record before changing it, which helps prevent an unrelated change.
Status follow-up For a privacy request connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, include the reference shown in your account history. We can then separate a data question from a payment-status question and direct the reply to the correct record.
DATA CONTROL PATH

Your Data Path Across Devices

We design the Privacy Policy around the moments where account data is actually created or used: phone verification, wallet status checks, mobile login and support contact.

Account collection

During account creation, we may receive your chosen account details, phone verification result and activity needed to provide access. We use these records to connect your login with the correct account rather than asking you to repeat identity details whenever you move between the mobile lobby and desktop.

Wallet matching

Payment records normally contain a rail, amount status and reference needed to match activity with your account. For DANA, OVO, GoPay and QRIS, that reference supports status checks. Bank transfer and virtual account records serve the same matching purpose when those rails are selected.

Cookie choices

Cookies and similar session tools help keep your login path working, remember selected page settings and protect the account from repeated suspicious requests. You can manage cookie controls through your browser, although limiting them may require you to repeat sign-in or verification steps.

Security signals

We may record browser, device, time and session signals when you sign in or change account details. These checks help us notice an unfamiliar access pattern. They do not replace your responsibility to keep passwords and verification codes private or to sign out on shared devices.

Retention timing

We keep account, support and payment-reference records only for the period needed for security, service handling and applicable legal duties. When a record is no longer needed for those purposes, our handling process is designed to remove it or separate it from direct account identification.

Change or deletion

You can ask what account data we hold, request a correction or ask about deletion through the support path in your account area. Deletion may be limited where a record is needed for security, an open payment question or a legal duty; we explain the reason in our reply.

Privacy Policy Questions About Your Account

These answers focus on the account and wallet questions you may search before opening access. If your situation is not covered, use the support path in your account area and tell us which data record or Privacy Policy point you want us to check.

The bata124 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. It also explains how we handle access, correction, deletion and retention requests connected with your account and wallet activity.

We may keep the payment rail, status and reference needed to match activity with your account. A DANA, OVO, GoPay or QRIS reference supports status checks, while the Privacy Policy does not ask you to send a wallet password or one-time security code.

Device and browser signals help us keep a mobile or desktop session working, identify unusual account access and protect changes to phone or wallet details. These signals are handled for account security and service operation, as explained in the Privacy Policy.

Use the support path inside your bata124 account and ask for an access request. Include the account phone detail or relevant payment reference, but never send your password or verification code. We may complete phone verification before releasing account-linked data.

Yes, you can ask us to correct an inaccurate account name, phone detail or wallet status. Identify the exact field through the account support path. We compare the request with the account record first, then explain any change or reason it cannot be made.

We retain payment references for the period needed to handle account security, support questions, payment-status checks and applicable legal duties. The Privacy Policy does not set one identical period for every record, because retention depends on the record type and its purpose.

Yes. Access to the service and any related account process depends on local law and is available where local law permits. The Privacy Policy still explains our handling of account and device data for the Indonesia access path, including requests made through support.

Related Pages

bata124 Indonesia Liga 1 Over Under About Us Table Game Guide bata124 Casino