Reference

sultan18 Terms & Conditions In Plain English

sultan18 Terms & Conditions explain how your account, wallet activity, lobby access and policy requests work before you open an account.

Account accessWallet checksPolicy requestsLocal law applies
sultan18 sultan18 Terms & Conditions In Plain English
HELP WITH TERMS

Three Ways To Clarify Account Rules

A clear support route matters when a Terms & Conditions question affects your account or wallet status. Start from the account support path and include the detail that needs checking, such as a phone verification prompt, a QRIS receipt or a virtual account reference. We can then match your request to the relevant policy wording instead of asking you to repeat the full account history.

Team online

Account support path

Open the support route from your account area when a login step, phone verification request or account detail seems unclear. Include your registered contact detail and the exact Terms & Conditions point you want us to explain.

Wallet status check

For DANA, OVO, GoPay or QRIS questions, keep the payment receipt and reference visible before contacting us. We use those details to distinguish a policy question from a wallet status issue without changing your submitted account data.

Policy change request

If a clause appears inaccurate for your account, send the wording and your requested correction through the account support path. We can explain the applicable rule, record the request and tell you whether access depends on local law.

DATA AND ACCESS

How We Apply These Rules Daily

Our Terms & Conditions work alongside practical account controls rather than sitting apart from them.

Account details

We use the account information you submit for access checks, phone verification and policy correspondence. If a name, phone detail or other account field is wrong, contact support with the requested correction before continuing through the account flow.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a wallet event to the correct account. Keep your receipt until the status is clear, because it may be needed for a Terms & Conditions request.

Cookies and sessions

Cookies and session data help keep the account path connected while you move from login to the lobby. Your phone and desktop may show different session prompts, so sign out and sign back in if a policy page does not load correctly.

Login security

You are responsible for protecting your password, phone access and verification messages. Do not share an account session with another person. If you suspect that someone accessed your account, use the support path promptly and describe the sign-in concern.

Retention requests

We retain account and payment-related records only as needed for account administration, policy handling and applicable legal duties. You may ask what record is being handled or request a correction through support, subject to the rule that applies to your account.

Access and changes

You can ask us to explain a restriction, correct account information or clarify a changed clause. We assess each request against the active Terms & Conditions and local requirements; access or eligibility depends on local law rather than on a promise of availability.

Terms & Conditions Questions Answered

These Terms & Conditions questions cover the account decisions people usually want settled before opening access. We keep the answers tied to the actual account path, local wallet references and policy contact process, so you can decide what to do next without guessing which rule applies.

You can read the Terms & Conditions on this page before moving through account access. We recommend checking the wording again when we publish a change, especially before phone verification or a wallet action involving DANA, QRIS, bank transfer or a virtual account.

Yes. The Terms & Conditions cover account and wallet activity connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account steps. Keep the receipt and reference because support may need them when checking a policy-related status.

We may require clear account details and phone verification before account access. If the submitted information does not match the account or wallet reference, we may ask for a correction or further check before allowing the relevant account path to continue.

You can request a correction through the account support path. Tell us which field is inaccurate and provide the account detail needed to locate it. We assess the request under the active Terms & Conditions and any applicable local requirement.

Cookies and session data help connect your login, policy page and lobby path. If a page behaves differently on a phone and desktop, sign out and sign back in first. A session issue does not change the Terms & Conditions you accepted.

Access or eligibility depends on local law. Regional availability may therefore differ, and we may restrict an account path where a legal or account requirement is not met. Contact support if you need the reason for a restriction explained.

Use the account support path and quote the clause or page wording that concerns you. Include your registered contact detail and any relevant receipt only when the question involves a wallet status. We will explain the current rule and record a correction request when appropriate.