Reference

Open Terms & Conditions Before Access

metic4d Terms & Conditions explain how your account, wallet status, device access and policy requests work before you enter the lobby.

Account stepsWallet checksPolicy accessSupport path
metic4d Open Terms & Conditions Before Access
CONTACT OPTIONS

Contact Us About Account Terms

A clear contact route matters when a policy clause affects your account or wallet status. We keep support focused on the Terms & Conditions, so you can identify the relevant account step, attach the needed reference and receive a direct explanation. Use the route that matches your question before repeating a payment or changing your device session.

Team online

Account access

Send your registered phone number and the account step where access stopped. We can explain the phone verification requirement, check whether the device session matches your account and point you to the relevant Terms & Conditions clause.

Wallet status

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and wallet status shown in your account. We use those details to separate a policy question from a pending cashier record or an account ownership check.

Policy request

Ask us to clarify wording, report an account detail that needs correction or request the current policy text through the account support path. State the exact clause or section so our reply can address your request without guesswork.

DATA PRACTICES

Explore How Policy Data Stays Protected

The Terms & Conditions explain what happens to account information after each policy step, from phone verification through wallet reconciliation and account closure.

Account records

We use your registered account details to confirm ownership, process phone verification and connect support replies to the correct account. Keep your phone number current, because an outdated detail can delay an access request or policy correction.

Cookies and sessions

Cookies and device sessions help keep the account path connected while you move between login, wallet status and the lobby. The Terms & Conditions explain their role, and a new device may require another account check before access continues.

Wallet evidence

Payment references from DANA, OVO, GoPay and QRIS help us match a wallet event to your account. Bank transfer and virtual account records can require additional confirmation, so retain the receipt until the account status is settled.

Security steps

Do not share your password or phone verification code with another person. When account access looks unusual, we may pause the affected step while ownership is checked, then explain the next action through the support route.

Retention requests

The policy sets out why certain account, transaction and support records may remain available after an account action. You can ask which record is involved, why it is retained and whether a correction request applies to that data.

Policy changes

When Terms & Conditions wording changes, we identify the updated policy and its effective point through the account path. Contact us before continuing if a new clause is unclear, especially where it affects access, wallets or verification.

Check Terms & Conditions Answers

These Terms & Conditions questions address the points you are most likely to check before opening or continuing an account. Each answer connects the policy wording to a practical account action, from phone verification and local eligibility to data requests and wallet records. Use the support path when your situation needs an account-specific response.

They cover account opening, phone verification, password care, device sessions, wallet ownership, payment records, data handling, cookies, retention, policy changes and account closure. They also explain how to contact us when you need a clause clarified or an account record corrected.

Yes. Access and eligibility depends on local law. Before opening an account, check that access is permitted where you are located and provide accurate registration details. We may limit an account step when applicable rules or an ownership check require it.

Phone verification connects the account to a contact detail you control and helps us handle access requests securely. If the code does not arrive, avoid repeated changes to your profile and contact support with the registered number and affected account step.

The policy treats DANA, OVO, GoPay and QRIS references as account and wallet evidence. A transaction should match your account details. Keep the receipt or reference available, because support may need it to reconcile a pending status or answer a policy request.

You can request a correction through the account support path. Identify the inaccurate field, provide the registered phone number and explain the requested change. We may ask for an ownership check before updating the record or connecting it to a wallet.

Cookies and sessions support continuity between login, wallet status and the lobby. The Terms & Conditions explain their purpose and related account handling. A new device can trigger another verification step, particularly when the session does not match the account history.

Use the metic4d account support path and name the clause or section you want explained. Include your registered phone number and any relevant reference, such as a QRIS receipt or virtual account record, so we can address the policy question directly.