Reference

bos868 Privacy Policy For Your Account

bos868 Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and browse from a mobile device in Surabaya or…

Account and phone checksWallet activity recordsCookie and device choicesClear contact route
bos868 bos868 Privacy Policy For Your Account
CONTACT PATH

Privacy Help Beside Your Account

A clear contact path matters when a privacy question appears beside a login or wallet status issue. We ask you to contact support from the account area and include the phone number linked to your account, the relevant date, and a payment reference where one exists. Do not send a password, wallet PIN, or full bank credentials. We use the submitted details only to locate the request and verify that it concerns your account.

Team online

Account request

Ask about your Privacy Policy rights from the account support path. Include your verified phone number so we can match the request without asking for your password or wallet PIN.

Wallet status

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the payment reference and date. We can investigate the stored status without requesting private wallet credentials.

Correction request

If your name, phone detail, or account record needs correction, state the field and the accurate replacement. We may request an account check before changing personal data.

DATA PRACTICE

Your Data Choices Across Devices

We keep privacy controls close to the account flow rather than hiding them in general site copy.

Account details

We use your account name, phone number, and verification result to create and protect access. Phone verification is an account step, not permission to request your wallet PIN or banking password.

Payment references

A cashier record may contain the rail, amount instruction, reference, and status for DANA, OVO, GoPay, QRIS, or bank transfer. We do not need your private wallet login to reconcile that record.

Device signals

Your mobile browser may send device type, browser version, language, and security signals. These help us recognise abnormal sign-in behaviour while keeping the mobile path available on Android and iPhone.

Cookies

Cookies can keep a session connected, remember a selected setting, and help us detect suspicious sign-in patterns. You can adjust browser cookie controls, although some account functions may then need another sign-in.

Retention

We retain account, security, and transaction records for as long as needed for the stated purpose, dispute handling, and lawful obligations. You can ask which category applies to a particular record.

Policy requests

To request access, correction, deletion where available, or a processing explanation, contact us through the account support path. We verify the requester first and answer within the period required by applicable law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account, wallet, browser, and contact questions you may have before opening access. We keep each answer tied to a practical step, from phone verification to a DANA reference, so you know what to send and what we can explain. Where a request depends on local rules, we will identify that point directly.

It covers account creation, phone verification, sign-in, support contact, cashier records, device signals, cookies, security events, and retention. It applies to our website and mobile-browser access where local law permits.

We may collect your account name, phone number, verification result, browser and device signals, support messages, and payment references. We collect only the details needed for access, security, payment status, or lawful duties.

No. Our Privacy Policy treats DANA, OVO, GoPay, and QRIS as payment context and status records. We do not ask for your wallet password or PIN to investigate a cashier reference.

Open the account support path and request access to your data. Include your verified phone number and the category you want checked. We may verify ownership before disclosing or changing account records.

Yes, you can request a correction and ask whether deletion is available for a specific record. Some security, transaction, or legal records may need retention, and we will explain the reason.

On Android and iPhone browsers, we may process device type, browser version, session signals, and cookie choices. These details support sign-in security and session continuity without requiring a separate app.

Use the account support route and describe the concern, date, and relevant reference. Never include a password or wallet PIN. We will verify the request, locate the record, and explain the next step.