Reference

barong4d Privacy Policy for Your Account

The barong4d Privacy Policy tells you what we collect when you open an account, check DANA or QRIS status, and move between the lobby and your phone.

Account dataWallet recordsDevice controlsPolicy requests
barong4d barong4d Privacy Policy for Your Account
POLICY HELP

Switch To Our Privacy Support Path

A privacy question should not get lost beside a wallet request. We route account, device and data questions through the support path shown on our site, so you can identify the relevant account before asking us to check a record. In Yogyakarta or elsewhere in Indonesia, include your registered phone number and the subject of your request, but never send your password or wallet PIN.

Team online

Account access

Use the account support route when you cannot reach your profile or need to confirm which phone number is attached. We may ask for an account step before discussing private records.

Wallet records

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and approximate date through our support path. We use those details to locate the correct payment entry.

Privacy request

Ask us to access, correct or remove eligible account data through the policy contact route. We check ownership first, then explain any legal or security reason a request needs limits.

DATA CONTROLS

Browse Our Account Data Practices

We keep this policy practical by connecting each data use to an account action: login, phone verification, wallet matching or security review.

Collection

We collect account details you enter, verification results, wallet references and basic device signals. For example, a QRIS status check may be linked to its reference, time and account so we can trace the request.

Cookies

Cookies and similar browser storage can keep your session working and remember security settings. You can clear them through your browser, although doing so may require phone verification before account access returns.

Security

Login events, failed attempts and device changes help us detect unusual account access. We do not ask you to disclose a password, PIN or one-time verification code in a support message.

Retention

We keep account and transaction records for the period needed to operate the service, investigate security events or meet legal duties. When that need ends, we delete or separate the record where practical.

Your requests

You may ask what eligible data we hold, request a correction or ask about deletion through the policy contact route. We verify account ownership before changing a phone, login or transaction record.

Sharing

We share only the records needed with payment or service partners handling a requested action, such as matching a bank transfer. We do not provide your private account details for unrelated requests.

Open Answers About Privacy Policy

These answers address the policy searches we receive most often, including account access, Indonesian wallet records and requests to change stored details. If your situation is unusual, use the policy support route and describe the exact record or device involved. We can then check the correct account without asking you to post private credentials.

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

We use your phone number to create and protect the account, complete required verification and identify the correct profile when you request help. We do not need your password or wallet PIN for support.

Yes. The Privacy Policy covers QRIS, DANA, OVO and GoPay references linked to your account, plus bank transfer or virtual account details needed to match a payment status or resolve a receipt question.

You can ask for access to eligible account data through the policy contact route. We first verify that you control the account, then explain the available record and any lawful reason for limited access.

Send a correction request through our support path and identify the affected account field, such as your phone number. We confirm ownership before changing it, which helps prevent another person from taking over access.

We retain personal and transaction records while they support account operation, security checks or legal duties. After that need ends, we remove the record or reduce its link to your account where practical.

Yes. Access and eligibility depend on local law. The Privacy Policy applies to your use of the site where local law permits, and our support route can clarify a policy question without promising access.