Reference

Privacy Policy for Your bodyslot Account

Our Privacy Policy shows how we handle the account details connected with Live Blackjack Royal, Monsoon Magic Slots and your wallet activity.

Clear data purposesWallet records explainedPhone access controlsCookie choices
Browse the lobby Read FAQ
bodyslot Privacy Policy for Your bodyslot Account
PRIVACY HELP PATH

A Clear Route for Privacy Questions

Privacy questions should not get lost beside a cashier request. We keep a support path inside your account for questions about phone verification, cookie choices, wallet references or a copy of personal…

Account request Use the support route after login to ask for access, correction or removal of personal data. Include your account phone number and describe the exact record, such as a QRIS reference or device login.
Wallet record For DANA, OVO or GoPay questions, share the payment reference shown in your account rather than a wallet password. We use that reference to locate the relevant event and explain its privacy handling.
Access trouble If phone verification blocks your privacy request, tell us which device path you used and what appeared on screen. We can separate an account-access issue from a request to change stored data.
DATA HANDLING

How We Protect Wallet And Login Data

We handle privacy as part of the account flow, from the first phone check to the point where you browse Football Score Chase or Fishing War Fast Round on mobile.

Data collected

We may store your phone number, verification status, login timestamps, device signals, selected pages and payment references. These fields help us recognise your account and investigate an unusual access event without asking for your wallet password.

Cookies

Cookies can remember a session, language setting and security state when you move from login to the lobby. You can manage browser cookie controls, although disabling necessary cookies may interrupt account access.

Account security

Phone verification is part of account access, and we use device and login signals to identify unusual attempts. Never send a one-time code or wallet password through support; we will not request either.

Retention

We keep account, security and payment references for the period needed to operate the service, resolve disputes or meet legal duties. When that period ends, records are deleted or changed so they no longer identify you.

Your request

You can ask what personal data we hold, request a correction or ask about deletion through the account support route. We may verify ownership with your registered phone before releasing or changing a record.

Policy contact

Our support team handles privacy questions through the logged-in account path, including requests linked to QRIS, bank transfer or virtual account references. If access is unavailable, describe the issue without including secret credentials.

Privacy Policy Answers Before Account Access

These Privacy Policy answers focus on the account decisions Indonesian customers usually make before opening access. We cover phone verification, wallet records, mobile cookies, data requests and local-law restrictions, so you know what happens when you use DANA, OVO, GoPay, QRIS or a bank rail.

It covers account details, phone verification, login and device events, cookies, lobby activity linked to your account and payment references. It also explains retention, security steps, request handling and when access depends on local law.

We may collect your phone number, verification result, login timestamps, device signals and records needed to connect your account with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

After login, use the account support route and ask for a personal-data access request. State the phone number on the account and the record you need, such as a device event or QRIS payment reference.

Yes, you can ask us to correct an inaccurate account detail through support. We may confirm ownership with your registered phone before making a change, and we will explain if a payment record must remain unchanged.

We use payment references and wallet status to match an account request to the correct transaction. We do not need your wallet password, and you should never send that password or a one-time code through support.

Necessary cookies can keep your session and security state while you move from phone verification to the lobby. Browser controls let you manage cookies, but disabling required ones may interrupt login or account access.

You can send a removal request through the logged-in support path. We assess the request against operational and legal duties, explain any records that must remain, and remove or anonymise eligible data after approval.

Related Pages

bodyslot Indonesia Access guide Monsoon Magic Slots bodyslot Casino Live Blackjack Royal