Reference

Privacy Policy for boz388 Indonesia Accounts

Our boz388 Privacy Policy explains what account, device and wallet data we collect, why we use it and how you can ask for changes.

Account dataWallet recordsCookie choicesContact path
boz388 Privacy Policy for boz388 Indonesia Accounts
HELP CHANNELS

Contact boz388 About Your Privacy Policy

A clear contact route helps when you want to ask what data we hold or why a wallet record appears in your account history. Send the relevant phone number, date and reference without sharing your password or one-time code. We use the account path, payment reference and device context only to locate the request and respond through the available support channel.

Team online

Account access

Use our support chat when phone verification, a login record or a device session needs clarification. Include your registered number and approximate time so we can locate the relevant account event.

Wallet status

For DANA, OVO, GoPay, QRIS or bank transfer questions, send the transaction reference and status shown in your account. Never include your wallet PIN, password or one-time code.

Privacy request

Ask through the account message path to access, correct or question personal data. We may request phone verification before discussing records, helping us avoid sharing account details with the wrong person.

DATA PRACTICE

Data Choices Across Your Account Path

We keep this policy practical by separating account access, transaction matching and product-use records.

Collection purpose

We collect account details to create access, verify a phone number and answer support requests.

Device signals

Browser type, device markers and login times can help identify an unfamiliar session.

Cookie controls

Cookies can keep a session available and remember selected settings.

Account security

Keep your password and one-time code private, and sign out from shared devices.

Retention approach

We retain account, support and transaction references only for the period needed for service operations, dispute handling and legal duties.

Change requests

You can request access, correction or deletion of eligible personal data through support.

Privacy Policy Questions About boz388 Data

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain wallet records, cookies, device activity, account requests and local access in direct terms. If your situation is not covered, contact us through the privacy request path and include only the minimum account detail needed to identify your case.

The boz388 Privacy Policy covers account details, phone verification, login and device events, support messages, cookies and transaction references connected with DANA, OVO, GoPay, QRIS or bank transfer activity.

We use your phone number to create and protect account access, complete verification and match a support request to the right record. We do not need your wallet PIN or one-time code.

Yes. Our Privacy Policy explains how we may use DANA and QRIS references to match an account transaction, check a status and answer a support request. The payment provider keeps its own records.

Send a privacy request through the account message path with your registered phone number and the data category you want. We may complete phone verification before releasing account-linked records.

You can ask us to correct inaccurate data or delete eligible records through support. We assess the request under applicable rules, and some payment, dispute or legal records may need continued retention.

Cookies can store a session and selected browser settings. You can clear or restrict them through your device browser, but doing so may sign you out or require phone verification again.

Yes. Account access and eligibility depends on local law. Where local law permits, we use the account and device details described in this Privacy Policy to provide access and handle support requests.