Reference

badai777 Privacy Policy Explained

The badai777 Privacy Policy tells you what we collect during account opening, why we use it, and how you can ask for access or changes.

Account clarityWallet recordsCookie choicesRequest access
badai777 badai777 Privacy Policy Explained
PRIVACY HELP DESK

Where To Send A Privacy Request

A clear contact route matters when an account record looks wrong or a wallet reference needs explanation.

Account contact route Open the support contact path from your signed-in account and select the privacy subject.
Payment reference check For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, share the transaction…
Access request details Ask to access, correct, or remove personal data through the displayed support route.
DATA HANDLING

Cookies, Devices And Account Records

We handle privacy through practical account controls rather than broad promises. Your sign-in session, phone verification step, device type, and cookie choices can affect how the lobby opens on mobile or desktop.

Account details

When you open an account, we collect the details needed to create access and connect your phone verification step with the correct account record. You should keep those details accurate.

Device signals

A mobile browser or desktop session can produce device and session signals. We use them to recognise unusual sign-ins, maintain the lobby session, and investigate account access concerns.

Cookie settings

Cookies can remember necessary sign-in and preference settings. Where optional controls are shown, you can adjust them through your browser or the cookie setting provided on the page.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records are handled as transaction references. We use them to reconcile status and do not ask for your wallet password.

Retention approach

We keep account, security, and transaction records only for the operational or legal period that applies to them. A deletion request may not remove records required for those purposes.

Changing your details

If your phone number or account detail needs correction, contact us through the signed-in support route. We may check ownership first, then update the record where the request is valid.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account questions you may have before opening access or sending a request. We keep the wording tied to actual account steps, device use, cookies, and payment references so you know what to prepare. If your question is not covered, use the support contact route displayed after sign-in.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification helps connect you with the correct account and reduce mistaken or unauthorised access. We use the resulting record for account control and request handling, subject to local requirements.

Yes. A mobile browser can send device and session signals used to maintain sign-in, detect unusual access, and keep necessary settings working. The same approach applies when you use desktop access.

We use DANA and QRIS references to match a transaction, check its status, and respond to a receipt question. We do not need your wallet password to investigate that reference.

You can ask for access through the support contact route shown inside your account. We may verify ownership before sharing records and will explain any material that cannot be supplied.

Send a correction request through the signed-in support path and identify the affected account detail. We may request a verification step before changing phone, identity, or contact records.

You may request deletion through support, but some account, security, or payment records may need to stay for an operational or legal period where local law permits.