Reference

g1002 Terms & Conditions Explained

g1002 Terms & Conditions set the rules for opening an account, using the lobby and requesting wallet actions in Indonesia.

Account rulesWallet checksPolicy accessPhone verification
g1002 g1002 Terms & Conditions Explained
POLICY HELP

Reach Support About Your Terms

Questions about the Terms & Conditions should include the account step or policy clause that caused confusion. From the account help area, send a request with your registered phone number and a short description; do not include a wallet password or one-time verification code. We can then check access status, wallet records and the policy path without asking you to repeat sensitive credentials.

Team online

Account access

When phone verification does not complete, use the account help path and mention the device you used. We will check the access step against the current Terms & Conditions and explain what can happen next.

Wallet status

For a DANA, OVO, GoPay or QRIS question, include the payment rail and account reference. Our support path can match the request with the relevant policy rule without requesting your wallet PIN.

Policy request

If a clause needs clarification or you want to request a policy change, send the request from your account area. We record the topic, review the applicable wording and reply through the available account contact path.

ACCOUNT CONTROLS

Browse How We Apply These Terms

The policy is practical because it connects account activity with the records needed to resolve a request.

Data handling

We use submitted account details to process phone verification, match wallet ownership and answer policy requests. A request should contain only the details needed to identify the account and the specific Terms & Conditions question.

Cookie controls

Cookies can keep your session and policy page settings consistent between account screens. If you clear them, we may ask you to sign in and complete the same phone verification step again on that device.

Account security

Keep your password and verification code private. We do not need either item in a support request, and the policy permits us to pause an access step when account activity or submitted details require checking.

Record retention

We retain account, payment and support records for the period needed to operate the account, resolve disputes and meet applicable obligations. The current policy path states how a retention question can be submitted.

Correction requests

To request a correction, identify the account detail that is wrong and send it through account help. We may ask for a matching account step before changing phone, wallet or profile data.

Policy contact

For a Terms & Conditions question, name the clause, account action or payment rail involved. This gives our support team a usable path to check the request and explain whether local law affects access.

Find Answers About Account Terms

These Terms & Conditions answers focus on the decisions you make before opening or using an account. They cover eligibility wording, phone verification, wallet matching, device access and requests about stored records. Read the full policy text as well, because the current version controls when a specific account or payment situation is not covered by a short answer.

You can open the current Terms & Conditions from the policy path linked in the account area. Read it before completing account access, especially the sections covering phone verification, wallet matching, device sessions and requests to correct stored details.

Yes. The Terms & Conditions cover wallet actions through DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account steps. The payment record must match the account details, and a mismatch can pause the request while we check it.

You can use the account path on a supported mobile browser, tablet or desktop, with the same Terms & Conditions applying across devices. Access depends on local law, and phone verification must be completed before account access is enabled.

Phone verification confirms that the number connected to your account can complete the access step. Keep the verification code private and use the registered number. If the step fails, contact account help with your device details rather than sending the code.

Yes. Send a correction request through account help and identify the field that needs changing, such as a phone or wallet detail. We may ask for a matching account step before applying the change under the current Terms & Conditions.

Access depends on local law. When a location or eligibility rule applies, the current Terms & Conditions explain the relevant restriction and the available contact path. We can clarify the policy wording, but we cannot change a legal access requirement.

Use the account help path and quote the clause or describe the account action that concerns you. Include your registered phone number and payment rail only when relevant. Never include your password, wallet PIN or one-time verification code.