This page sets out the legal framework that governs your account, your transactions and your use of mj33 — including how we handle payments made through DuitNow, FPX and Boost. Access and eligibility depend on local law and the region where you are located.
Account & User Policy
DuitNow · FPX · Boost Coverage
Malaysia-Region Eligibility
Data Handling Terms
POLICY SCOPE NOTICE
How Our Legal Terms Apply to Your Account
These terms apply whenever you create an account, make a transaction or interact with any part of the mj33 platform. Where you use a local payment method — DuitNow for instant bank transfers, FPX for direct online banking, or Boost as your preferred e-wallet — each transaction is processed subject to the conditions set out here as well as those of the respective payment provider. We do not override the terms your payment provider has already disclosed to you; both sets apply in parallel. Eligibility to open an account and conduct transactions depends on local law in your region. If local law in your area does not permit access to this type of platform, these terms do not authorise you to proceed. We may update this policy from time to time. The version that applies to you is the one published at the time of your transaction or account action. Material changes will be flagged through a notice visible after you log in. If you continue using your account after a change is published, that is treated as acceptance of the updated terms. Questions about how these terms apply to a specific transaction or account situation can be directed to our support team through the contact paths listed on this page.
DuitNow
Instant bank transfer transactions are subject to both these terms and DuitNow provider conditions.
FPX
FPX online banking payments fall within this policy and your bank's own transaction terms.
Boost
Boost wallet transactions are covered here alongside Boost's published user agreement.
Eligibility
Account access and transactions are available only where local law and eligible regions permit.
WHAT THIS COVERS
What Falls Inside and Outside This Policy
Not every activity on mj33 is governed by the same set of rules. This section draws a clear line between what this policy directly covers, what is shared with third-party terms, and what sits outside our responsibility entirely. Understanding the boundaries helps you know where to raise a question and who can resolve it.
Account Access
Creating, verifying and managing your mj33 account — including login credentials, account details and session activity — falls fully within this policy. Any access dispute should be raised with our support team first.
Transactions
Deposits and withdrawals made via DuitNow, FPX or Boost are covered here for the platform side of the transaction. The payment provider's own terms govern the transfer leg. Both sets of terms apply at the same time.
Site Content
Game content supplied by studios available in the lobby — including titles across slots, live casino and table games — is governed by each studio's certification and content terms. We make that content accessible; we do not alter its certified rules.
Third-Party Services
External links, third-party payment processors and any services you access outside the mj33 domain are not covered by this policy. We have no liability for how those services handle your data or transactions once you leave our platform.
YOUR ACCOUNT RIGHTS
Practical Actions Available to You Under This Policy
You have several concrete actions available to you at any point while your account is active. Reviewing your transaction history is straightforward — log in and open the account dashboard, where every deposit and withdrawal record is listed with its date, method and status. If any account detail is incorrect, you can submit a correction request through the support channel; we will verify the change against the identity information already on file and update the record accordingly. If you have a question about how a specific term applies to your situation — for example, how a Boost wallet withdrawal is treated under these terms — our support team can provide a written clarification. You may also request a summary of the personal data we hold linked to your account. That request is handled through the same support path and is subject to the verification steps described in the data handling section of this policy.
Review Records
Your full transaction history — every DuitNow, FPX and Boost movement — is visible in your account dashboard after login. No separate request is needed to view your own records.
Correct Account Details
Submit a correction request to support with the accurate information. We verify against identity records on file before updating. Changes to payment-linked details may require additional verification steps.
Raise a Policy Question
If a specific term is unclear, contact support through live chat or email. We aim to provide a written response that directly addresses your question rather than a generic policy excerpt.
Request Data Summary
You may ask for a summary of personal data held on your account. The request goes through our support team and requires identity verification before the summary is sent.
POLICY CONTACT PATHS
How to Reach Us on Legal and Policy Matters
Policy and account questions can be directed through the contact paths below. For straightforward account corrections or transaction queries, live chat is the quickest route. For formal requests — such as a data summary or a written policy clarification — email gives you a record of the exchange. All contact paths connect to the same support team; choose the one that suits your situation.
Live Chat
Open the chat widget from any page after login for account-level policy questions and transaction queries.
Email Support
Send formal requests — data summaries, written clarifications or account correction submissions — via our support email address listed in your account dashboard.
Account Dashboard
Your dashboard shows the current state of your account, active terms version and any policy notices posted since your last login.
HOW WE HANDLE THIS
Data Handling, Cookies and Account Security
We collect only the account and transaction data needed to operate the platform and process payments through DuitNow, FPX and Boost. Data is not sold to third parties. Cookies are used to maintain your session and remember your preferred payment method across visits — you can manage cookie preferences through your browser settings, though disabling certain cookies may affect account functionality. Account security relies on the login credentials you set; we do not store payment PINs or banking passwords. If you believe your account has been accessed without your permission, contact support immediately so we can review the session log and take appropriate action. Retention periods for account and transaction data follow the requirements of applicable law; records are not kept beyond what is necessary for legal and operational purposes. To request changes to your stored data or to ask how retention applies to your account specifically, use the support email path shown in your dashboard.
Data Collection
We collect account registration details and transaction records. Payment credentials for DuitNow, FPX and Boost are handled by those providers — we receive confirmation of the transaction, not your banking details.
Cookies and Sessions
Session cookies keep you logged in and remember your payment preference. Analytics cookies help us identify which parts of the account flow need attention. Manage these through browser settings.
Account Security
Your login credentials are your responsibility to keep secure. We do not ask for your password by email or chat. Report any suspicious activity on your account through live chat or email without delay.
Retention and Changes
Data is retained as long as required by applicable law and no longer. To request a review of what we hold or to ask for a correction, submit the request through our support email listed in the dashboard.
POLICY QUESTIONS ANSWERED
Frequently Asked Questions on mj33 Legal Terms
These questions cover the account and policy situations that come up most often. If your question is not addressed here, reach out through the live chat or email path shown in the support section above.
Do these legal terms cover my DuitNow and FPX transactions?
Yes, for the platform side of each transaction. The transfer leg is also subject to DuitNow's or FPX's own terms. Both sets of terms apply at the same time. You can review your transaction records in the account dashboard after login.
How do I know which version of the terms applies to my account?
The version in effect at the time of your account action or transaction is the one that applies. If we update the terms, a notice appears in your account after login. Continuing to use your account after that notice is treated as acceptance of the updated version.
Can I request a copy of the personal data mj33 holds on me?
Yes. Send the request through the support email address shown in your account dashboard. We verify your identity before releasing any data summary. The process covers account registration data and transaction records linked to your profile.
What happens if I use Boost and the payment fails — who do I contact?
Check your account dashboard first to see whether the transaction registered on our side. If our record shows no transaction, contact Boost directly for the transfer status. If our record is inconsistent with what you see in Boost, raise it with our support team via live chat.
Is my account accessible from any region in Malaysia?
Access and eligibility depend on local law and the region where you are located. We do not make a region-by-region legal determination on your behalf. If local law in your area does not permit this type of platform, these terms do not authorise access.
How do I correct an error in my account details?
Submit a correction request through live chat or support email with the accurate information. We cross-check against identity records already on file. Changes linked to a payment method — such as a registered Boost or FPX account — may require additional verification before the update is applied.