Reference

Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a bosku21 account, use the mobile lobby, or contact support about a wallet status.

Account dataCookie choicesWallet checksContact requests
bosku21 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Help Near Account Access

A clear contact path matters when you want to ask about the Privacy Policy, correct an account detail, or check why a payment reference is attached to your profile.

Policy questions Ask how we collect, use or retain your account details. Include the subject Privacy Policy and the contact detail linked to your bosku21 account so we can route the request correctly.
Wallet references For DANA, OVO, GoPay or QRIS questions, share the transaction reference and approximate date rather than a secret code. We use those details to check payment status without requesting your wallet PIN.
Account corrections If your phone or contact detail is wrong, ask us to review the record through the account support path. We may request a verification step before changing information tied to login access.
DATA HANDLING

What We Do With Your Details

The Privacy Policy is designed around practical account handling rather than broad statements. We limit collection to details needed for access, support, security and payment reconciliation, then use the record to respond…

Account creation

When you open an account, we use the contact details and phone verification result needed to connect you with the correct login. A clear account path reduces duplicate records and helps support locate one profile.

Cookies and sessions

Cookies may keep a session active or remember a setting on your mobile browser. You can clear browser storage, although doing so may require another login and may remove saved preferences from that device.

Payment matching

A DANA, OVO, GoPay or QRIS reference can help match a cashier event to your account. Bank transfer and virtual account records serve the same checking purpose when those routes are selected.

Account security

We may use phone verification, login records and device signals to protect account access. If a sign-in looks unusual, support may ask for account details that confirm ownership before discussing the record.

Retention requests

We retain records only as needed for the stated account, security, support or payment purpose and applicable requirements. Ask us about a particular record, and we will explain the available correction or removal path.

Policy changes

If this Privacy Policy changes, the current page is the place to check the new wording before using account or wallet functions. You can contact support when a change affects your data request or account access.

Privacy Policy Answers For bosku21

These Privacy Policy answers cover the questions we expect before account access: what is collected, why wallet references appear, how cookies work and where to send a request. They also explain the practical steps for correcting a record or asking about retention. If your question concerns availability in Indonesia, remember that access depends on local law.

It covers details connected with account creation, phone verification, login activity, cookies, device signals, support requests and payment references. It explains how we use those details for account access, security, payment checks and contact handling, with service availability subject to local law.

We may handle contact details, account identifiers, phone verification results, login records, cookie choices and relevant device signals. We use these details for a stated account or support purpose, rather than asking for unrelated personal material during a normal access request.

Payment references help us connect a cashier event with the right account and investigate a status question. The same approach can apply to OVO, GoPay, bank transfer or a virtual account. Send a reference, not a wallet PIN or password.

Yes. Contact us through the account support path and identify the record you want corrected, such as a phone detail or contact address. We may request a verification step before changing information that controls login or is linked to payment reconciliation.

Cookies can preserve a session or remember a browser setting while you move from login toward the lobby. Clearing them may sign you out and remove saved preferences. You can then sign in again, while support can explain a cookie-related access issue.

Send a Privacy Policy request with the account contact detail and a precise description of the record. We will explain whether it is still needed for account, security, support or payment handling and outline the available request path for correction or removal.

The policy describes our handling of account and payment data across the service, while access or eligibility depends on local law. If you are in Makassar or another Indonesian location, contact us before account access when you need a location-specific explanation.