Reference

Open your account with clear privacy terms

Your account, wallet and device data are handled under this Privacy Policy before you enter the lobby or use DANA, OVO, GoPay and QRIS.

Account data explainedDANA, OVO, GoPay, QRISCookie choices coveredSupport contact paths
Explore Lobby Read FAQ
batman365 Open your account with clear privacy terms
CONTACT ROUTES

Start a privacy request through support

Privacy questions should reach a real service channel, not a dead inbox. Our support desk handles account data requests every day from 09:00 to 23:00 WIB through live chat and email. Share your account ID, registered phone number and the data topic you want checked, and we will route it to the team that can verify it.

Team online

Live chat

Use live chat from the account menu when you need a quick privacy check. We may ask for your account ID and recent login device so we can confirm the request belongs to you.

Email desk

Send privacy requests by email when you need a written answer or correction record. Include your registered phone number, wallet rail used, and the exact account detail you want us to inspect.

Account menu

Open Account, then Profile, then Privacy to review saved contact details and cookie choices. This path also helps you prepare the right evidence before asking us to change account records.

DATA CONTROLS

Browse privacy controls before you join

Privacy works better when the account flow shows what happens at each step. We separate profile data, wallet references, device records and support messages so each team sees only what it needs…

Account details

We use your phone number, username and profile records to keep account access tied to you. If a detail changes, ask support to update it after identity checks through chat or email.

Wallet references

DANA, OVO, GoPay and QRIS references help us match deposits and withdrawals to the correct account ledger. We store transaction references and timing, not private wallet app conversations or unrelated spending.

Device signals

We may record browser type, IP region, login timing and device changes to spot unusual account access. When something looks different, we can ask for confirmation before changing profile or wallet records.

Cookie choices

Cookies keep your session active, remember language display and measure basic site behaviour. You can adjust browser cookie settings, though blocking all cookies may force fresh login checks more often.

Retention checks

We keep privacy records only as long as needed for account service, transaction tracing, dispute handling and legal duties. When a record is no longer needed, we remove or restrict it from routine access.

Change requests

Ask us to correct outdated profile data, explain a record or review access to your account details. We verify ownership first, then reply through the same support path whenever possible.

Check privacy answers before opening account

These answers focus on the privacy choices you are likely to check before creating an account or using your wallet. They cover what we collect, how payment references are handled, how cookies work, and how you can reach us when a record needs correction.

We collect the details needed to create and protect your account, such as username, phone number, login records and support messages. Wallet references are added when you use DANA, OVO, GoPay or QRIS.

No. We use transaction references, timing and account matching details so your wallet activity can be checked inside our ledger. We do not need unrelated wallet app history to process a privacy or account request.

Cookies keep you signed in, remember display choices and help us notice repeated errors during account access. On Android or iOS browsers, you can change cookie settings through the browser privacy menu.

Yes. Contact live chat or email with your account ID, registered phone number and the field you want corrected. We verify ownership first because profile changes can affect wallet checks and account access.

We keep account, wallet and support records for as long as they are needed for service, transaction tracing, dispute handling and legal duties. Older records may be removed or access-restricted when no longer needed.

Only the team members needed to handle the request should see the record. A wallet question goes to account and payment staff, while a cookie or login issue may be checked by technical support.

Yes, it explains how we use location, device and account signals when access or eligibility depends on local law. If a signal needs confirmation, support may ask you to verify account ownership before changes are made.

Related Pages

batman365 Indonesia Register FAQ About Us batman365 Casino