Mobile / App
md444 takes a straightforward approach to your personal data — we collect only what we need to run your account, process transactions through Nagad or Upay, and keep your access secure. What we do with that information, and what choices you have, is set out clearly in this policy.
This policy describes the categories of information md444 collects when you create an account, complete identity checks, or move funds through your wallet using Nagad or Upay. We collect your name, contact details, device identifiers and transaction records as part of standard account operation. We do not sell your personal data to unrelated third parties. Data may be shared with payment processors — including the local mobile wallet rails you use — and with technical partners who help us keep the platform running. Any sharing is limited to what those partners need to do their job. We also collect browser and session data through cookies to understand how pages are used and to keep your logged-in session stable across devices. If you access md444 from Bangladesh, your use of this platform and any data processing that follows is subject to your local law and the eligibility conditions that apply in your region. We keep records only as long as they are needed for account operation, legal compliance or dispute resolution, and we delete or anonymise them after that period ends. Changes to this policy will be posted on this page; we encourage you to check back when you have questions about how your data is handled.
Transaction records linked to your Nagad wallet are held to support account history, dispute resolution and compliance requirements. They are not shared beyond what is necessary for processing.
When you use Upay to fund or withdraw from your account, we log the transaction reference and amount. These logs are stored securely and accessible to you through your account history.
Session cookies keep you logged in as you move between the lobby, account settings and your wallet. You can adjust cookie preferences in your browser, though some features may behave differently if cookies are blocked.
Documents submitted during account verification are stored only for as long as required by the applicable compliance framework. After that period, they are removed from active storage.
Not every service connected to your md444 session falls inside this policy. We cover the data we directly collect and control — your account, your wallet activity and how you navigate the site. Third-party services linked from our pages operate under their own terms. Understanding the boundary helps you know where to direct questions about your data.
Login credentials, session tokens and account settings data are fully within our policy scope. We control how this data is stored, who can access it and how long it is retained.
Deposits and withdrawals processed through Nagad or Upay involve payment processors outside md444. Their handling of transaction data is governed by their own privacy terms, not ours.
Pages you browse on md444, including the lobby, account section and support pages, are covered. We track session behaviour through first-party cookies to keep navigation consistent and secure.
Links to external sites, game studios or payment portals take you outside our policy boundary. We are not responsible for data practices on those third-party pages once you leave our domain.
You have real choices about the data md444 holds on you. The most direct route is your account settings page, where you can review the contact details, payment methods and preferences tied to your profile. If something is wrong — a misspelled name, an outdated mobile number, an incorrect address — you can submit a correction request through the support channel and we will update the record once your identity is confirmed. You can also ask us what data we hold, how it is used and who it has been shared with. We respond to data enquiries through our published support route; we do not have a separate data-request portal, so please use the main contact path. If you believe your data has been mishandled, you can raise a formal concern with us in writing and we will acknowledge it and investigate. Availability of these rights may depend on your local law and eligible region, so the specific process may vary. We aim to handle every enquiry with care, and we will tell you clearly if a request falls outside what we are able to action under the current framework.
Open your account settings to see the personal details, wallet links and login history currently on file. If something looks unfamiliar, contact support right away.
Submit a correction request through the support channel with your account reference and the detail you want changed. We will verify your identity before updating any record.
You can ask us what categories of data we hold, why we hold them and which processors have access. Send the question through our published support route and we will respond in writing.
If you think a data decision was wrong, write to us formally through the contact path below. We acknowledge every concern and follow up with our findings within a reasonable period.
Questions about this privacy policy should be directed through the support routes published on the site. Whether you want to review your data, request a correction or raise a concern, the contact paths below are the right place to start. We do not operate a separate data-protection inbox, so please use these channels and reference your account when you write.
Open the chat widget from any page on md444. Tell the agent your account reference and the privacy question you have. They will escalate data-specific requests to the right team.
Send a written privacy enquiry to the support email address listed on the Contact page of md444. Include your account username and a clear description of the data question or concern.
The Account Help section of the site contains step-by-step paths for common data requests, including how to update contact details linked to your Nagad or Upay wallet.
md444 applies access controls so that personal data is only reachable by staff and systems with a clear operational reason to view it. Account passwords are stored in hashed form — we do not hold your password in plain text. Session tokens expire automatically when you log out or after a period of inactivity, reducing risk if a device is left unlocked. We review our data practices periodically and update this policy page when anything material changes.
We keep your account records while your account is active and for the compliance period required after closure. Once that period ends, records are deleted or anonymised. You can ask about the retention period that applies to your account.
First-party cookies keep your session active and your wallet preferences saved between visits. You can manage cookies through your browser settings. Blocking all cookies may affect how your account page and wallet selector behave.
We recommend you use a unique password for your md444 account and update it if you think it has been shared. If you notice any unfamiliar login activity, contact support immediately through live chat or email.
When we update this policy, the revised version is posted on this page with the date of the change. We will also notify you through your registered contact detail if the changes materially affect how your data is handled.
These are the questions we hear most often about how md444 handles personal data. If your question is not covered here, reach out through live chat or the support email listed on the Contact page.
We collect your name, email address, mobile number and, where required, identity documents during verification. We also log device identifiers and session data when you browse the site. Wallet transaction references are stored when you deposit or withdraw through Nagad or Upay.
We share data only with payment processors, identity verification partners and technical service providers who need it to do their job. We do not sell your personal information to unrelated third parties. Any processor we work with is bound by data handling obligations.
Open your account settings page to view your profile, contact details and linked payment methods. For a broader data summary, send a written request through the support email listed on our Contact page. We will respond with the categories of data we hold and how they are used.
Yes. Contact support through live chat or email with your account reference and the detail that needs changing. We verify your identity before making any update. Some fields — like a name tied to a verified identity document — may require additional confirmation steps.
We retain records for the compliance period required after account closure, which depends on your local law and eligible region. Once that period passes, records are deleted or anonymised. You can ask us about the specific retention timeline that applies to your account.
Raise a formal concern in writing through our support email, including your account reference and a clear description of the issue. We acknowledge every concern and follow up with our findings. Whether further escalation is available depends on your local law and eligible region.