Reference

Open elemen33 Terms & Conditions Clearly

elemen33 Terms & Conditions set the rules for opening an account, using the lobby and moving funds through supported payment rails.

Account accessWallet checksLocal-law access
elemen33 Open elemen33 Terms & Conditions Clearly
POLICY HELP

Check Terms Support From Your Account

Questions about the Terms & Conditions should reach us through the support path connected to your account, so we can match your request with the relevant account or wallet record. If login or phone verification stalls, tell us which step you reached rather than sending another registration attempt. For payment wording, include the rail used, such as QRIS or DANA, and keep your receipt available. We can then explain the applicable policy path without asking you to publish sensitive details in an open channel.

Team online

Account support path

Use the support contact shown after account access when you need a clause explained. Include your account identifier and the section heading, such as account closure or payment verification, so we can direct the request to the right policy process.

Wallet status request

If an OVO, GoPay or QRIS transaction remains unclear, send the payment reference through the account support route. We use that reference to check the recorded status and explain which Terms & Conditions step applies before any further wallet action.

Login access query

When a phone verification step prevents account access, describe your device path, such as mobile browser or desktop browser, and the message shown. We will use those details to explain the access rule and the next permitted account step.

DATA PRACTICES

Explore How Policy Checks Work

The Terms & Conditions connect account rules with practical handling of your data, cookies and payment records.

Account data

We handle the details supplied during account opening, including contact and verification data, for access checks and policy administration. If a field is inaccurate, contact us through the account route and identify the correction needed without sharing your password.

Cookie choices

Cookies can support session continuity and remember selected policy preferences on your browser. Your device settings may allow you to remove or restrict them, although some account functions may then require another login or may not work as intended.

Login security

Your account remains tied to the login details and phone verification step you provide. Do not share access codes or passwords. If you suspect that another person has reached the account, contact support promptly and describe the last known access.

Payment records

A DANA, QRIS, bank transfer or virtual account reference helps us match a wallet event with the correct account. Keep the receipt until the status is settled, and send only the reference requested through our protected account support path.

Retention requests

Some account, security and transaction records may need to remain available for policy administration or legal obligations. You may ask how a record is used or request a change, and we will explain what can be actioned under the applicable rules.

Policy contact

For a Terms & Conditions question, name the clause, account step or payment event involved. Our support team can clarify wording, record a correction request and explain access outcomes where local law permits, without treating a general lobby question as a policy request.

Find Answers About Account Terms

These Terms & Conditions questions cover the account actions you are most likely to check before using elemen33 in Indonesia. We keep the answers tied to the policy itself: account ownership, verification, wallet records, device access, data requests and local-law availability. If your case does not fit one of these answers, use the support path shown in your account and quote the relevant clause.

They cover account opening, phone verification, login protection, wallet use, transaction checks, policy changes, data handling and access to available lobby areas. The rules apply when you use a mobile browser or desktop browser, and access depends on local law.

Read the policy presented during the account path, enter accurate details and complete the requested phone verification. Your acceptance is recorded through the account flow. Do not continue if a clause is unclear; contact support with the section name first.

Those local rails may be shown when available to your account and region. Use a wallet or bank route connected to your own details, follow the displayed steps and retain the receipt. A payment reference may be needed for a status check.

Verification helps us match a wallet event or bank transfer with the correct account and apply the Terms & Conditions consistently. We may request a receipt, reference or account detail, but you should never send a password or private access code.

The policy does not become a different agreement on mobile or desktop, but the account flow can display differently by browser. If phone verification or a policy link fails on one device, try the other path and tell support what appeared.

Contact us through the support route connected to your account and state the field that needs correction. We may ask for verification before changing it. Requests are assessed against account security, transaction records and applicable local requirements.

No. The Terms & Conditions make availability dependent on local law, account status and the routes shown to you. If a casino, sports or game area is not displayed, do not bypass that restriction; ask support which policy condition applies.