Reference

Open the y2000m Privacy Policy

y2000m Privacy Policy explains how we use account details, device signals and wallet records when you access our Indonesia lobby.

Account clarityWallet recordsPolicy access
y2000m Open the y2000m Privacy Policy
HELP WITH PRIVACY

Browse your privacy support paths

A clear contact route matters when a Privacy Policy question concerns your phone verification, wallet reference or device session.

Account request Ask us to explain account data connected with your y2000m login, including the phone-verification…
Wallet record For DANA, OVO, GoPay or QRIS records, send the payment reference rather than a…
Device access If a device session looks unfamiliar, tell us the sign-in time and device path…
DATA HANDLING

Explore the controls behind our policy

We apply the Privacy Policy to the practical moments that matter: account creation, phone verification, wallet checks, cookie use and support requests.

Collected account details

We may handle details needed to create and maintain your account, such as contact data, phone-verification results and sign-in events. These records help us connect a privacy request to the right account without asking for unnecessary wallet credentials.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event can produce a reference, amount status and timing record. We use those fields to reconcile account activity, not to request your wallet password or private wallet login.

Cookies and sessions

Cookies and similar session tools can remember sign-in state, security settings and the page path you opened. You can manage browser controls, but changing them may require another login before the account and Privacy Policy pages display correctly.

Account protection

Phone verification and session checks help us assess whether a request comes from the account holder. If you switch from a mobile browser to desktop, the new session may receive its own security record for access review.

Retention choices

We keep records for the period needed to operate the account, resolve payment questions, meet applicable duties or handle disputes. When that period ends, records are removed or separated from direct account use according to our process.

Change request route

To ask for access, correction, deletion or a restriction question, contact support from your account and name the data involved. We may verify your identity before responding, especially when the request concerns phone or payment-linked details.

Browse y2000m Privacy Policy answers

These Privacy Policy answers cover the searches we hear around account access, local wallets, cookies and personal data. Read them before opening an account or when you need a clear next step after a payment reference, device change or phone-verification request. Access depends on local law.

The y2000m Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains why we use each category, how long operational records may remain and how you can ask about access, correction or deletion.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use payment status and reference details to reconcile your account event and investigate a receipt question, without asking for your wallet password.

Contact us through the support path inside your account and state that you are making a Privacy Policy data request. Include your account identifier and the record category, such as phone verification or a wallet reference. We may verify your identity before sharing account-linked details.

You can ask us to correct inaccurate account details through the same support route. Tell us which field is wrong and provide the current value or supporting context. We review the request against the account record before making a change, where local law permits.

Our Privacy Policy explains that cookies and session tools can preserve sign-in state, security settings and the path back to a policy page. Browser controls can remove or block them, but you may need to sign in again before account data is shown.

We retain payment references for the period needed to reconcile account activity, answer a DANA, OVO, GoPay or QRIS status question, handle disputes or meet an applicable duty. The exact period depends on the record and local law, not on a fixed promise.

Use the support contact route linked from your y2000m account and describe the privacy concern in clear terms. For a device issue include the session context; for a payment question include the reference. We may request account verification before discussing private records.