Casino / Slots
This page sets out the legal framework that applies when you access mig68 — your rights, our obligations and the conditions that govern account use in supported regions. Access and eligibility depend on your local law and the region from which you connect.
Our legal policy governs every interaction between you and mig68 — from the moment you open an account through to each transaction you make using Rocket, Upay or Bank Transfer. The terms here are not a formality; they define what we can do for you and what we ask of you in return. When you submit a deposit request or raise a query through our support channel, the conditions described on this page are the ones in effect. We do not apply different rules to different payment routes — the same policy covers all three verified rails equally. If a specific provision conflicts with a rule in your local jurisdiction, local law takes precedence for residents of that region. We update this policy when our service changes in a material way; the current version is always the one shown here, and the date at the foot of this page reflects the last revision. If you are unsure whether access is permitted where you are, check your local regulations before proceeding. Questions about a specific clause can be directed to our policy support path described in the sections below.
Transactions made via Rocket fall under the same terms as all other payment routes. No separate legal terms apply to Rocket deposits or withdrawals beyond what this policy states.
Upay transfers are processed under our standard transaction policy. The amounts, limits and verification steps shown in your account at the time of transfer are the ones that apply.
Bank Transfer instructions and any associated limits are shown inside your account wallet screen. This policy covers disputes or queries arising from those transactions.
Understanding what this policy covers helps you know where to direct a question. Not every part of your experience falls under the same set of rules — some areas, like third-party payment processors, have their own terms that sit alongside ours.
Your login, registration steps and account settings are fully within the scope of this policy. If access is restricted in your region due to local law, that restriction applies regardless of any steps taken on our side.
Deposits and withdrawals made through Rocket, Upay or Bank Transfer are covered here. The limits and verification steps shown in your account at the time of the transaction are part of this policy's scope.
Game content, lobby pages and support materials published on mig68 are within scope. We are responsible for the accuracy and fairness of what we publish on our own domain.
Payment processors, mobile wallet operators and any external service you connect to have their own terms. This policy does not override those. We recommend you review the terms of any third-party service you use alongside your mig68 account.
This policy is not a passive document — it gives you concrete steps you can take at any time. You can review your transaction history directly from your account wallet screen; every deposit and withdrawal made via Rocket, Upay or Bank Transfer is logged there with a timestamp. If you believe a detail in your account record is incorrect — a name, a registered mobile number or a linked payment method — you can submit a correction request through our support channel. We will review the request and respond through the same channel. If a transaction appears in your history that you did not authorise, raise it as a dispute through the support path below; do not wait, as time-sensitive records are easier to verify quickly. Policy questions — where a clause is unclear or where you want to know how a specific rule applies to your account — can also be sent to the same contact path. We aim to keep responses specific to the clause you raise, not generic replies.
Open the wallet screen in your account to see a full log of transactions. The history is filterable by date and payment method, including Rocket, Upay and Bank Transfer entries.
Submit a correction request through our support channel if any registered detail is wrong. Include the field name and the correct value so we can verify and update it without delay.
If a transaction in your history looks wrong, contact support as soon as you spot it. Provide the transaction reference shown in your wallet screen and the support team can trace the record.
Any clause on this page can be queried directly. Send your question through the policy contact path and reference the section heading so we can give you a precise, clause-specific answer.
Three contact routes are open for policy-related queries. Choose the one that works for your situation — live chat for quick clarifications, email for written records of a dispute, and the account help portal for self-service options tied to your profile.
Open the chat widget from any page on mig68. Use this route for quick questions about a clause, a transaction entry or an account detail you need clarified promptly.
Send policy queries or dispute details to our support email address shown in your account settings. Email creates a written record, which is useful when you need a documented response to a specific clause or transaction.
Log in and open the Help section in your account dashboard. From there you can check the status of an open query, review previous support interactions and find the current policy version.
Our approach to data, cookies and account security is built into the policy you are reading now. We do not treat these as separate topics — each one affects how your account functions and how we handle the information linked to it.
We collect only the information needed to operate your account — registration details, transaction records and support correspondence. We do not sell account data to third parties. If you want to know what data is held against your account, submit a data review request through the support channel.
Cookies on mig68 keep your session active and remember your preferences between visits. You can adjust cookie settings through your browser at any time. Disabling session cookies may affect how the lobby and wallet screens load on your device.
Access to your account is protected by the credentials you set at registration. If you believe your account has been accessed without your permission, use the support channel immediately. Do not share your login details; we will never ask for your password in a support interaction.
To request a change to how your data is stored or used — including deletion where local law permits it — contact us through the policy support path. State your account reference and the specific change you are requesting so we can process it accurately.
These questions come from account holders who want to understand how the policy applies to their situation. If your question is not here, use the support contact paths above.
Access and eligibility depend on your local law and the region you connect from. If online account services of this kind are restricted where you are, that restriction applies regardless of what this policy says. Check your local regulations before opening or using an account.
Open your account wallet screen first — transactions can take a short time to appear after the mobile wallet confirms the transfer. If the entry is still missing, contact support through live chat or email with the transaction reference from your Rocket or Upay app.
Yes. Send a data review request through the support email or account help portal. Include your registered account name and the specific data you want to review. We will respond through the same channel with the details held against your account.
Raise it through live chat or email as soon as you notice it. Provide the transaction reference shown in your wallet history, the date, the amount and the payment method used. We will check the record and respond with our findings.
We update this page when a material change is made to how the policy works. The revision date at the foot of the page reflects the last update. We do not send automatic notifications, so check this page directly if you want to confirm the current version.
Contact us through the email support route and reference the specific clause you are questioning. Written correspondence through email is the right path for formal disagreements — it creates a record that both sides can refer to during the review process.