Reference

Terms & Conditions for Your Account Path

limit138 slot Terms & Conditions explain how you open, use and protect your account across our casino, slot and sports areas.

Clear account stepsWallet status checksPolicy contact routeIndonesia access wording
limit138 slot Terms & Conditions for Your Account Path
POLICY HELP

Three Routes For Terms Questions

A clear contact path helps when a clause affects your account or wallet status. Start from the account help route if you cannot sign in, then keep your payment receipt or reference…

Account access If phone verification or sign-in does not complete, use the account help path and describe the exact screen or step that stopped. We can use your registered contact detail to check the account record without asking for your password. Access remains subject to local law and the account checks in these Terms & Conditions.
Wallet status For a wallet question, include the payment rail, amount reference shown to you and approximate time. DANA, OVO, GoPay and QRIS status can be checked against the account event, while bank transfer and virtual account cases may need the bank reference. We then explain the relevant Terms & Conditions step.
Policy changes If you want to question a clause or ask for a wording change, contact us through the policy support route and name the section concerned. We record the request, confirm the account detail needed to respond and point you to the current Terms & Conditions text rather than relying on an old page.
DATA AND SECURITY

How We Apply These Terms Daily

Our policy work is tied to practical account events rather than broad statements. We check the identity details connected to a wallet action, keep the policy wording available, and use account-security controls…

Account records

We keep the account details needed to provide sign-in, phone verification, wallet matching and policy support. Your registered contact detail helps us distinguish your request from another account. We use those records for the purposes described in these Terms & Conditions and do not ask support requests to include your password.

Payment matching

When you use DANA, OVO, GoPay or QRIS, we match the payment status with the account event shown in the cashier path. Bank transfer and virtual account references may be checked separately. This matching helps us explain a pending or rejected step without treating a receipt alone as account approval.

Cookies

Cookies can keep a policy page, sign-in state or device preference working during your visit. We use the cookie details needed for those functions and may ask your browser to store a session marker. You can manage browser cookies, but changing them may affect account access or policy-page display.

Device security

Our account conditions apply across mobile and desktop browsers, so a phone sign-in and a later desktop session may trigger different security checks. Keep your device lock and browser private. If a session looks unfamiliar, stop using it and contact account help before continuing with wallet activity.

Data retention

We retain account, payment-status and support records for the period needed to operate the account, address disputes, apply these Terms & Conditions and meet legal or payment obligations. A retention question should name the account detail or event involved, allowing us to explain what can be changed or removed.

Change requests

You can ask us to correct an account detail or clarify how a policy record was used through the support route. We may verify your registered phone detail before discussing private data. We then confirm whether the request changes the record, requires more evidence or is limited by a legal duty.

Terms & Conditions Questions Answered

These Terms & Conditions questions focus on the steps that most often matter before an account is opened or a wallet is connected. We answer them directly so you know what to prepare, which checks may occur and where to ask for clarification. Keep your registered phone detail and payment reference available when a question concerns your own account.

They cover account creation, phone verification, sign-in, device sessions, casino and slot access, wallet status, payment matching, data handling, cookies, policy changes and support requests. The rules apply to your use of the account, and access depends on local law and any account checks shown to you.

Phone verification may be required before account access or before a sensitive account action. We use the registered contact detail to confirm the account record, not to request your password. If the check stalls, contact account help and describe the exact step shown on your device.

DANA and QRIS are covered as payment routes connected to an account event. We compare the status shown in the cashier path with the payment reference available to us. A receipt does not replace account verification, and a pending status may remain until the payment record can be matched.

OVO and GoPay can appear as local wallet options where available to your account and where local law permits. The account name and payment ownership must align with the applicable checks. If wallet status looks incorrect, send the payment reference through account help for a status check.

The same Terms & Conditions follow your account when you move between a mobile browser and desktop browser. A new device or session can request another sign-in or security check. Keep your registered phone available, and contact account help if an unfamiliar session appears.

Use the policy support route and identify the account field or payment event that appears incorrect. We may verify your registered phone detail before discussing private records. We then explain whether the detail can be corrected, what evidence is needed and whether a legal retention duty applies.

Contact us through the policy support route and name the clause or page wording you want clarified. We can point you to the current text, explain the effective-date treatment and record a correction request where appropriate. Please include no password or unnecessary wallet credentials in your message.