Reference

bandit4 Privacy Policy for Your Account

The bandit4 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS for…

Account detailsDevice and cookie useWallet status checksAccess depends on local law
bandit4 bandit4 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Policy Help Near Account Access

If a Privacy Policy question affects your account, start from the support route beside the account and cashier area so we can connect your request with the right records. Tell us the email or phone detail linked to your account, the device you used, and whether the issue involves DANA, OVO, GoPay, QRIS or another payment reference. We use those details to locate the relevant event without asking you to send a password. For requests from Bandung or elsewhere in Indonesia, access remains where local law permits.

Team online

Account access

Use our account support path when you need to ask how the Privacy Policy applies to sign-in records, phone verification or a locked session. Include your registered contact detail and device type, and we can investigate the relevant access event without requesting your password.

Wallet status

For a Privacy Policy question about DANA, OVO, GoPay or QRIS activity, send the payment reference and approximate time through the cashier support path. We can check the recorded status and explain which account data was used to match the transaction.

Data request

Ask us to access, correct or remove eligible personal data through the contact route connected to your account. We may ask for an account step or phone verification before changing records, so a request is linked to the right person.

DATA PRACTICES

How bandit4 Handles Privacy Details

We keep the Privacy Policy practical: account records support access, payment references support reconciliation, and device signals help us identify a session that does not match your usual sign-in pattern.

Account records

We collect the contact details and verification information needed to create and protect your account. A clear account path lets you confirm the correct phone or email before access, reducing the chance that a request or wallet status is attached to another account.

Payment references

DANA, OVO, GoPay and QRIS activity may produce a reference, amount status and timestamp for account matching. Bank transfer and virtual account records follow the same purpose. We do not need your wallet password to check whether a payment event reached the account.

Cookies

Our cookies can remember a session choice and help us understand which Privacy Policy page brought you to an account step. You can adjust cookie controls in your browser, although disabling some cookies may interrupt sign-in or prevent a preference from being saved.

Device security

We may record browser type, operating system, approximate session details and sign-in time to help identify suspicious access. If your phone changes or a session stalls, support can compare the event with your account details without asking for a private password.

Retention choices

We retain personal data only for the account, security, payment matching or legal purpose that requires it, then assess whether it is still needed. The period can differ by record type. Contact us if you want us to explain retention for a specific account detail.

Your request

You can ask what personal data we hold, request a correction, question a use or seek deletion where applicable. Send the request from the contact linked to your account and include the record concerned; we may verify ownership before making any change.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account, wallet, device and contact questions we expect you to ask before opening an account. We keep the wording direct so you can decide what to share and how to request a change. If your situation is not listed, contact us with the account detail or payment reference involved.

The bandit4 Privacy Policy covers contact details, phone verification, sign-in events, device signals, cookie choices and payment references. We use them to provide account access, match wallet status and investigate security issues. You can ask us to explain a specific record through the account contact route.

Yes. The Privacy Policy covers the transaction references and status details connected with DANA, OVO, GoPay and QRIS activity. We use these records to match a payment event with your account. We do not need your wallet password, and support can check a reference when status is unclear.

You can contact us to request access to personal data linked with your bandit4 account. Include your registered email or phone detail and describe the records you want, such as sign-in or payment references. We may verify account ownership before responding or sharing account-specific material.

Send a correction request through the account support route, using the contact detail linked to your account. Tell us which field is wrong and what it should say. We may complete phone verification before changing the record, especially when the change affects account access or payment matching.

We use cookies to retain session preferences and understand how pages such as the Privacy Policy are reached. Browser controls can limit or remove cookies. Some choices may affect sign-in or page settings, so support can help if a mobile browser no longer keeps the required account preference.

Retention depends on why a record exists, such as account access, security checks, payment matching or a legal requirement. Different records may therefore have different periods. Contact us with the account detail involved, and we can explain the applicable retention approach where local law permits.

You may request deletion of eligible personal data through the contact route connected with your account. Some records may need to remain for security, payment reconciliation or legal reasons. We will assess the request, verify ownership and explain the outcome under the Privacy Policy and local requirements.