Reference

Terms & Conditions for mata22 Accounts

VIP Baccarat, bingo168 and Royal Fishing sit behind one account path, while these mata22 Terms & Conditions explain how access, wallet checks and account use work.

Account rulesWallet ownershipPolicy accessSupport route
mata22 Terms & Conditions for mata22 Accounts
HELP WITH THE RULES

Three Ways To Resolve Policy Questions

A clear contact path matters when a clause affects your account or wallet status. We keep policy questions separate from game requests so our team can check the relevant account step, payment receipt or verification state. If you are in Surabaya or elsewhere in Indonesia, use the support route displayed inside your account and include the exact notice you saw. That gives us enough context to respond without asking you to repeat the full account history.

Team online

Account access

If phone verification or a policy notice blocks your account path, contact us through the support route shown after login. Include your registered phone detail and the wording of the notice, but never send a password or one-time security code.

Wallet status

For DANA, OVO, GoPay or QRIS questions, send the payment receipt reference and the displayed status through our account support channel. We can match the query to the relevant Terms & Conditions step without requesting your wallet password.

Policy changes

When you need clarification about a revised clause, quote the section heading and date shown on the page. Our support team can explain how the change affects account use, withdrawal verification or access where local law permits.

ACCOUNT DATA PRACTICE

How We Apply These Conditions

The policy is easier to use when you know what happens to account details after each step. We use the information needed for phone verification, payment matching, security checks and support handling…

Data handling

We use account details to confirm access, match payment ownership and investigate policy questions. A support request should contain only the details needed to identify the issue, such as a receipt reference or the section wording involved.

Cookies

Cookies can keep your session, language choice and policy acknowledgement connected while you move through the account path. Clearing them may require you to sign in again and repeat the Terms & Conditions acknowledgement.

Account security

Phone verification is part of our account access process. Keep your password and one-time code private, use your own device where possible, and contact support if a sign-in notice does not match your recent action.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be checked against your account when a payment or withdrawal needs confirmation. We do not need your wallet password to investigate a receipt.

Record retention

Relevant account, payment and support records may remain available for the period needed to apply these Terms & Conditions, resolve disputes and meet applicable local requirements. We do not promise a fixed period where requirements can differ.

Change requests

To request a correction to your account details or ask about policy wording, use the support route displayed in your account. State the requested change clearly so we can check ownership before updating any record.

Terms & Conditions Questions Answered

The questions below address the account decisions that most often need a plain answer before you continue. We refer to the current Terms & Conditions shown on the site, because wording and access requirements may change with local rules. If your case involves a payment receipt, phone check or withdrawal review, include that detail when contacting us so we can point you to the relevant clause.

You can read the current Terms & Conditions on this page before opening an account and whenever you return to the policy area. Check the displayed date or update notice, then contact support through your account if a clause about access, payments or verification needs clarification.

Yes. Account access and eligibility depends on local law. We apply the conditions shown for your region and may restrict an account path where local requirements do not permit access. Do not continue if the service is not permitted where you are located.

Phone verification connects your account access to a contact detail you control and helps us investigate sign-in or payment questions. Enter the code only in the account path, never share it with support, and contact us if the verification message does not match your action.

Those payment rails may appear for supported accounts, but availability is not identical for every account or region. Your payment must belong to you and match the details requested in the account path. Keep the receipt reference if a status check is needed.

Yes. We may request a check before processing a withdrawal when account ownership, payment history or bank details need confirmation. Follow the instructions provided through your account support path, and do not send passwords or wallet security codes.

Use the support route shown after login and state which account detail needs correction. We may ask for information that confirms ownership before making a change. Include the relevant section or notice if your request relates directly to these Terms & Conditions.

We may update the wording when account processes, local requirements or security practices change. The current version is the one displayed on this page or in an account notice. Read the new clause before continuing, and contact support if its effect is unclear.