Reference

barus4d Terms & Conditions

barus4d Terms & Conditions set the rules for opening, using and closing your account in Indonesia.

Account access rulesWallet record dutiesPolicy changes
barus4d barus4d Terms & Conditions
HELP WITH TERMS

Contact Paths For Policy Questions

A clear support path helps you resolve a Terms & Conditions question before it affects account access.

Account access If your phone verification does not complete, contact our account support desk through the…
Wallet status For a DANA, OVO, GoPay or QRIS question, send the payment reference and receipt…
Policy request You can ask us to clarify a clause, request a copy of the current…
ACCOUNT SAFEGUARDS

How We Apply These Rules

Our policy handling is designed to keep account decisions traceable rather than surprising.

Data handling

We use account details, registered phone data and payment references for access checks, support handling and transaction reconciliation.

Cookies and sessions

Cookies can keep a mobile or desktop session working between account pages.

Login security

Your password and verification details remain your responsibility.

Record retention

We retain account, payment and support records for the period needed to operate the service, resolve disputes and meet applicable…

Changing your details

If your phone, payment ownership or other account detail changes, contact us before using the changed detail for a wallet…

Access decisions

Eligibility and access depend on local law. We may restrict a feature, request further account checks or decline access where…

Terms & Conditions Questions Answered

These Terms & Conditions questions focus on the account decisions people usually want to understand before opening barus4d access. We keep the answers practical: what you submit, how a payment record is matched, when a session may require another check and how to ask for a correction. If your situation is not covered, contact support through the registered account route with the relevant reference.

You must provide accurate account details, keep your registered phone available and complete the requested verification step. Use an account and payment method that belong to you. Access depends on local law, so we may decline or pause access where local law permits.

Those local payment rails may be available when shown in your account. The payment reference and account details must match, and you should keep the receipt. If a wallet status differs from the account record, contact support before sending another request.

A new device, cleared cookies, closed session or unusual login can trigger another phone check. We use it to connect the active browser with your account. Complete the prompt from your registered phone, or contact support if the code does not arrive.

Contact support from the registered account route and identify the detail that needs correction. Include the relevant date or payment reference, but do not send your password. We may ask for additional verification before changing a phone, payment or personal record.

We compare the payment reference, account identity and status supplied by the relevant rail. DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests can remain under review while a mismatch is checked. Keep your receipt for support.

Yes. We may restrict access when details conflict, security activity requires checking or a legal condition applies. Eligibility depends on local law, and access may be declined where local law permits. Support can explain the status without bypassing the required check.

Use the registered account support route and state whether your request concerns account data, browser cookies, payment records or support history. Give a date or reference where possible. We will confirm the request and explain the available correction or access process.