Reference

Privacy Policy for barges Accounts

Our Privacy Policy explains how barges handles the information you provide when you open an account, verify your phone, access the lobby or use DANA, OVO, GoPay and…

Account dataWallet recordsDevice signalsCookie choices
barges Privacy Policy for barges Accounts
CONTACT THE TEAM

Privacy Help Beside Account Support

A clear contact path helps you control your information without explaining your request to several teams. Use our support route when you need a copy of account data, a correction to your phone or contact details, clarification about a wallet record or help understanding a cookie choice. Include the email or phone connected to your barges account, the request you are making and any relevant reference, but do not send a password or full payment credentials. We may ask for an account check before changing private data.

Team online

Account data requests

Ask us to confirm the personal data linked to your barges account or request a readable copy. We may verify your phone first so a third party cannot obtain account details by using only a name or payment reference.

Wallet record questions

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, contact support with the date, method and transaction reference. We use those details to locate the record without asking you to share a wallet PIN or complete card credentials.

Correction and deletion

Tell us which detail needs changing or which eligible data you want removed. We assess the request against account security, payment records and legal retention needs, then explain any part that must remain available.

DATA CONTROL

What We Do With Your Information

Privacy work is part of the account flow, not a separate promise hidden from the cashier path.

Account information

We handle details such as your name, contact point, phone verification status and account activity to create access, answer support requests and protect the account. We avoid using these details for an unrelated purpose without a clear reason connected to service delivery.

Payment references

A wallet or bank transaction can create a reference, amount, status and time record. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references help us match a payment state to your account without needing your private wallet password.

Cookies and settings

Cookies and similar storage can keep a session active, remember a selected setting or help us understand whether a page loads correctly. You can manage browser controls, although restricting essential storage may interrupt login or policy access.

Device security

We may record browser type, operating system, approximate connection details and login events to detect unusual access. A mobile session from Indonesia and a later desktop session can appear as separate security events without revealing unrelated device content.

Retention choices

We keep information only while it supports account administration, security, payment reconciliation, dispute handling or a legal requirement. When a retention reason ends, we delete, aggregate or restrict the record according to the handling process that applies.

Your request route

You can ask for access, correction, restriction or deletion of eligible personal data through support. State the account contact, request type and relevant date; we may verify ownership before responding so privacy controls do not expose your account.

Privacy Policy Answers for barges

These Privacy Policy answers address the account and payment questions we expect you to ask before opening or continuing a barges account. They focus on identifiable data, device activity, cookies, local wallet references and the steps used to make a request. If your situation is not covered, contact our support route with the smallest amount of information needed to locate your account.

The barges Privacy Policy covers data collected through account creation, phone verification, login, support, cookies, device access and payment references. It explains why we use those details, how retention works and how you can request access, correction or deletion.

We use phone verification to connect account access and privacy requests to the correct person. It also helps us respond to unusual login activity. We do not ask you to send a wallet PIN or password when checking your account.

Yes. The Privacy Policy includes transaction references linked to DANA, OVO, GoPay and QRIS, such as method, status, time and reference number. These records help us match a payment state to your account and resolve support questions.

We may collect browser type, operating system, approximate connection details and login events from the device you use. This supports account security and page function. We do not use a mobile or desktop session as permission to inspect unrelated files.

Contact support with the phone or email connected to your account, identify the data request and include a useful date or payment reference. We may verify ownership before sending information, then explain the available response and timing.

You can ask us to correct inaccurate account details or remove eligible information through support. Some payment, security or dispute records may need to remain for a defined retention reason. We will explain the result instead of silently ignoring your request.

You can adjust cookie controls in your browser and remove stored site data from its privacy settings. Essential storage may still be needed for login and policy access, so restricting it can interrupt account sessions or require another phone check.