Reference

Open batara88 Privacy Policy Before Account Access

Our batara88 Privacy Policy explains what we collect when you open an account, verify your phone and move between the lobby and local wallet options.

Account dataWallet recordsCookie choicesPolicy requests
batara88 Open batara88 Privacy Policy Before Account Access
CONTACT PATHS

Use Support When Privacy Questions Stall

A clear contact path helps you ask about the Privacy Policy without sending account details through an unsafe route. Start with the support link attached to your signed-in account, especially when your question concerns phone verification, wallet status or a receipt connected with DANA or QRIS. We use the account context to locate the right record, while access and eligibility depends on local law. Please include only the details needed to identify your request.

Team online

Account support link

Use the support link after signing in to ask what account data we hold, why a verification step appears or how to correct a profile detail. Keeping the request inside your account helps us connect the Privacy Policy question to the correct batara88 record.

Cashier status path

For a privacy question tied to DANA, OVO, GoPay, QRIS or a bank transfer, begin beside the cashier status rather than sending payment credentials. We can check the related reference and explain which data came from the wallet or bank rail.

Data request route

Ask for access, correction or deletion through support and state the account step involved. We may request phone verification before replying, because a Privacy Policy response can contain personal account details that should not reach another person.

DATA IN PRACTICE

Explore How batara88 Handles Your Data

Our handling process follows the account journey rather than collecting a broad profile without purpose.

Account data

We may hold your sign-in details, phone verification result and selected account settings. These details let us connect your request to the correct account when you ask about access, a policy choice or a record linked to Texas Holdem Live.

Wallet references

A DANA, OVO, GoPay or QRIS request can create a reference, amount and status record for matching. We do not need your wallet password to identify that event, and the external payment provider may retain its own separate records.

Cookies

Cookies and similar session tools can remember sign-in state, language or a page setting on your device. You can manage browser permissions, but turning off necessary cookies may affect the account path used to reach the lobby and policy pages.

Device security

We may record device and connection signals when you sign in, particularly after a phone verification step. These checks help identify unusual access and protect account data; they are not a request for your private device files or unrelated app content.

Retention timing

We keep account, payment-status and support records for the period needed to operate services, settle disputes or meet applicable legal duties. When that reason ends, the Privacy Policy process allows deletion or continued storage only where a valid duty applies.

Change requests

You can ask us to view, correct or remove eligible data by contacting support from the account path. Include the email or phone detail used at account opening, and we may verify ownership before making a change or explaining a restriction.

Browse Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you may have before opening an account or linking a local payment route. They cover collection, cookies, access requests, wallet references and account security in plain terms. If your situation is not listed, use the signed-in support path and tell us which record or account step you want us to check. Where local law permits, we will explain the available action and any identity check needed.

It covers account details, phone verification, device signals, cookies, support messages and payment-status references. It explains why we use each category, how long records may remain and how you can request access, correction or deletion through the support path.

Yes. The policy covers references created when you use DANA or QRIS, such as a transaction identifier, status and account connection. Wallet credentials remain with the payment provider, which may apply its own privacy terms and retention rules.

Sign in, open the support route and ask for an account data request. Tell us the phone or email used during account opening. We may complete phone verification before sharing records, so the response goes to the account holder.

You can request a correction through support and identify the field that is wrong, such as a phone number or profile detail. We may compare the request with your account step and ask for verification before changing the stored record.

Cookies can preserve a session, language choice or page setting on your browser. Necessary cookies support the sign-in route, while browser controls can limit optional storage. Removing necessary cookies may require you to sign in again on that device.

We use phone verification and device or connection signals to check account access, especially after an unfamiliar sign-in. Keep your account details private and contact support if a device or wallet status appears that you do not recognise.

You may ask for deletion through the support route, and we will assess which records can be removed. Some account, payment-status or support records may remain when needed for a dispute, security matter or legal duty.