Reference

Open idcash With Clear Terms

idcash Terms & Conditions set out how you open an account, use the lobby, connect DANA, OVO, GoPay or QRIS, and request help when an account or wallet…

Account accessWallet rulesPolicy requestsLocal-law wording
idcash Open idcash With Clear Terms
TERMS HELP PATH

Get Help With Account Clauses

A clear support route matters when a clause affects your account, payment record or access request. We ask you to start from the support path linked in your account and include the relevant transaction reference, device type and question about the Terms & Conditions. This gives our team enough context to explain the applicable step without asking you to repeat the same account history.

Team online

Account access

If phone verification does not complete, use the account support path and state which Terms & Conditions section concerns you. Add the phone number on the account and the device path you used, such as a mobile browser, so we can direct the access request correctly.

Wallet status

For DANA, OVO, GoPay or QRIS questions, send the payment reference and the status shown in your cashier record. We can explain which term applies to a pending, reversed or unmatched entry while keeping the account and wallet details tied to the same request.

Policy changes

When you want a correction, clarification or change request under the Terms & Conditions, quote the section and describe the result you are asking for. Our support route keeps the request attached to your account record rather than treating it as a general lobby question.

ACCOUNT SAFEGUARDS

Check How We Handle Policy Data

The Terms & Conditions also explain the practical controls around your account record. We limit policy handling to the details needed for access, payment matching, security checks and support replies, while your…

Data handling

We use registration details, phone verification results and transaction references to apply the Terms & Conditions to your account. When you contact support, include only the details needed to identify the issue; never send a password or one-time verification code in a policy request.

Cookies and sessions

Cookies or similar browser storage can keep a policy acknowledgement and login session connected to the same device path. If you clear browser data, switch from mobile to desktop or use private browsing, the account may ask you to sign in and confirm the terms again.

Account security

Your Terms & Conditions duties include protecting the phone and login details attached to the account. Sign out on shared devices, check the account before confirming a wallet action and contact support through the account route if an access step looks unfamiliar.

Record retention

We retain account, verification and transaction records for the period needed to apply the agreement, investigate a payment question or meet a lawful request. A retention question should identify the record type, such as QRIS confirmation or a phone verification event.

Change requests

To request a correction to your name, phone detail or other account record, use the policy support route and describe the exact field. We may need a further account check before changing information that affects wallet matching or access under the Terms & Conditions.

Who to contact

Questions about interpretation, data use, cookies, retention or account access belong in the support path connected to your idcash account. Include the policy heading and a short description of the issue; this helps us separate a Terms & Conditions request from a game or lobby query.

Find Answers About idcash Terms

These Terms & Conditions questions cover the account steps you are most likely to check before opening access in Indonesia. Each answer points you back to the relevant policy process, including local-law wording, phone verification, wallet records, device sessions, data requests and support contact.

They cover account creation, phone verification, login security, permitted access, wallet ownership, payment records, data handling, cookies, retention and support requests. They also explain that access or eligibility depends on local law and that available account routes can vary by location or account status.

Yes. Read the current wording before completing the account path, then confirm acceptance where the account page asks you to do so. Phone verification may be required before account access, and continuing after a displayed policy change means you should check the updated clauses first.

They explain how wallet ownership, payment references and status matching apply to DANA, OVO, GoPay and QRIS. If a record is pending or unmatched, keep the receipt reference and contact support through your account so the payment question can be assessed under the relevant clause.

Use the account support path and name the exact field you want corrected, such as a phone detail or account name. We may request an additional check before making a change that affects phone verification, wallet matching, security or your rights under the Terms & Conditions.

A switch from mobile browser to desktop, or a cleared browser session, can require another login or policy acknowledgement. Keep your login details private and check the account after switching devices. The Terms & Conditions still apply to the same account, regardless of the device path.

We keep records for the period needed to operate the agreement, answer a payment question, protect account access or meet a lawful request. For a retention query, contact support with the record type and reference, such as a QRIS confirmation, bank transfer entry or verification event.

Start with the policy support route linked to your account and quote the section that concerns you. We can explain the account process and available records, while access or eligibility depends on local law. The same route can handle data, cookies, wallet and policy-change questions.