Reference

Your Privacy Policy at a Glance

Your f2000m Privacy Policy sets out how we handle account, device and wallet details while you move from Mobile Login Indonesia into the lobby.

Account clarityDevice awarenessWallet detailRequest access

Browse Our Lobby Read FAQ

How Payment Data Is Used

f2000m Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We use payment details only to identify your account, match a transaction and resolve a status question. When you choose DANA, OVO, GoPay or QRIS, we may receive a reference, amount, time and result from the payment route; we do not need your wallet password. Bank

1
transfer and virtual account records can include the sending bank, such as BCA, BRI, Mandiri or BNI, together with a reference used for reconciliation. We also record account steps such as phone verification and sign-in events to protect access. Where local law permits, we retain relevant
2
records for the period needed for security, disputes and legal duties. Availability and eligibility depends on local law, and our policy applies to data collected through f2000m pages, account tools and support requests.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH DATA

Three Ways to Reach Policy Support

A clear contact path helps when you want to ask about a record rather than a lobby feature.

Account request Open the support route from your signed-in account and state whether you need access, correction or deletion. We can then match the request to your phone verification record and ask for only the details needed to confirm ownership.

Wallet receipt For DANA, OVO, GoPay or QRIS questions, include the payment reference and date rather than a password or full wallet credentials. We use the reference to check the recorded status and explain what data is held.

Access concern If Mobile Login Indonesia shows an unfamiliar sign-in or device, tell us through the account support path. We can review the event, help secure access and explain which security record prompted the check.

SIX DATA CHECKS

Six Controls for Account Data

Privacy work is part of the account flow, not a separate page you need to decipher later. We separate identity details from wallet references where practical, record device signals for security and…

Collection

We collect details you provide during account creation, including contact data needed for phone verification. We also receive technical signals such as device type, browser events and sign-in time when you use the mobile or desktop path.

Cookies

Cookies can keep your session active, remember a language or help us understand whether a policy page loads correctly. You can manage browser cookie settings, although changing them may require another sign-in before account data is shown.

Account security

Phone verification and sign-in records help us distinguish your normal account access from an unfamiliar device. We do not ask for your DANA, OVO, GoPay or QRIS password, and you should never place one in a support message.

Retention

We keep account, payment-reference and security records only as long as needed for the stated service, dispute handling, fraud checks or legal duties. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Your request

You can ask what personal data we hold, request a correction or ask whether deletion is available. We may verify the request through your account phone step so one person cannot alter another account's records.

Limited sharing

We share data only when needed to operate a stated account or payment process, protect access, respond to a lawful request or resolve a dispute. A QRIS reference, for example, is used for matching and status checks rather than wallet-password access.

Privacy Policy Questions for f2000m

These answers address the privacy searches we hear most often before an account is opened. They cover the records created during phone verification, wallet activity and device access, along with the practical route for asking about your data. If your question concerns eligibility, access depends on local law.

The f2000m Privacy Policy covers personal data collected through account creation, phone verification, sign-in, device use, payment references and support requests. It also explains cookies, retention, permitted sharing and the steps available when you want access, correction or deletion.

We use your phone number to create and verify the account, connect a support request to the correct record and identify unusual sign-in activity. The verification step does not give us your DANA, OVO, GoPay or QRIS password.

No. Our Privacy Policy distinguishes payment references from wallet credentials. For DANA, OVO, GoPay and QRIS, we may record a transaction reference, time, amount and result so we can match status, but you should not send a wallet password to us.

Use the support route inside your signed-in account and ask for a data access copy. Include the phone number connected to the account and describe the record you want, such as a sign-in event or QRIS reference. We may verify ownership first.

Yes. Send a correction request through the account support path and identify the inaccurate field without including unnecessary wallet credentials. We compare the request with your verified account record, update eligible details and explain if a record must remain for security or legal reasons.

Retention depends on why the record exists. Account, security and payment-reference data can remain while needed for access, dispute handling, fraud checks or legal duties. Once that purpose ends, we remove the record or separate it from direct identifiers where practical.

Yes. The Privacy Policy applies when you use Mobile Login Indonesia on a phone or tablet as well as a desktop browser. Device type, browser events and sign-in time may be recorded for security, while cookies can support your session and policy-page settings.

Your Privacy Policy at a Glance

Three Ways to Reach Policy Support

Six Controls for Account Data

Collection

Cookies

Account security

Retention

Your request

Limited sharing

Privacy Policy Questions for f2000m

01 What does the f2000m Privacy Policy cover?

02 Why does f2000m need my phone number?

03 Does the Privacy Policy store my wallet password?

04 How can I request my f2000m data?

05 Can I ask f2000m to correct my data?

06 How long does f2000m keep account data?

07 Does the Privacy Policy apply on mobile devices?

Related Pages