Reference

baru 01 Privacy Policy For Your Account

The baru 01 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, browse Blackjack or Fish Hunter, and use…

Clear data purposesWallet record contextAccount contact route
baru 01 baru 01 Privacy Policy For Your Account
HELP PATHS

Ask About Privacy Near Account Help

A direct question is easier to resolve when you include the account step or record involved.

Account help route Open the account help path and describe the Privacy Policy question in your own…
Wallet record query For DANA, OVO, GoPay or QRIS questions, provide the visible reference, date and status…
Access concern If your phone or desktop sign-in looks unfamiliar, tell us the device path and…
DATA PRACTICE

What We Do With Your Account Data

Privacy is handled through practical account controls rather than broad promises. We limit collection to records that help create, protect and maintain your account, then explain the reason…

Account details

We use your phone number and account details to create the correct sign-in path, confirm an account-access request and keep…

Cookies and devices

Cookies can keep a sign-in session and selected page settings working on your mobile browser or desktop.

Payment references

A DANA, OVO, GoPay or QRIS reference helps us match a wallet status with your account.

Account security

Before discussing a private account record, we may ask for an account step such as phone verification.

Retention choices

We keep records only for the period needed for the purpose described in this Privacy Policy, including account security and…

Request changes

Send a clear request through our support route if your phone detail is wrong, your cookie preference needs attention or…

Privacy Policy Questions About baru 01

These Privacy Policy answers address the questions we expect before you open an account or connect a local wallet. They cover the records created by sign-in, browsing and payment status checks, plus the practical route for asking us to correct or explain something. If your situation is not listed, use the account help path and identify the relevant record without sharing a password.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with your account. It explains why we use those records, how retention works and how you can ask about correction, deletion or a collection purpose.

We use the phone number to create your account path, support account access and complete a verification step before discussing private records. If the number is incorrect, contact support through the account help route; we may verify ownership before changing it.

Yes. The policy covers the DANA or QRIS reference, status, amount and time connected with your account activity. It does not replace the wallet provider's own terms, and we do not need your wallet password to match a receipt or status.

We may retain the OVO or GoPay reference and the bank transfer or virtual account status needed to reconcile an account entry. These records help us explain a pending or duplicated status. The relevant provider separately handles its own account data.

Use the support route linked from account help and state whether you want a correction, purpose explanation or deletion request. Include the affected account detail, but do not send a wallet password. Where local law permits, we will explain the available next step.

Retention depends on the purpose described in the Privacy Policy, such as account security, support history or payment reconciliation, and may depend on local law. Ask support about a specific record, its purpose and whether removal is available after that purpose ends.

Yes. Tell support whether you used a mobile browser or desktop and describe the sign-in or page-setting issue. We can identify the relevant cookie category or device record and explain its purpose. Access and any available request depend on local law.