Reference

Open cargo555 Privacy Settings Before Access

cargo555 Privacy Policy explains what we collect when you open an account, verify your phone, use the mobile lobby or choose DANA, OVO, GoPay and QRIS.

ACCOUNT DATAWALLET RECORDSCOOKIE CHOICESACCESS RIGHTS
cargo555 Open cargo555 Privacy Settings Before Access
CONTACT ROUTES

Switch to the Privacy Contact Path

Privacy questions should reach us through the account support route shown after you sign in, especially when your request concerns a phone verification, wallet receipt or device session. We ask you to use the same account details linked to the request so we can distinguish a genuine data request from an unauthorised attempt. If access is unavailable, keep the payment reference and approximate time ready rather than sending a full wallet password.

Team online

Account request

Use the support route attached to your cargo555 account to ask what personal data is held, why it is used or which retention purpose applies. Include your registered phone number and request details, but never send your password or one-time verification code.

Wallet evidence

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the payment reference and status shown in your account. We use those details to locate the relevant record without asking you to forward an entire wallet statement.

Access concern

If a mobile browser session, phone verification step or account sign-in looks unfamiliar, contact support through the available account route and tell us the device and approximate time. We may ask account checks before discussing private records or changing access details.

DATA PRACTICE

Browse cargo555 Data Handling Controls

We treat the Privacy Policy as an operating process rather than a footer link. Account creation, phone verification, wallet activity and mobile browser access each create different records, and we use them…

Account records

When you open an account, we collect the details needed to create and maintain it, including your phone number and verification status. We use these records to identify your account, respond to requests and prevent another person from changing private settings.

Wallet references

DANA, OVO, GoPay and QRIS activity can produce payment references, status messages and reconciliation details. Bank transfer and virtual account records work in the same way. We use these records to match a request to your account and resolve a receipt question.

Device signals

A mobile browser path may send device type, browser details, IP address and session events. These signals help us spot an unfamiliar login and keep your account session separate from another phone, without treating the device itself as your identity.

Cookie choices

Cookies can keep a session active, remember selected settings and help us understand whether a page request worked. You can manage available cookie controls in your browser, although blocking required cookies may interrupt phone verification or account access.

Retention periods

We keep each data category only for the period connected to account support, transaction records, security checks or a legal requirement. When a record no longer has a valid purpose, our handling process is to delete it or separate it from direct account details.

Change requests

You may ask us to access, correct or clarify personal data through the account support route. Tell us which record is involved, such as a phone detail or QRIS reference. We may verify account ownership before making a change or disclosing private content.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the searches we hear most often before an account is opened. We focus on the records created by phone verification, wallet activity, browser access and support requests, so you can decide what to share and how to contact us. If your situation is not covered, use the account support route with the relevant reference.

It covers account details, phone verification, wallet and payment references, device and browser signals, cookies, support conversations, retention and your available data requests. It also explains how we use these records for account access, security, transaction matching and policy administration.

Yes. The Privacy Policy includes the DANA or QRIS reference, amount, status and related reconciliation details created when you use those rails. Similar records may arise from OVO, GoPay, bank transfer or a virtual account, without requiring your wallet password.

We use your phone number to create or locate your account, complete the phone verification step and protect account access. It may also help us match a support request to the correct account. We do not ask you to disclose a one-time code in support messages.

You can request access, clarification or correction through the account support route. Name the record involved, such as a phone detail, device session or GoPay reference. We may verify that you control the account before providing private data or applying a change.

Retention varies by record type and purpose. Phone verification and account details may be needed while the account is active, while payment references can remain for transaction matching, support and applicable requirements. We remove or separate records when the valid purpose ends.

Use the account support route as soon as you notice an unfamiliar mobile browser, IP address or session event. Tell us the approximate time and device type, and avoid sending your password or verification code. We may complete ownership checks before discussing the session.

Yes. Access to cargo555 and related data processing depends on local law. If you are in Indonesia, review the rules that apply to your location before opening an account. Where local law permits, our Privacy Policy explains the records and choices connected with access.