Reference

Terms & Conditions for Your mega128 Account

mega128 Terms & Conditions explain how you open, use and protect your account across Live Blackjack Gold, local wallets and the wider lobby.

Account accessWallet checksLocal-law wordingPolicy contacts
mega128 Terms & Conditions for Your mega128 Account
CONTACT THE TEAM

Where to Ask About Terms & Conditions

A clear policy question should reach the account support route, not disappear into a payment attempt. We keep requests about Terms & Conditions close to the login and cashier paths, so you can identify the account, wallet status or policy clause involved. Include your account phone number, the relevant transaction reference and a short description, but never send your password or full wallet credentials. If access is restricted, we explain which check is pending and what request you can make next.

Team online

Account path

Open the support route beside your account area when a Terms & Conditions question concerns phone verification, login access or a restricted session. We use the account details already attached to your request so you do not need to repeat private login credentials.

Cashier path

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, use the support route beside the cashier status. Add the receipt reference and displayed status; we can then match the request to the correct account condition.

Policy request

If you want a clause clarified or need to request an account-data change, identify the section and explain the change in plain English. We use your verified account details to send the response through the available account contact route.

ACCOUNT SAFEGUARDS

What We Handle Under These Conditions

The policy describes how we handle the account records needed for access, wallet checks and policy requests.

Account data

We use your account name, phone number and verification result to connect a Terms & Conditions request with the correct account. If a detail changes, ask through the policy contact route; we may verify ownership before applying the change.

Wallet records

Payment references and displayed wallet status help us check a DANA, OVO, GoPay or QRIS request. Bank transfer and virtual account records may also be matched before we change a transaction status or respond to your policy question.

Cookies

Cookies can keep your session and policy page preferences available while you move from login to the lobby. You can manage browser cookie settings, although disabling required cookies may interrupt account access or make a session expire sooner.

Device security

A new phone or browser can trigger an additional account check under these conditions. Sign out of shared devices, keep your phone verification details private and contact us through the account path if a session looks unfamiliar.

Record retention

We keep account, transaction and security records only as long as needed for the stated account, legal or dispute purpose. A retention request must identify your account; some records may remain where local law permits or requires continued storage.

Policy changes

When we change these Terms & Conditions, we place the revised wording on the policy page and may ask you to acknowledge it at login. Read the effective wording before using the account, especially after a phone or wallet-status request.

Terms & Conditions Questions Answered

These Terms & Conditions answers focus on the account decisions you are most likely to make before opening or continuing access. We cover eligibility wording, verification, payment ownership, personal data, cookies and the route for asking us to clarify or change a policy record. If your situation is not listed, use the account support path with the relevant reference.

They cover account creation, phone verification, login use, lobby access, payment ownership, transaction checks, cookies, account security, data handling and policy changes. They apply to your use of titles such as Dice Duel Mobile Play and to requests made through the account or cashier path.

Yes. Access depends on local law, and we may limit an account or feature where local law permits when an eligibility, security or legal check requires it. The policy page states the applicable wording, and support can clarify the account step connected to a restriction.

Phone verification connects the account to a contact detail you control and helps us investigate unfamiliar sessions or policy requests. We may require it before account access continues. Keep the verification detail private, and use the account support route if the step does not complete.

Our conditions require payment details to belong to you. A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request may be held while ownership or receipt details are checked. Do not send private credentials; provide only the requested transaction reference.

Cookies can preserve a login session and selected policy-page settings while you move between account areas. Your browser controls them, but disabling required cookies can interrupt access. The conditions explain their account function, while optional browser settings remain your choice.

Yes, send a clear request through the policy contact route and identify the account detail you want changed. We may verify ownership before editing it. Account, phone-verification and transaction records can have separate retention needs where local law permits or requires storage.

Name the policy section, describe the issue, and include your account phone number or transaction reference when relevant. For a QRIS receipt, wallet status or login check, the displayed reference helps us locate the right record. Never include your password or full wallet credentials.