Reference

Open bonanza247 Privacy Policy for Your Account

Our Privacy Policy explains what bonanza247 collects when you open an account, sign in, use a mobile browser, or check wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity checks
bonanza247 Open bonanza247 Privacy Policy for Your Account
CONTACT ROUTES

Contact Us About Your Privacy Policy

A direct support request gives you a practical route for privacy questions before or after account opening. Tell us which account step concerns you, such as phone verification, a DANA receipt, or a QRIS status reference, and we can route the request without asking you to repeat unrelated game details. Use the account help path near the cashier area, and keep your registered contact ready.

Team online

Account privacy request

Ask us to explain, correct or locate account data connected with your phone verification step. Include your registered contact, but never send a password or one-time security code.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the transaction reference and date shown in your account so we can identify the correct payment event.

Login data concern

If a mobile or desktop sign-in looks unfamiliar, contact our account support route promptly. We can review the session details and explain the security step needed before access continues.

DATA PRACTICES

Protect Your bonanza247 Account Data

We handle privacy as part of the account flow rather than as a separate promise on a page. Phone verification, session checks and wallet references each have a defined operational purpose.

Account details

We use the details you provide during account opening and phone verification to create your account, support sign-in and connect requests to the correct account record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may produce references and status details. We use those records to trace the payment request you ask about.

Cookies and sessions

Cookies can remember a session on your phone or desktop browser and help us identify unusual sign-in behaviour. Clearing browser data may require you to sign in again.

Security controls

Phone verification and account checks help separate your sign-in from an unfamiliar device. We will not ask you to disclose your password or one-time security code in a support request.

Retention questions

If you want to know how long a particular account, cookie or wallet reference remains, send the request through support with the relevant account step or transaction reference.

Change requests

Where local law permits, you may ask us to correct account details or explain available data choices. We may verify account ownership before making a change.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers cover the account and wallet questions we expect you to ask before opening bonanza247. They explain the records created by local payment rails, browser sessions and phone verification, while keeping the request path clear for Indonesian account holders.

It covers account details, phone verification, sign-in sessions, cookies, payment references and support requests connected with bonanza247. It also explains purposes, retention questions, security checks and available correction requests.

Yes. A DANA or QRIS request can create a payment reference, status record and security signal. We use those details to trace the request and respond when you ask about its account history.

We may collect the details needed for account creation, phone verification, sign-in support and security checks. The Privacy Policy explains why each category is used and how to ask about a specific record.

Cookies can keep a mobile browser session available and help identify unusual sign-in behaviour. If you clear browser data, you may need to sign in again and repeat an account security step.

Where local law permits, you can ask us to correct account details or clarify the purpose of a record. Send the request through support, and we may verify account ownership first.

Use the account support route and include the wallet name, transaction reference and date shown in your account. Do not send your password or one-time security code with the request.

The policy is available for account questions, but service access and eligibility depend on local law. Where local law permits, we can address requests about data use, retention and account corrections.