Reference

barus4d Privacy Policy Explained

barus4d Privacy Policy shows what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account dataWallet recordsDevice sessionsCookie choices
barus4d barus4d Privacy Policy Explained
PRIVACY HELP DESK

Three Ways To Ask About Privacy

A clear contact path matters when your account data needs attention. Use the support route connected to your account and describe whether your request concerns phone…

Access request Ask us which personal details are linked to your barus4d account and how those…
Correction request If your contact detail or account record is inaccurate, send the specific field that…
Privacy question For questions about cookies, device recognition, retention or a payment reference, tell us the…
DATA HANDLING MAP

Six Privacy Controls We Explain

We describe our Privacy Policy in practical terms because your account activity creates different types of records.

What we collect

We may receive account details you enter, phone verification results, sign-in events and device or browser signals.

Why we use it

We use account and session data to provide access, identify unusual sign-in activity, answer support requests and reconcile wallet status.

Cookie choices

Cookies and similar browser storage can remember session settings and help us understand whether a request comes from an active…

Account security

Phone verification, sign-in records and device signals help us protect your account from unauthorised use.

How long records stay

We retain records for as long as needed for the purpose described in our Privacy Policy, account support, security checks…

Your request route

You can ask about access, correction or deletion of eligible personal data through the account support path.

Privacy Policy Questions About barus4d

These Privacy Policy answers address the questions we expect before account creation or a wallet transaction. They cover the data created by sign-in, phone verification, device use and local payment references. If your situation is not covered, contact us through the account support path and describe only the record you want us to check.

The barus4d Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains why we use those records, how security checks work, how retention applies and how you can request access or correction where local law permits.

Yes. Our Privacy Policy covers the account-side references created when you use DANA or QRIS, such as a status or transaction identifier. The relevant payment provider may keep separate records under its own terms, so do not send wallet passwords or one-time codes to us.

You can request a correction through the account support path by naming the inaccurate field and the account contact used for phone verification. We may confirm your identity before making a change, especially when the record connects to GoPay, OVO, bank transfer or virtual account activity.

The Privacy Policy allows us to use device and browser signals to maintain a session, recognise unusual sign-in activity and protect your account. Clearing browser storage can remove preferences and may require another sign-in. Contact us if you see a device session you do not recognise.

We keep each record for the period needed for its stated purpose, account support, security checks or applicable legal requirements. An account field, a support message and a QRIS or bank transfer reference may follow different retention periods, which we can explain in response to your request.

You may ask us to delete eligible personal data through the account support path. We first verify the request and check whether a record must remain for security, support or legal reasons. Where local law permits, we will explain the result and any records that cannot be removed.

Yes. Account access and eligibility depend on local law, and our Privacy Policy is applied where local law permits. If you contact us about access from Indonesia or another location, include the relevant account context rather than sending sensitive credentials so we can address the correct policy question.