Reference

body4d Privacy Policy And Your Account

body4d keeps its Privacy Policy practical: it explains what we collect when you open an account, use DANA or QRIS, and contact support about wallet status.

Account dataWallet recordsDevice choicesCookie controls
Browse the lobby Read FAQ
body4d body4d Privacy Policy And Your Account
HELP WITH YOUR DATA

Contact Us About Privacy Policy

A clear support route matters when a data request sits beside an account or wallet question.

Data request Ask us to confirm whether we hold account data, explain its use or provide the policy basis for a handling step. Include your verified account phone number so we can match the request without asking for your DANA, OVO or GoPay password.
Correction path If your phone, account detail or identity record needs correcting, contact support from the account linked to that record. We may ask for a verification step before changing it, helping prevent another person from editing your account through a copied receipt.
Receipt concern For a QRIS, bank transfer or virtual account question, attach the payment reference and time rather than private wallet credentials. We use the reference to check status against the account record and keep the privacy request separate from the payment review.
HOW WE HANDLE DATA

Inside body4d Data Controls

The Privacy Policy is designed around the points where your data actually moves: account creation, phone verification, lobby access, wallet matching, device sessions and support contact.

Account records

We use the phone number and account details you submit to create access, complete phone verification and connect activity with the correct account. If you browse Live Roulette Prestige or Garuda Flight Reels after signing in, related session records may be kept for account security and service continuity.

Payment references

A DANA, OVO, GoPay or QRIS payment can create a reference, amount, status and time record. Bank transfer and virtual account records serve the same matching purpose. We use these fields to identify a receipt and resolve a wallet-status question without requesting your private wallet credentials.

Device and cookies

Your browser or mobile device may provide session, language, browser and security signals. Cookies can keep a signed-in session or remember a setting. You can manage cookie behaviour in your browser, although restricting necessary cookies may require you to sign in again.

Account security

Phone verification helps us connect an account request with the right person. We may examine sign-in time, device changes and unusual payment patterns before allowing an account action. Never share a verification code, wallet PIN or password in a support message.

Retention choices

We retain each category only while it supports account operation, security, dispute handling or a legal duty described in the Privacy Policy. When the relevant period ends, we assess whether the record can be deleted, anonymised or restricted instead of keeping it without a purpose.

Your requests

You can ask for access, correction, deletion, restriction or an explanation of how your data is used, subject to identity checks and any legal limits. Send the request through support from your account, and tell us which record or policy action you want us to address.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before account access. They cover the data linked to a phone-verified account, local wallet records, cookies, device sessions and requests for changes. If your question concerns a specific receipt or sign-in event, use the support route with the account reference rather than sending a password.

It covers account and phone-verification data, device and session signals, cookies, support messages, game activity linked to your account and payment references. It also explains retention, security checks, your request options and the circumstances in which we may restrict or remove a record.

Yes. The Privacy Policy explains the transaction references we may receive when you use DANA, OVO, GoPay or QRIS, including status, time and matching details. We use those records to connect a payment with your account and answer a receipt question, not to request your wallet password.

We may collect the phone number and account details you submit, your phone-verification result, sign-in events, device or browser signals, support messages and activity connected with the signed-in account. The policy explains why each category is needed and how long the relevant record may remain.

Yes. Send a correction request through support from the account linked to the record, identify the field that needs changing and complete any identity check we request. We may keep a record of the request so we can show what was changed and protect the account from unauthorised edits.

Contact us through the signed-in support path and specify the data or account record you want removed. We first verify the request, then check whether retention is required for security, payment disputes or a legal duty. If deletion is limited, we explain the reason and any available restriction.

Cookies or similar session tools may keep your sign-in active, remember a selected setting and help identify unusual access. You can adjust browser controls on your phone or desktop. Blocking necessary cookies may end the session or require another phone-verification step when you return.

Some account access, eligibility, retention and request outcomes depend on the rules that apply to your location. Where access or eligibility is discussed, it depends on local law. Our support team can explain the policy route for your request, but cannot change a legal restriction.

Related Pages

body4d Indonesia About Us body4d Casino Account information Access guide