Reference

Privacy Policy for Your auto2000 Account

Our Privacy Policy explains how we collect, use and protect details connected with your auto2000 account, including account access, device activity and wallet steps.

Account dataWallet recordsCookie choicesSecurity requests
auto2000 Privacy Policy for Your auto2000 Account
ASK ABOUT YOUR DATA

Privacy Policy Help When Details Need Checking

A clear support path matters when your account record or payment reference does not look right. Contact us through the support route shown on auto2000 and include the email or phone detail linked to your account, the date of the request and the specific Privacy Policy question. Do not send a wallet PIN or full payment password. We can use your account step and transaction reference to locate the right record while limiting what you need to disclose.

Team online

Account access

If you cannot reach your account, we first confirm the contact detail attached to it and may ask for a verification step. This helps us discuss Privacy Policy requests with the account holder rather than disclose account data to an unknown sender.

Wallet record

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the payment reference and date rather than a wallet password. We use those details to locate the relevant record and explain its handling under our Privacy Policy.

Correction request

If your name, phone detail or contact address needs correction, tell us which field is wrong and what should replace it. We may request an account check before changing the record, then confirm the action through the contact path on file.

SECURITY AND RETENTION

What Our Privacy Policy Covers Day To Day

We apply the Privacy Policy during ordinary account use, not only when you contact support.

Collected details

We may handle contact details, verification results, login events, device or browser signals, selected lobby activity and payment references. These records help us provide account access, investigate a stalled wallet status and protect the account from unusual activity.

Cookie use

Essential cookies can keep a signed-in session working between the account page and lobby. Other browser storage may support preferences or security checks. You can review cookie controls in your browser, although disabling essential storage may interrupt account access.

Account security

We may compare a new device or login pattern with earlier account activity before allowing access. Keep your contact detail current and never share a password or wallet PIN. If a login prompt looks unfamiliar, pause and contact us through the support route.

Payment matching

A payment reference lets us connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event with your account without requesting the wallet password. The reference can also help us resolve a receipt or status question more accurately.

Retention period

We keep account, security and payment records only while they serve an operational, security or legal purpose. When a record is no longer needed, our process removes it or changes it so it no longer directly identifies your account, where local law permits.

Your request route

You can ask what account data we hold, request a correction, ask about deletion where available or raise a concern about handling. Include your account contact detail and a focused request so we can verify the account and respond to the correct person.

Privacy Policy Answers For auto2000

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening or using auto2000 in Indonesia. They explain what we collect, why a device check may appear, how payment references are handled and how to ask for a change. If a request involves eligibility or access, the outcome depends on local law.

It covers details linked to your account, including contact data, verification results, login events, device signals, selected activity and payment references. It also explains cookies, security checks, retention and the route for asking about, correcting or deleting data where local law permits.

Device and browser signals help us recognise unusual login patterns and protect your account. They can also keep essential sessions working between the account page and lobby. We use them for security and account operation, not as a reason to request your DANA or GoPay password.

We use a payment reference, amount or related account detail to match a wallet event with your account and check a receipt or status. We do not need your wallet PIN for that process. Bank transfer and virtual account references can be handled through the same account-matching approach.

Yes. Send a focused correction request through the support route shown on the site and identify the account contact detail, the field that is wrong and the replacement. We may verify account ownership first, then confirm the correction through the contact path on file.

We retain account, security and payment records while they are needed for account operation, fraud prevention, dispute handling or a legal purpose. When that need ends, we remove or anonymise the record under our process, where local law permits. You can ask about a particular record.

Contact us with the account detail you can safely verify and state that you are asking about deletion. We assess the request against account security, payment records and any legal retention need. Where local law permits, we remove or anonymise data that no longer needs to remain.

The policy explains how we handle data when you access the service from Indonesia, including login and wallet checks. Account access and eligibility depends on local law. If a location or account question remains unclear, use the support path before submitting further personal or payment details.