Reference

Open bataplay Privacy Policy Clearly

bataplay Privacy Policy explains what we collect when you create an account, verify your phone and use the Indonesia lobby from mobile or desktop.

Clear data purposesWallet record controlsPhone verification contextCookie choices
bataplay Open bataplay Privacy Policy Clearly
CONTACT PATHS

Browse Privacy Help Beside Your Account

A clear contact route matters when your Privacy Policy question concerns a phone check, a wallet record or a device session. We keep policy support close to the account and cashier path, so you can send a request without describing your entire activity again. In Yogyakarta and elsewhere in Indonesia, open the support option after signing in, state the request in plain English, and attach only the receipt or screen detail needed for us to locate the record.

Team online

Account support

Use the support route after signing in when you need to ask about personal data, a phone verification record or a device entry. Include your registered phone number so we can locate the correct account without asking you to send a password.

Wallet record help

For a Privacy Policy question about DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, mention the payment rail and reference shown in your receipt. We use that narrow detail to check the record while limiting extra account exposure.

Access request

Ask us to provide, correct or remove eligible personal data through the same account support route. We may confirm your phone verification step before responding, because a privacy request should reach the account owner rather than another person.

DATA PRACTICES

Explore How Privacy Controls Work

Privacy is handled through practical account controls rather than broad promises. We separate sign-in checks from wallet references, review device activity when a session looks unusual, and use cookies to keep a…

Account data

We collect the details needed for your account path, including contact data and the phone verification result. This lets us connect your request to the right profile before you reach areas containing wallet records or account activity.

Payment references

DANA, OVO, GoPay and QRIS references can be stored with account activity, while bank transfer and virtual account records may include a matching transaction reference. We use these entries for status checks, reconciliation and a focused response to your request.

Cookies

Cookies help retain sign-in state, remember selected settings and support movement between account pages. You can manage cookie controls in your browser; changing them may require another login before the account path works as expected.

Device security

A mobile browser or desktop session can create device and connection signals used to detect unusual access. If a new device opens Live Roulette Turbo or another account area, we may ask for an additional account check.

Retention

We keep personal data only while it serves the purpose stated in the Privacy Policy or while a legal, security or transaction record requires it. When retention ends, we remove or separate the data according to the applicable process.

Your request

You can ask what personal data we hold, request a correction, or ask whether deletion is available. Send the request from the signed-in support path and identify the affected account step, such as phone verification or QRIS receipt matching.

Browse Privacy Policy Answers

These Privacy Policy answers address the account questions you are most likely to have before opening an account or sending a data request. They explain wallet records, cookies, phone verification, mobile access and the practical route for contacting us. If your situation is not covered, use the signed-in support path and describe the specific record you want us to check.

It covers personal data collected during account creation, phone verification, sign-in, wallet activity, cookie use and support requests. It also explains retention, security checks and eligible access or correction requests. Service access depends on local law, including where local law permits.

We use your phone number to create and identify the account path and to complete the phone verification step before account access. It helps us connect a Privacy Policy request to you and reduce the chance that another person receives account data.

Yes. Payment references from DANA, OVO, GoPay and QRIS can be linked to account activity for status checks and receipt questions. Bank transfer and virtual account references can be handled in the same way, with access limited to the purpose described in the Privacy Policy.

We may use device and connection signals to identify unusual access, such as a new mobile browser opening an account area. These signals support account security and are not a request for your device contents. Cookie controls remain available through your browser settings.

You can ask for access to personal data or request a correction through the signed-in support route. Include your registered phone number and the record concerned, such as a QRIS receipt or phone verification entry. We may confirm ownership before responding.

Retention depends on the purpose of the record and any applicable legal or security need. Wallet references may remain while a transaction question is open, while other data can be removed or separated when its stated purpose ends. Ask support about a specific record.

Sign in, open the account support option beside the cashier path, and select the privacy request route where shown. Describe the data concern without sending a password. For wallet matters, add the payment rail and limited receipt reference so we can narrow the check.