Reference

Terms & Conditions For Your sga404 Account

sga404 Terms & Conditions explain how your account, wallet checks and lobby access work before you open the service.

Account accessWallet checksLocal lawPolicy contact
sga404 Terms & Conditions For Your sga404 Account
HELP WITH TERMS

Get Clear Answers Before Account Use

A direct policy question should have a direct route, so we keep account and wallet help close to the relevant action.

Account access Use the account help route when phone verification, login details or an account-status question prevents access. Tell us the registered phone number and the exact message shown, but never send your password or a wallet PIN. We will direct you to the relevant Terms & Conditions clause.
Wallet status For a DANA, OVO, GoPay or QRIS status question, keep the payment receipt and reference details ready. Our support path can check whether the account record and wallet request match the policy conditions, then explain what information is needed for the next step.
Policy requests Ask us to clarify a clause, correct an account detail or explain a policy change through the available support contact. Include the page section and your request in one message so we can connect the question with the correct account record.
ACCOUNT SAFEGUARDS

How We Apply These Account Rules

The practical side of our Terms & Conditions is visible in the account flow: we check the phone step before access, match wallet records to transaction requests and keep policy-related contact tied…

Data handling

We use account details to operate access, complete phone verification, match payment records and respond to policy requests. Send only the details needed for your question. When you contact us about Terms & Conditions, we use the account record to identify the clause or correction you are asking about.

Cookie choices

Cookies may support login continuity, account settings and the page state you need while reading these terms. Your browser controls can manage cookie storage. If a cookie setting changes the account path, contact us with the device and browser details so we can explain the available route.

Account security

Keep your password, phone access and wallet credentials private, and sign out on a shared device. We may use phone verification or an account check when access details change. Report an unfamiliar account action through support promptly so the security question is linked to your record.

Record retention

Transaction references, account changes and policy contacts may be retained as part of the service record. The period depends on the record and applicable local requirements. Ask us what record relates to your request, and we will explain the available process for a retention question.

Correction requests

You can ask us to correct inaccurate account information by naming the field that needs changing and confirming the account contact. We may request a matching verification step before making the change. This protects the account while giving you a clear route to update your details.

Policy changes

When Terms & Conditions change, we publish the revised wording on this page and identify the effective point where applicable. Read the current version before using the lobby or a wallet route. If a change is unclear, quote the section title when you contact us.

Terms & Conditions Questions Answered

Most account questions can be resolved by matching the action to the clause that governs it. These answers focus on the Terms & Conditions themselves: account creation, phone verification, wallet records, data requests, policy changes and local access. Read the relevant answer before opening an account, then contact us with the section title if your situation needs a specific response.

They cover account creation, phone verification, login security, wallet ownership, transaction records, policy changes and account contact requests. They also explain that access depends on local law. Read the current page before using the lobby, because the terms apply to each account action and supported wallet route.

Yes, phone verification is part of the account access path. We may need you to complete that step before entering the lobby or handling an account request. If verification stalls, contact support with the displayed message and registered phone details, without sharing your password or wallet PIN.

The Terms & Conditions require wallet and transaction details to match the account record. Keep your DANA, OVO, GoPay or QRIS receipt when asking about a status. We may request a reference or account check before explaining the next step for that payment record.

You can contact us to request a correction and identify the exact field that is wrong. We may ask for a matching verification step before changing it. This process applies to account details used for access or wallet checks, and the request should come from the registered contact.

Cookies may support login continuity, account settings and page state, while account data supports verification, payment matching and policy contact. Your browser controls cookie storage. For a data question, tell us which account detail or cookie setting concerns you and we will explain the available request path.

Access depends on local law. You should use the service only where local law permits, and we may restrict an access or account action when local requirements apply. If your location or eligibility is unclear, contact us before opening an account so we can direct you to the relevant policy wording.

Read the current wording on this page, note the section title and send your question through the available support contact. If you are asking about a policy change, include the clause that changed and the account action affected. We will explain the applicable process using your account record.