Reference

Privacy Policy for Your badak77 Account

Our Privacy Policy explains what we collect when you open a badak77 account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess requests
badak77 Privacy Policy for Your badak77 Account
ASK ABOUT DATA

Get Help With Privacy Policy Requests

A clear contact route matters when your account record or wallet reference needs attention. Our support path is available from the account and cashier areas, so you can explain whether your request concerns phone verification, a DANA or QRIS receipt, a cookie choice or stored account data. Include the account identifier connected to your request, but do not send a password or full payment credentials. We use the details you provide to locate the relevant record and reply with the next step.

Team online

Account data request

Ask us to locate the personal details connected with your badak77 account. Start from the support path near account access and include your registered phone number or account identifier so we can separate your request from another wallet record.

Wallet record question

If a DANA, OVO, GoPay or QRIS receipt appears different from your account history, send the reference shown in your cashier record. We can explain which details we hold and which processing details remain with the payment provider.

Policy clarification

For a question about cookies, retention, phone verification or access where local law permits, use the same support route and describe the policy point plainly. We will use your account context only to handle the request and avoid asking for unnecessary credentials.

HOW WE HANDLE IT

Privacy Controls Around Your Account

We keep the Privacy Policy practical by linking each data use to an account action you recognise.

Data we receive

We may receive the account details you enter, phone verification results, support messages, device information and activity needed to operate access. A DANA, OVO, GoPay or QRIS reference may also appear when you use that payment route.

Cookies on your device

Cookies can remember a selected setting or help a sign-in path work between pages. You can manage browser storage from your phone or desktop settings, although changing it may remove saved choices and require another account access step.

Account protection

We use phone verification and relevant device signals to help protect account access. Keep your password private and contact support if a sign-in or wallet status does not match your activity; never place full credentials in a message.

Payment references

Our records can show a rail, amount reference and status needed to match a cashier event. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may apply their own data handling terms to the transfer itself.

Retention period

We retain account, support and transaction-related records only for the period needed for the stated account, security, dispute and legal purposes. When a record is no longer needed, our handling follows the applicable deletion or anonymisation process.

Change or access request

You may ask what personal data we hold, request a correction, raise a processing concern or ask whether deletion is available. Send the request through support with enough account detail to verify ownership, and we will explain any lawful limitation.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to check before opening access. We keep the examples tied to the badak77 site, including phone verification, mobile cookies and local wallet references. If your situation is not covered, use the support route beside the account or cashier area and describe the specific record or request.

The badak77 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use those records, how retention works, how security checks support access, and how you can ask about your data where local law permits.

When you open an account, we may receive the details you submit, including a phone number and account identifiers, plus verification results. We can also process device or browser signals and activity connected with access. Do not send passwords or full wallet credentials through support.

Yes, the Privacy Policy explains the account-side payment references we may hold for DANA, OVO, GoPay and QRIS, such as a route and status reference. The wallet or bank provider controls its own processing, so its separate terms may also apply to the transfer.

We may use cookies or browser storage to remember a selected setting and help your account path work between pages. You can manage them in your mobile browser settings. Removing them may clear saved choices and require another phone verification or sign-in step.

You can contact support to ask which personal data is connected with your account, including account identifiers, verification records or cashier references. Include enough detail to confirm ownership, but omit passwords and complete payment credentials. We will explain the available response and any lawful restriction.

We keep account, support and transaction-related records for as long as needed for account operation, security, dispute handling and applicable legal purposes. Retention can differ by record type. When the purpose ends, we follow the relevant deletion or anonymisation process.

Use the support route near account access and state which detail needs correction, such as a phone number or account identifier. We may request account verification before changing it. A correction request does not require you to disclose a password or full DANA, OVO, GoPay or QRIS credentials.