Reference

Privacy Policy for Your barong4d Account

Our Privacy Policy explains what data we collect when you open a barong4d account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet checksCookie choicesAccess depends on local law
barong4d Privacy Policy for Your barong4d Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support route helps you ask about the Privacy Policy without sharing more than necessary. When your login or wallet status stalls, contact our available support route from the account area and describe the request in plain English. You can ask which data is linked to your account, why a device check appeared, or how to correct a phone number. For a DANA or QRIS receipt, include the reference shown in your account rather than sending a wallet password.

Team online

Account data request

Ask us to locate the personal data connected with your barong4d account. We may request the registered phone number and an account confirmation step before disclosing details, so another person cannot use a casual message to access your records.

Wallet privacy check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference through the available account support route. We use the reference to investigate status without asking you to reveal your wallet password or private wallet access code.

Correction or deletion

You can ask us to correct inaccurate personal details or request deletion where the law allows it. We first confirm account ownership, explain any records we must retain, and tell you what happens to access while the request is being handled.

DATA HANDLING

What We Do With Your Account Details

Your Privacy Policy rights work alongside practical account controls. We separate sign-in details from payment references where our operational process allows, limit access to staff who need it for account support, and…

Account collection

When you create an account, we may collect your name, phone number, login credentials and verification details. We use them to establish the account path and confirm that a request comes from you before changing access or responding to a personal data request.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references such as amount, time, status and a transaction code. We use those records to match a cashier event, check a receipt and resolve an account query without storing your wallet password.

Device behaviour

A phone or desktop browser may send device and connection signals when you sign in. These signals help us recognise an unusual login or protect an account change. They are not a reason for you to share your screen, wallet PIN or private login code.

Cookies on your browser

Cookies can keep a session active, remember a language or connect your return from the login page to the lobby. Your browser can block or remove them, although doing so may require another sign-in and can affect account-area functions.

Retention and removal

We keep personal data only while it serves account operation, security, dispute handling or a legal requirement. When you request removal, we assess which records can be deleted and which transaction or access records must remain for a defined operational or legal reason.

Security contact

If you suspect that someone accessed your account, contact the available support route promptly and ask for a security check. Do not include a wallet PIN or full password. We may pause an account change until your phone and account ownership are confirmed.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening an account or linking a local wallet. They explain what we collect, how device and cookie data work, and which account step we use before changing personal details. Access remains where local law permits.

The barong4d Privacy Policy covers data collected through account opening, sign-in, cookies, device access, support requests and wallet references. It explains how we use that data for account access, security, payment status checks and lawful records, including activity connected with DANA and QRIS.

We use your phone number to create and verify the account path, help confirm ownership during a support request and protect changes to login details. If the number is wrong, request a correction through support. We may verify the request before changing the account record.

Yes. The Privacy Policy covers payment references created when you use DANA, OVO, GoPay or QRIS, such as a transaction code, time and status. We use those references to match account activity and investigate a receipt. We do not need your wallet password for that check.

Cookies can remember a session, language preference or route from login to the account area. We may also use device signals to identify unusual access. You can remove or block cookies in your browser settings, but you may need to sign in again afterward.

Where local law permits, you can ask us which eligible personal data is linked to your account and request a copy. Send the request through the available support route. We may ask for your registered phone number and an ownership check before releasing personal details.

Use the account support route to request a correction or deletion. Tell us which detail needs changing and provide the registered phone number for verification. We assess the request under applicable rules and explain if a payment or security record must be retained.

We retain data for as long as it supports account operation, security checks, payment queries, dispute handling or a legal requirement. When those purposes end, we assess removal or anonymisation. A request may require an account verification step before we confirm the result.