Reference

boss01 Privacy Policy Explained Clearly

The boss01 Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Live Baccarat Turbo or use DANA and QRIS.

Account dataCookie choicesPayment recordsRequest changes
boss01 boss01 Privacy Policy Explained Clearly
CONTACT ROUTES

Get Privacy Help Near Your Account

A clear contact path helps you ask about the Privacy Policy without searching through the lobby.

Account support link Send a Privacy Policy question from the support route connected to your account.
Payment record query For DANA, OVO, GoPay or QRIS questions, add the transaction reference and approximate time.
Access correction request If your account detail, device record or contact address appears wrong, tell us what…
DATA PRACTICES

How boss01 Handles Privacy Requests

Privacy is handled through practical account controls rather than a hidden process. We separate login and payment checks, record security events when a sign-in or phone verification occurs…

Account details

We use the contact details you submit to create and maintain your account, send account-related messages and complete the phone…

Device signals

A phone or desktop session may produce device type, browser, time and security-event records.

Cookie controls

Cookies can keep your session active, remember a selected setting and help us understand whether a policy message was displayed.

Payment matching

When you use QRIS Verify Steps, DANA, OVO, GoPay or bank transfer, we retain references and status details needed to…

Retention timing

We keep each category only for its operating purpose, account-security need or applicable legal duty.

Your requests

You can ask what account data we hold, request a correction, question a payment record or ask about deletion through…

Privacy Policy Questions Before Opening

These Privacy Policy answers focus on the account steps you are most likely to check before opening access. They explain payment records, cookies, device activity, corrections and contact routes in plain English. If your question concerns a particular DANA, OVO, GoPay or QRIS reference, include that reference when you contact us. Account access remains subject to local requirements and depends on local law.

The boss01 Privacy Policy covers account contact details, phone verification records, device and browser signals, login events, cookie activity and payment references. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we record status details needed to match activity to your account.

Phone verification helps connect a person to the correct account before access and supports account recovery or security checks. We use the submitted number for account operations and do not treat verification as permission to request your wallet password, full payment PIN or unrelated phone content.

Yes. The Privacy Policy covers references, timestamps and status information for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These records help us match a receipt to your account; they do not give us access to your private wallet credentials.

Yes. Send a correction request through the account support link and identify the detail that appears wrong, such as your contact number or email address. We may confirm your identity before changing it, because an incorrect edit could affect phone verification and future account access.

Cookies can maintain your login session, remember a setting and record whether a policy message was displayed. You can adjust cookie controls in your browser. If you block required cookies, some account functions may not keep your session or may ask you to sign in again.

We keep records for the operating purpose described in the Privacy Policy, for account security, or for a legal duty that applies. When the reason ends, we may delete, anonymise or restrict the record. Retention can differ by data type and depends on local law.

Use the support route connected to your account and state whether you want access to a record, a correction, a payment-reference check or a deletion request. Include your registered contact detail and relevant transaction reference, but do not send a wallet password or payment PIN.