Reference

bos001 Privacy Policy For Your Account

bos001 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between Live Blackjack Prestige and other lobby areas.

Account dataPayment recordsCookie choicesSecurity steps
bos001 bos001 Privacy Policy For Your Account
HELP WITH DATA

Three Ways To Ask About Privacy

A clear contact route helps you act on this Privacy Policy without searching through unrelated pages.

Account help Use the account help route when you want to ask what personal details we hold, confirm a phone verification record, or request a correction. Include your account identifier so we can separate your request from another account with a similar name.
Cashier path For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, begin beside the cashier path and attach the payment receipt reference. We can then check the recorded status without asking you to send a full wallet password or private access code.
Access request When you ask for access, correction, deletion, or a copy of your records, send the request through the contact route displayed inside your account. We may ask for a verification step before releasing details, protecting the account from an unknown requester.
DATA PRACTICES

Six Privacy Controls Behind bos001

We handle Privacy Policy requests as account operations, not as a general lobby message. Sign-in records help us detect unusual access, while payment references let us reconcile DANA, QRIS, and bank transfer…

Account collection

We collect details you provide during account opening and phone verification, together with sign-in and device signals needed to protect access. If a detail changes, use the account path to request a correction rather than creating a second account.

Payment matching

A DANA, OVO, GoPay, or QRIS payment creates a reference that helps us match the amount and status to your account. Bank transfer and virtual account records serve the same operational purpose, including receipt checks.

Cookie control

Cookies may keep your selected language, sign-in state, or page setting available during a visit. You can remove or restrict them in your browser settings, although some account steps may then ask you to confirm again.

Security checks

We use phone verification and account activity signals to reduce the chance of an unknown person entering your account. If a sign-in looks unusual, an extra account check may be required before private details or wallet status are shown.

Retention records

We retain account, support, and payment records only for the operational, legal, and dispute-handling periods that apply to the service. When a record is no longer needed for those purposes, our handling process moves it toward removal or restriction.

Change requests

You can ask us to access, correct, restrict, or remove eligible personal details through the contact route in your account. We may request identity confirmation and explain if a payment or legal record must remain available.

Privacy Policy Answers For Account Holders

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain wallet records, device cookies, account access, and requests for changes in plain language. If your question concerns a particular DANA, QRIS, or bank transfer reference, use the account help route with that reference ready.

The bos001 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages, and payment references. It explains why we use each category, how we protect access, and how you can request a copy, correction, restriction, or removal where applicable.

Yes. Privacy Policy covers the transaction reference, status, and account match connected with DANA and QRIS. We use those records to check whether a payment was received and to answer receipt questions. Do not send your wallet password or private security code through support.

Phone verification helps us connect the person opening an account with the account record and helps reduce access by an unknown person. The verification result may be retained with account security records. If your phone detail is wrong, request a correction through account help.

You can request access to eligible account data through the contact route shown inside your account. Tell us which records you need, such as sign-in details, support messages, or payment references. We may complete an identity check before sending private data to the requesting account holder.

Send a correction request through account help and identify the field that needs changing, such as your phone detail or contact record. We may ask you to complete phone verification before updating it. Payment and security records can require an additional explanation when they cannot be edited.

Retention depends on why a record exists. Account security, payment matching, support handling, legal duties, and dispute checks can require different periods. Our Privacy Policy does not treat every record alike; when a record is no longer needed, we move it toward removal or restriction.

Ask through the account help route if you want to know how cookies relate to your bos001 visit. You can also clear or restrict cookies in your phone browser settings. After that change, sign-in and verification pages may ask you to confirm selected settings again.