Reference

a2000m Privacy Policy for Indonesian Accounts

Our Privacy Policy explains how we collect, use and protect the details connected to your a2000m account, including phone verification, login activity and wallet records.

Account clarityWallet recordsCookie choicesContact path
a2000m a2000m Privacy Policy for Indonesian Accounts
CONTACT ROUTES

Get Policy Help Near Your Account

A clear contact route matters when you want to ask how your data is handled or correct an account detail.

Account support Use our account support channel for questions about the Privacy Policy, phone verification, login…
Wallet status help For a privacy question linked to DANA, OVO, GoPay or QRIS, send the receipt…
Policy request Ask us to explain a data category, correct an inaccurate account detail or clarify…
DATA PRACTICES

What We Handle Behind Your Login

We treat account data as part of the service path rather than as a marketing shortcut.

Account creation

When you open an account, we collect the details needed for the account path and phone verification. This helps us connect your login to the correct wallet status and prevents support from changing a record without first confirming that the request comes from you.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount and status record connected to your account. We use those details to identify a pending or completed cashier event, not to request your wallet password or PIN.

Cookies

Cookies and similar device storage can keep your session active, remember basic preferences and help us identify technical failures. You can manage cookie settings through your browser, although turning off necessary cookies may interrupt login or account verification.

Account security

We use login activity, device signals and phone verification to help protect your account. If a sign-in looks unusual, support may ask you to confirm account details before discussing wallet records, changing contact data or assisting with access.

Retention period

We retain account, security and payment records for as long as needed for the stated account purpose, dispute handling and applicable legal duties. When a record no longer needs to be kept, our handling follows the removal or anonymisation process available for that data type.

Change requests

You can contact us to ask what account data we hold, correct a detail, or ask how a record is used. Include your account phone number and the requested change; we may verify ownership before making an amendment or sharing account-specific details.

Answers About a2000m Privacy Policy

These questions cover the account and wallet situations that most often lead you to open a Privacy Policy page. Each answer stays focused on how we handle your data, what you can request and which account step helps us respond safely. If your situation is not listed, contact support with the relevant account detail rather than sending a password or wallet PIN.

It covers data connected to your a2000m account, including account creation, phone verification, login activity, cookies, payment references and support messages. It also explains retention, security steps and how to request correction or clarification when access is available where local law permits.

We use your phone number to create and verify the account path, connect you with the correct login and help support confirm ownership. It may also help us locate wallet status records. We will not ask you to send your phone password or wallet PIN.

Yes. The Privacy Policy covers transaction references and status details that may arrive from DANA, OVO, GoPay or QRIS when you use those rails. We use the references to match account activity and investigate a receipt, while sensitive wallet credentials remain with the payment provider.

Contact our account support channel with the phone number attached to your account and state the exact detail you want corrected. We may verify ownership before changing the record. For a payment-related correction, include the receipt reference and avoid sending a password, PIN or full wallet credentials.

On a mobile browser, cookies or similar storage can keep your session, remember basic settings and help identify failed login steps. You can adjust them in your browser controls. Blocking necessary storage may interrupt phone verification or require you to sign in again.

We keep account, security and payment records for the period needed for account operation, dispute handling and applicable legal duties. The period can differ by data type. When continued retention is no longer needed, the record follows our removal or anonymisation process.

Use our account support channel and describe the Privacy Policy request clearly. Include your account phone number so we can route it correctly, and add a payment receipt reference only when relevant. We may confirm ownership before discussing private records or applying a change.