Reference

y200m Terms & Conditions, Clearly Set Out

Our Terms & Conditions explain how your account, wallet instructions, device access and lobby permissions work before you open an account.

Account stepsWallet checksLocal-law accessPolicy contact
y200m y200m Terms & Conditions, Clearly Set Out
CLAUSE SUPPORT

Where To Ask About A Clause

A clear contact route helps when a term is unclear or your account step stops at verification.

Support chat Use the support chat from your account when a clause, phone verification step or wallet instruction is unclear. Include your account email and the screen you reached so we can trace the policy question.
Email request Send a written request by email when you need a copy of a term, a correction to your account record or clarification about DANA, OVO, GoPay or QRIS conditions.
Receipt check Keep your payment receipt and reference number when asking about a Terms & Conditions issue. Our support route can compare the displayed instruction with the recorded wallet or bank-transfer status.
ACCOUNT CONTROLS

Six Controls Behind Our Policy

The policy is easier to use when you know what happens to account details after each step.

Data handling

We use the account details you submit to create access, complete phone verification and respond to a policy request. Share only the details needed for the stated account or payment question.

Cookie choices

Cookies may keep your language, session and policy-page choices available on the same device. Your browser settings can remove or restrict them, although some account steps may then need repeating.

Account security

Keep your password and phone access private, and sign out on shared devices. We may ask for account details before discussing a Terms & Conditions request or changing recorded contact information.

Record retention

We retain account and transaction records for the period needed to operate the account, resolve disputes and meet applicable obligations. A retention question can be sent through support chat or email.

Change requests

To request a correction, name the field, explain the change and attach supporting detail without sharing your password. We will confirm the appropriate route and any verification needed before editing records.

Policy contact

For a question about these Terms & Conditions, contact us through the account help path or email. Quote the clause heading and your account email so the request reaches the right team.

Terms & Conditions Questions You May Search

These answers focus on the policy questions that commonly arise before account access. Read the full Terms & Conditions for the wording that applies to your situation, then use the account contact path if you need a record-specific answer.

You can read the current Terms & Conditions on this page before confirming your account. The policy covers access, verification, payment instructions, device use, data handling and requests to correct records.

Yes. The Terms & Conditions explain how wallet instructions and transaction records are handled, while DANA and QRIS appear as available payment context. The route shown to you can depend on local law.

A new phone may require another login or phone verification step before account access. Keep your contact details current and ask support through chat or email if the policy step does not complete.

We use submitted data for account access, phone verification, transaction handling and policy support. The Terms & Conditions describe these purposes, while a data question can be sent through our stated contact route.

Send the requested correction through support chat or email, identify the account field and provide the requested verification. Do not send your password; we will explain the next policy step.

We may revise the Terms & Conditions when an operational or legal change requires it. We will make the current wording available on this page, and you should read it before continuing.

Use the account help path beside the cashier area, support chat or email. Include the clause heading, account email and any transaction reference so we can address the exact policy issue.