Reference

badai77 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a badai77 account, use the mobile lobby, or check a wallet status through DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesSupport access
badai77 badai77 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route helps when a Privacy Policy question concerns a login, phone check or wallet receipt. We ask you to contact support from the same account where possible, because that lets us compare your request with the relevant session or payment reference without exposing another person’s data. If you are in Makassar or elsewhere in Indonesia, use the available support channel shown in your account and include only the details needed to locate the case.

Team online

Account request

Ask us to access, correct or clarify personal data linked to your badai77 account. Include your registered phone number, the request type and the approximate date of the account event so we can verify ownership before replying.

Wallet receipt

For a DANA, OVO, GoPay or QRIS privacy question, send the payment reference and status shown in your account rather than a wallet password or full security code. We use the receipt trail to locate the relevant record.

Login concern

If a browser session or Mobile APK Download path appears unfamiliar, tell support the device type, sign-in time and affected account step. We can review the access event and explain what security data was recorded.

DATA HANDLING

What Your Privacy Policy Covers

Privacy Policy choices affect more than a sign-in form: they also cover cookies, device signals, account security and records created when you check payment status.

Account details

We handle the phone number and account details you provide for account creation, phone verification and account recovery. Before disclosing or changing those details, we may ask you to confirm account ownership through the registered contact path.

Device sessions

Browser and phone signals help us identify a session, protect account access and investigate an unfamiliar sign-in. The same approach applies when you move from a desktop browser to the mobile lobby or Mobile APK Download path.

Cookie controls

Cookies can keep a session active, remember selected settings and help us detect unusual access. Your browser provides controls for clearing or blocking them, although some account steps may ask you to sign in again afterward.

Payment records

A DANA, OVO, GoPay or QRIS reference lets us match a cashier request with its status. For BCA, BRI, Mandiri or BNI bank transfer records, we use the reference and status needed for reconciliation, not your banking password.

Retention timing

We keep records only for the period needed for account security, payment reconciliation, support handling and applicable legal duties. When a retention reason ends, we remove, anonymise or restrict the record where that action is available.

Change requests

To request access, correction or an eligible deletion, contact support from your account path and describe the data involved. We may request a phone verification step, then explain the result, any limits and the next available route.

Privacy Policy Answers For badai77

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep the process practical: identify the account, describe the record and use the support path shown in the lobby. If a request concerns local availability or eligibility, the outcome depends on local law.

It covers account details, phone verification, device sessions, cookies, payment references, support cases and retention. It explains how we use those records to protect access, reconcile DANA, OVO, GoPay, QRIS or bank transfer activity, and respond to requests about your personal data.

We may collect the details you enter for an account, your registered phone number, verification results, device and browser signals, session events, payment references and support messages. We use only the data needed for account access, security, payment matching and service handling.

Yes, you can request access to eligible personal data linked to your account. Contact support from the account path, provide your registered phone number and describe the records you want. We verify ownership first and explain any restriction that depends on local law.

Send a correction request through the support route connected to your account. State which detail is wrong and what it should say. We may use phone verification before changing it, especially when the correction affects login, account recovery or a wallet receipt.

Yes. We record the reference and status needed to match a DANA, OVO, GoPay or QRIS request with your account. We do not need your wallet password. For a payment query, share the receipt reference shown in the cashier path.

Cookies can maintain your session, remember settings and help detect unusual account access. You can clear or block them through your browser controls. After that, the account may ask you to sign in again or repeat a phone verification step.

Retention varies by the record and its purpose. We keep account, security, payment and support records while needed for those purposes and applicable legal duties. You can ask support about a specific record, and we explain whether removal or restriction is available.