My MX Data gives departments, public bodies, suppliers and authorised partners a controlled, traceable way to exchange sensitive files. Named recipients, detailed audit records and MX's quantum secure patented methodology keep accountability attached to every handoff.
7-day trial · up to 5 users · no credit card required
Audits, reviews, investigations and partner assurance all test information handling. Secure file sharing should make those questions easier to answer, not leave teams reconstructing events from inboxes and public links.
Named recipients create clear accountability. MX exchanges files with identified users rather than public links that can be forwarded or remain active beyond their original purpose.
Detailed activity records support reconstruction. Uploads, views, downloads and restoration events can be recorded with timestamps and relevant access details.
Expiry and permission controls make access deliberate. Teams can define how long a file remains available and what an authorised recipient can do with it.
Suitability must be assessed, not assumed. MX provides technical controls and evidence; each public body remains responsible for classification, lawful use, configuration, accreditation and risk acceptance.
Alongside AES-256 protection, MX separates file data, divides it into encrypted shards and restores it for an authorised recipient. This adds another control layer without claiming absolute protection.
Information that identifies the file, sender or purpose is separated from the payload, so an individual fragment carries less useful context.
The anonymised payload is split into shards and handled according to configured data-location options. No individual shard is a complete usable file.
The file is restored after recipient verification, with relevant activity recorded to support accountability and later review.
ASR is not a claim of invulnerability. It is a patented methodology designed to reduce exposure, strengthen long-term data protection and make the handling process easier to explain.
MX focuses on the point where sensitive information moves between known parties. It supports controlled handoffs without attempting to replace every storage, records-management or collaboration system.
Exchange files with identified users rather than public links, reducing uncontrolled forwarding and clarifying ownership.
Record uploads, access, downloads and restorations to support chain-of-custody evidence and governance review.
Define how long a file remains available and apply download controls that reflect the purpose of the exchange.
Select appropriate regions for encrypted shards as part of wider departmental, contractual and legal requirements.
Add verification to protect user accounts and support a stronger identity and access-management process.
Move datasets, media and technical records without forcing staff to split files or use unapproved services.
Collect files from citizens, suppliers and partner bodies through one consistent, approved upload route.
Keep routing notes and operational conversation connected to relevant file activity rather than dispersed across inboxes.
SharePoint, OneDrive and established platforms can remain appropriate for productivity and records management. MX is designed for exchanges that need named access, stronger traceability and a defensible process.
The practical question is not which platform replaces everything. It is which exchanges need greater control and evidence. Explore MX's enterprise file-sharing approach.
MX can help facilitate compliance efforts through encryption, named-user access, audit records, expiry controls and data-location options. The public body remains responsible for classification, lawful basis, policy, retention, people and configuration.
Structured transfer records can reduce manual reconstruction and support internal, supplier and partner reviews.
Named users, authentication and permissions help show how access was limited to authorised participants.
Region options can support hosting and contractual requirements when assessed with the wider architecture.
From upload to recipient access, the exchange can be described to a DPO, auditor, procurement team or partner body.
Use MX where a file needs to move beyond the team that created it and the recipient, access conditions and evidence all need to remain clear.
Share case material, reports and operational documents with named users in another department or public body, while retaining a clearer activity record.
Explore controlled B2B exchangeProvide a branded upload route for sensitive evidence, procurement documents or supporting records instead of accepting files through fragmented channels.
Review secure upload portalsTransfer datasets, media, planning archives and technical packages without encouraging staff to use personal accounts or consumer services.
See secure large file transferUse these guides to support classification, assurance and longer-term security decisions around sensitive file exchange.
A harmless-looking spreadsheet can become sensitive once names, pricing or project details appear. Learn how to classify risk before a file leaves your organisation.
Read the guideLook beyond encryption to access, auditability, retention and configuration.
Read the guideUnderstand how separating and anonymising data changes the attacker's problem.
Read the guideWhere MX fits, what its controls can support and where departmental assessment remains essential.
My MX Data gives public sector teams a controlled route for moving sensitive files between departments, agencies, suppliers and other known recipients. Each exchange is associated with named users and recorded through a detailed audit trail.
The platform combines AES-256 protection with Anonymise, Shard, Restore. Administrators can also apply expiry dates, download restrictions and data-location options.
No service should make a blanket claim that it suits every government classification. The decision depends on the information, departmental risk assessment, recipients, hosting, configuration, contractual controls and required accreditation.
Use the current Government Security Classifications Policy as the starting point. Do not assume suitability for SECRET or TOP SECRET without formal assurance and approval.
Responsible sharing starts with purpose, necessity, lawful basis and accountability. Technology supports those decisions but cannot make them for a public body. Named access, expiry, download permissions and activity records provide stronger control and evidence around the transfer itself.
The ICO data sharing code explains how legal, technical and organisational measures work together.
No. Those platforms can remain appropriate for productivity, collaboration and longer-term content management. MX serves a focused purpose: controlled, auditable handoffs of sensitive files between known users.
Organisations can keep content where it belongs and add a stronger exchange process where access and evidence matter most.
MX can provide a branded secure upload portal or named-user exchange route. External senders get one clear, approved destination, while the receiving team gains a more controlled record of the submission.
This helps reduce attachment-based workflows, public links and manual chasing across multiple channels.
Depending on the configured workflow, records can include the sender, named recipient, upload time, access events, downloads, restoration activity, timestamps and relevant technical details.
That evidence can support internal audit, supplier assurance, incident investigation and partner questions, while departmental ownership and retention policies remain essential.
Use the seven-day trial to assess named-user access, audit records, large file transfer and secure handoffs with up to five users.
