Reference

Terms & Conditions for api36 Accounts

api36 Terms & Conditions set out how you open, use and protect your account, including identity checks, wallet activity, table access and requests for account changes.

Account eligibilityWallet verificationPolicy accessSupport route
api36 Terms & Conditions for api36 Accounts
TERMS HELP DESK

Three Routes For Policy Questions

A clear contact path helps when a clause affects your account or wallet status. We keep policy questions separate from game requests so your message reaches the right queue, and we can check the relevant account step without asking you to repeat the issue across several channels. Contact us before sending sensitive documents, and use the account details shown in your profile when you ask about access, payment records or a Terms & Conditions change.

Team online

Account access

If phone verification blocks your account, contact support through the account help channel shown on the site. Tell us the affected step and your registered phone number, but never send a password or one-time code.

Wallet status

For DANA, OVO, GoPay or QRIS questions, include the displayed status and transaction reference. We can check whether the cashier step, bank transfer or virtual account instruction matches your account terms.

Policy changes

When you want to question a clause or request a correction, use the support contact listed in your account area. We record the request, confirm its scope and explain the next response step.

ACCOUNT SAFETY DETAILS

How We Apply These Terms

The policy is easier to use when you know what happens behind each account action. We apply the Terms & Conditions to account details, wallet checks, device access and requests for changes…

Data handling

We use account details to provide access, check requests and respond to support questions under these Terms & Conditions. Send only the details requested through the account contact path, especially when asking about a payment record.

Cookie choices

Cookies can help keep your session and account path working across a mobile browser or desktop. Your browser controls can remove them, although some account steps may then require another login.

Account security

Keep your password and phone verification code private, and sign out on shared devices. If you notice an unfamiliar session, contact us through account support so we can check the access record.

Record retention

We retain account and transaction records for the period needed to administer these Terms & Conditions, resolve disputes and meet applicable requests. Ask support which record your question concerns.

Change requests

To correct your name, phone number or other account detail, send the request through the listed support route. We may verify ownership before applying a change to protect your wallet access.

Policy contact

For a clause about Live Blackjack Prestige, GoPay Verify Steps or account closure, identify the exact heading in your message. That lets us answer the policy point instead of sending generic platform text.

Terms & Conditions Questions Answered

These Terms & Conditions answers address the questions you may have before opening an api36 account. We explain the account path, local payment context, data requests and policy contact route in plain English. If your situation is different, quote the relevant clause when you contact support so we can check the exact account or wallet event.

They cover account creation, phone verification, permitted access, wallet ownership, deposits, withdrawals, account security, data handling, technical interruptions and closure requests. The same Terms & Conditions apply when you move between casino areas, sportsbook content or titles such as Live Blackjack Prestige.

Access depends on local law and your account status. Where local law permits, you can open an account using the details requested on the account form. We may require phone verification before access and can restrict an account when eligibility or ownership details cannot be confirmed.

Use a wallet or payment account that belongs to you and follow the cashier instructions shown for your account. DANA, OVO, GoPay and QRIS may require a matching reference, while bank transfer or virtual account steps can display BCA, BRI, Mandiri or BNI details.

Phone verification helps connect the account to the contact detail you supplied and can protect access after a new device login. Complete the requested step through the account page. Never share a verification code with another person or place it in a support message.

Contact support through the route shown in your account area and state which detail needs correction. We may ask for an ownership check before changing a phone number, name or wallet-related record. This process helps prevent an unrelated person from taking control of the account.

Send a specific request through the listed policy contact route, naming the account record, cookie setting or transaction reference involved. We explain how the request relates to these Terms & Conditions and may verify your identity before discussing private account information.

Ask support for account closure through the contact path displayed on the site, using your registered account details. We may first resolve pending wallet or verification matters and explain what records must be retained before the closure request is completed.