Reference

Privacy Policy for Your bodana4d Account

bodana4d Privacy Policy explains how we handle the details you provide when you open an account, access the lobby, or check DANA, OVO, GoPay and QRIS status.

Clear data purposesWallet status contextAccount access steps
Explore Our Lobby Read FAQ
bodana4d Privacy Policy for Your bodana4d Account
HELP WITH YOUR DATA

Get Privacy Policy Help Without Guesswork

Questions about the Privacy Policy should reach us through the account support route rather than through a public message. Include the phone number or account identifier connected to your profile, the device path you used, and the specific request you want us to handle. For a wallet question, add the DANA, OVO, GoPay or QRIS reference visible in your account without sending a password or verification code.

Team online

Account support

Use the signed-in account help path for a Privacy Policy question, identity correction or access request. We can match your message to the account record and explain which details support phone verification or sign-in protection.

Wallet records

If your request concerns DANA, OVO, GoPay or QRIS activity, mention the payment rail and date shown in your cashier history. We use that context to locate the relevant record without asking you to disclose a password.

Access concerns

When a device or browser no longer reaches your account, contact support through the available account route and describe the login step that stopped. We can direct a privacy question separately from a security check.

DATA HANDLING DETAILS

How We Keep Policy Requests Clear

We designed this Privacy Policy around the moments that create real questions: account creation, phone verification, mobile access, wallet status and requests to change stored details.

Account details

We use the details linked to your account to provide access, associate activity with the correct profile and respond to your Privacy Policy requests. Keep your phone number current so we can distinguish your request from another account.

Phone verification

Phone verification supports account access and helps us check that a privacy request comes from the account holder. We do not need your password or one-time code in a support message.

Cookies

Cookies may remember a session choice or help us understand whether a login page is functioning. You can manage browser cookie settings, though changing them may affect access to account pages.

Device signals

A mobile browser, desktop browser or other device can create technical access signals such as browser and session details. We use these signals to investigate unusual sign-in behaviour and protect account data.

Retention

We retain account, payment-status and support records for the period needed to operate the service, address disputes, maintain security or meet applicable requirements. A retention question can be sent through account support.

Policy changes

If this Privacy Policy changes, we will present the updated wording on the policy page. To request a correction, access copy or deletion where local law permits, state the request clearly and identify your account.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account decisions you may make before opening access or while using a mobile browser. We cover the information connected to sign-in, phone verification, cookies, wallet records and support requests. If your question involves eligibility or access, the answer depends on local law; send the account-specific details through the support route so we can address your situation directly.

The bodana4d Privacy Policy covers information connected to account creation, phone verification, sign-in, device access, cookies, wallet status and support messages. It also explains how we use records for security, service operation, dispute handling and requests to correct or remove data where local law permits.

Phone verification helps us connect an account request to the correct account holder and protect access from unusual sign-in attempts. It may be used when you open an account or ask about stored details. Do not send your password or verification code to support.

Yes. The Privacy Policy covers payment-status information displayed for DANA, OVO, GoPay and QRIS, as well as bank transfer or virtual account references when connected to your account. Send only the rail, date and account context needed to locate a record.

We may use cookies to keep a selected session active and help diagnose an account page that does not load correctly. Your browser settings can control cookies, but blocking them may interrupt sign-in or require you to repeat an account step on mobile.

You can request access to, or correction of, information linked to your account through the account support route. Include your account identifier and describe the exact field or record. We may confirm ownership through phone verification before processing the request.

We keep information for as long as it is needed for account operation, security checks, payment-status queries, dispute handling or applicable requirements. If you ask about a particular record, identify its account and date so we can explain the relevant retention context.

You can submit a deletion request through account support, and we will assess it where local law permits. Some records may need to remain for security, dispute or legal reasons. We will explain the result and any limitation linked to the request.

Related Pages

bodana4d Indonesia FAQ Live Baccarat Table About Us Bundesliga Over Under