Reference

batara88 Privacy Policy: Your Data, Wallets and Account Access

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account dataDevice checksWallet recordsPolicy requests
batara88 batara88 Privacy Policy: Your Data, Wallets and Account Access
CONTACT PATHS

Get Privacy Help Beside Your Account Route

A clear support route helps you ask about the Privacy Policy without sending sensitive details through an unsuitable channel. Start from the account support path, include the email or phone detail attached to your account, and describe the request in plain English. We can then locate the relevant record, explain the next account step, and direct payment receipt questions to the cashier-status team.

Team online

Access request

Use the account support path to ask what personal details are linked to your login. We may ask for an account step that confirms you are making the request.

Wallet data query

For DANA, OVO, GoPay or QRIS references, mention the wallet name and transaction date without sharing a full password. We use the receipt reference to find the correct record.

Correction request

If your contact detail or device record appears inaccurate, tell our support team which field needs attention. We review the account context before changing information linked to access.

HANDLING DETAILS

How batara88 Applies This Privacy Policy

We treat privacy as an account process rather than a label on a page. The steps below explain how we handle cookies, sign-in signals, wallet references, retention, and requests to change your…

Account creation

When you open an account, we use the submitted contact details to create your login record and send account-related notices. Clear phone verification may be required before access is completed.

Device signals

On mobile or desktop, we may record device and browser signals connected with sign-in. These records help us compare a new access attempt with your account history.

Cookies

Cookies can keep a session active and remember basic preferences, such as the selected lobby path. You can manage cookie settings in your browser, though some access steps may then need repeating.

Account protection

We use login events, verification results, and unusual access patterns to protect your account. We do not ask for your password through a support message or a wallet-status request.

Retention period

We retain account, support, and transaction references for the period needed to operate access, resolve disputes, or meet a valid legal duty. Records are then deleted or separated from direct identifiers.

Change request

To request correction, deletion, or a copy of your data, contact support through the account route. We verify the request against your account before taking action or explaining any limit.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we hear most often from people checking account access in Indonesia. They cover collected data, wallet references, device records, cookies, correction requests, and the verification step used to protect your account.

The Privacy Policy covers contact details, verification responses, login events, device signals, support messages, and transaction references created while you use your account. We use them for access, support, protection, and valid legal duties.

Yes. The Privacy Policy covers payment references from DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. These references help us match a wallet request to your account.

Phone verification helps us confirm that the person opening or accessing the account controls the submitted contact detail. It also supports requests to view, correct, or remove data under the Privacy Policy.

When you sign in on a phone or desktop, we may record device type, browser settings, login time, and approximate connection data. These signals help us identify unusual access and protect your account.

You can ask through the account support path for a copy or correction. Include the account contact detail and describe the field involved; we verify your request before releasing or changing records.

We keep account, support, and transaction records for the time needed to provide access, resolve a dispute, or meet a valid legal duty. After that, we delete or anonymise them under our process.

It applies to data handled through the account and related support routes, while access or eligibility depends on local law. If a local rule changes how a request is handled, we explain that limit.