Reference

boboslot Privacy Policy for Indonesian Accounts

boboslot Privacy Policy explains how we collect, use and protect the account, device and wallet details connected with your access.

Account dataWallet recordsDevice accessCookie choices
boboslot boboslot Privacy Policy for Indonesian Accounts
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route matters when a phone number, wallet reference or device record looks unfamiliar.

Account access If phone verification or sign-in creates a privacy concern, contact us through the account support path. Tell us which device you used and the account detail affected; we can check the matching record without asking for your password.
Wallet status For a DANA, OVO, GoPay or QRIS record, share the payment reference and visible status from your account. We use that reference to trace the event and avoid requesting wallet credentials or a complete card-style secret.
Privacy request To ask for access, correction or removal, identify the account contact and describe the requested change. We may need a phone verification step before acting, so another person cannot alter or receive your account data.
DATA PRACTICES

How We Handle Mobile and Table Data

Privacy controls should fit the way you actually reach the lobby, whether you sign in on an Android browser, an iPhone browser or a desktop device.

Account records

We use your registration contact, phone verification result and sign-in history to maintain the correct account. These records help us detect an unfamiliar login and respond when you ask about access to your profile.

Device signals

A mobile browser may send device type, browser details and basic session signals when you open the lobby. We use these details to keep a session working and investigate unusual access, not to read files stored on your phone.

Cookies

Cookies can keep your session connected and remember choices made in the account area. You can manage browser cookie settings, though blocking required cookies may interrupt sign-in, phone verification or the privacy link.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain references, status and timestamps. We use these records to match a transaction with your account without holding a wallet PIN.

Security checks

We may ask you to confirm the phone or email linked to your account before releasing account data or changing it. This step helps prevent an unrelated person from making a privacy request on your behalf.

Retention and changes

We keep records only for the period needed for account support, transaction matching, security checks and legal duties. Ask us to correct or remove eligible data through the privacy route, and we will explain any required exception.

Privacy Policy Answers for boboslot

These Privacy Policy answers address the searches we hear most often from people checking boboslot before opening an account. They cover the data connected with sign-in, mobile access, cookies, payment references and account requests. If your situation is different, use the privacy contact route with the account detail and event date available to you.

It covers account registration, phone verification, sign-in activity, mobile browser signals, cookies, support messages and payment references. It also explains how we use DANA, OVO, GoPay, QRIS, bank transfer and virtual account status when matching an event to your account.

No. Our Privacy Policy distinguishes a payment reference or status from a wallet secret. When you use DANA or QRIS, we may receive confirmation details needed to match the transaction, but you should never send us a wallet PIN or password.

We may collect the contact details you submit, the result of phone verification, sign-in and session records, device or browser signals, support messages and transaction references. The Privacy Policy explains the purpose of each category and how to ask about a specific record.

Use the privacy contact route from your account area and identify the phone or email linked to your profile. State whether you want access or correction, then describe the record. We may complete a phone verification step before releasing or changing account data.

Cookies may connect your mobile browser session, remember a selected setting and keep the account area available during navigation. You can adjust browser controls, but blocking required cookies can affect sign-in, phone verification and access to the policy link.

We retain payment references, timestamps and status for the period needed to match account activity, answer support requests, protect access and meet applicable legal duties. A deletion request can be submitted through the privacy route, and we will explain records that must remain.

Yes, privacy questions can be sent through the account support path, while access or eligibility depends on local law. Include your linked contact, device if relevant and event date. We will explain the available request process without asking for your wallet PIN.