Mobile / Slots
mbk33 collects only the account and transaction data needed to run your wallet, process Rocket and Upay payments, and keep your session secure. This policy sets out exactly what we collect, how we use it, and the choices available to you — subject to your local law and eligible regions.
When you open an account, we collect the details you enter during registration — name, email address and the mobile number linked to your wallet. If you deposit using Rocket or Upay, we retain a transaction reference and the amount processed so your account balance stays accurate and disputes can be resolved. We also log device type, browser session data and approximate region to detect unusual access patterns and protect your account from unauthorised use. We do not sell your personal data to third parties. We share information only where required to process a payment through the wallet rails you chose, or where a legal authority in an applicable jurisdiction makes a lawful request. Cookie data collected during your session helps us keep the lobby responsive on mobile. You can clear cookies from your browser settings at any time without losing your account access. Data retention follows the period required by the payment processing obligations tied to Rocket and Upay records. Once that obligation ends, account data that is no longer needed is deleted or anonymised. Your access to this platform depends on local law and eligible regions.
This policy covers data collected directly through mbk33 and the account tools available on it. It does not extend to third-party sites linked from our pages, and it does not govern how payment processors operate their own systems. Review the scope table below to understand which activities fall inside and outside this policy.
Login credentials, session tokens and device identifiers collected when you sign in or reset your password are fully within scope. We store these securely and use them only to authenticate your account and detect unusual login attempts.
Deposit and withdrawal records tied to Rocket or Upay are within scope for balance accuracy and dispute resolution. The payment processor's own data handling sits outside this policy — check the wallet provider's terms for their practices.
Behavioural data from browsing the lobby — which game categories you opened, how long a session lasted — is within scope. We use this to keep the mobile layout responsive, not to build a profile for advertising.
Links to external sites, game studios such as JDB, Habanero or Microgaming, and payment gateway pages operate outside this policy. Once you leave mbk33, the third party's privacy terms apply and we have no oversight of their data handling.
Your rights under this policy are practical, not theoretical. You can request a copy of the personal data we hold against your account at any time by contacting our support team through the published route. If any detail is incorrect — a wrong name, an outdated mobile number linked to your Rocket wallet — you can ask us to correct it and we will action the update after verifying your identity. You also have the right to ask what data we retain after you close your account, and to request deletion of data that is no longer required for a legal or payment obligation. For Rocket and Upay transaction records, a minimum retention period applies because payment processors require it; we will tell you the applicable window if you ask. Availability of these rights depends on your local law and the eligible region you access the platform from. Start by logging in and checking the account section — some changes, like updating your contact number, can be made directly there.
Request a summary of data held on your account by contacting support. We confirm what is stored, including wallet references for Rocket or Upay deposits, session logs and your registered contact details.
If your registered name or mobile number is wrong, raise a correction request through support. Identity verification is required before any change is applied to your account record.
Query how long specific data is kept, especially transaction references tied to Rocket or Upay. We will confirm the retention window that applies to your record and the reason it is held.
Ask us to delete data no longer needed for payment or legal purposes. We will confirm what can be removed immediately and what must be held for the minimum period set by applicable payment obligations.
If you have a question about how your data is handled, or you want to exercise any of the rights described in this policy, use one of the contact routes published on mbk33. We do not invent operating hours or response guarantees here — check the support page for the current contact options available to you.
Open the chat widget on mbk33 to raise a privacy question directly. Have your account email ready so the support team can locate your record without delay.
Send a written data request to the email address listed on our contact page. Include your registered mobile number and the nature of your query so we can route it to the right team.
The Help section inside your signed-in account lists the current support routes and links to this policy. Check there first — some account detail changes can be completed without contacting support.
We take a direct approach to data handling: collect what is needed, protect it at the account level, and make the process visible to you. Each item below covers a specific area of how we manage the information your account generates.
Session cookies keep your lobby state intact during mobile browsing. You can clear them from your browser settings without losing your account. We do not use cookies to serve third-party advertising or share session data outside mbk33.
Login attempts, device type and session duration are logged to detect access patterns that do not match your normal use. If an unusual pattern is flagged, account access may be paused until you verify your identity through the steps shown in your account.
Rocket and Upay transaction references are kept for the minimum period required by payment processing obligations. Account registration data is held while your account is active. After closure, we delete or anonymise data that no longer serves a legal or payment purpose.
When we update this policy, the revised version is published at mbk33/privacy-policy/ with the date it takes effect. Continued use of your account after a posted update means you have seen the revised terms. Contact support if you have questions about a specific change.
These are the questions we receive most often about how mbk33 handles account and payment data. If your question is not covered here, use the support contact routes listed above.
We collect your name, email address and the mobile number you register with. If you deposit via Rocket or Upay, we also record a transaction reference and the processed amount. Device and browser session data is logged to protect your account from unauthorised access.
We share data only where necessary to process a payment through Rocket or Upay, or where a lawful authority in an applicable jurisdiction requires it. We do not sell your personal data to advertisers or unrelated third parties.
Rocket and Upay transaction records are kept for the minimum period set by our payment processing obligations. Once that period ends, records that are no longer needed for legal or payment purposes are deleted or anonymised. Contact support to ask about the window that applies to your account.
Yes. You can request deletion of data that is not subject to a legal or payment retention requirement. Some Rocket and Upay transaction references must be held for a minimum period. We will confirm exactly what can be removed when you raise the request through support.
Contact support through live chat or the email address on our contact page. Tell us which detail is incorrect — for example, a mobile number linked to your Rocket wallet — and complete the identity verification steps the support team will send you before the change is applied.
No. Studios such as JDB, Habanero and Microgaming supply game content to the lobby but operate their own systems. Once a session connects to a studio environment, the studio's own data terms apply. This policy covers only data collected directly through mbk33.