Send files securely, with proof built in

01. How does MX ensure secure file sending?

MX secures the full file handoff rather than relying on a password attached to an email or an open sharing link. The sender assigns the exchange to a known recipient, applies the relevant permissions and keeps visibility over what happens afterwards. This creates a more controlled route for contracts, client records, financial packs and other sensitive business information.

Protection is applied through several connected controls:

• Named-user access: The file is assigned to an authorised recipient rather than anyone who obtains a public URL.
• Layered protection: AES-256 is combined with the quantum secure patented ASR methodology, which anonymises, shards and restores the file.
• Transfer rules: Expiry dates, permissions and download limits help match access to the purpose of the exchange.
• Recorded activity: Relevant events are written to an audit trail so the organisation can explain the handoff later.

The ICO's encryption guidance explains why encryption should sit within a wider approach to information security. MX follows that practical principle by combining technical protection with identity, access and evidence.

For a closer look at the underlying approach, visit the encrypted file sharing page.

02. Can I track who receives and accesses files on MX?

Yes. Traceability is central to the MX exchange model. The platform is designed to help organisations move beyond the vague status of an email attachment or forwarded link by maintaining a record of the key events around each transfer.

Depending on the workflow and controls applied, teams can retain visibility over:

1. Who the file was assigned to: Recipient access is tied to a named user rather than a reusable public link.
2. When the exchange progressed: Delivery, access and download events can be time-stamped.
3. What happened afterwards: Audit records provide evidence for operational follow-up, client assurance and internal review.
4. When access should end: Expiry controls help prevent a file remaining available without a continuing business need.

This evidence does not replace an organisation's wider governance responsibilities, but it can make sensitive exchanges more accountable. The ICO accountability principle emphasises the need for appropriate measures and records that demonstrate how personal data is handled.

These controls are especially useful when teams need traceable file sharing with clients and external advisers.

03. What protection does MX use during a file transfer?

MX uses AES-256 protection alongside its quantum secure patented methodology, known as Anonymise, Shard, Restore. The important point is not a claim of invulnerability. It is the way MX reduces exposure by changing how a file moves and how it becomes readable to the recipient.

The ASR process works in three stages:

• Anonymise: Identifying context is separated so the protected data is less useful if encountered outside the authorised workflow.
• Shard: The file is divided into protected fragments rather than travelling as one complete readable object.
• Restore: The fragments are brought back together only for the named, verified recipient.

This approach adds another layer around conventional encryption and supports a future-focused security posture without making careless or absolute promises about being impossible to compromise. The NCSC secure communication principles provide useful context for assessing identity, service security and communication risks more broadly.

Organisations can also use MX for controlled B2B file exchange where the same protection must extend across company boundaries.

04. Does MX make secure file sending compliant?

No platform can make an organisation compliant by itself. Compliance depends on the data involved, the lawful basis for processing, organisational policies, staff behaviour, supplier management, configuration and wider technical measures. MX should therefore be described as a platform that helps facilitate compliance, not one that guarantees it.

MX can support compliance objectives by giving organisations practical controls around sensitive exchanges:

• Access restriction: Named recipients and identity checks help reduce uncontrolled distribution.
• Audit evidence: File activity records can support reviews, client questions and regulatory audits.
• Expiry management: Access can close when the transfer has served its defined purpose.
• Data sovereignty options: Regional controls can assist workflows with jurisdictional requirements.
• Layered security: AES-256, ASR and permissions contribute to stronger information governance.

The official ISO/IEC 27001 overview frames information security as a combination of people, policies and technology. That is the right context for evaluating MX as part of an organisation's wider control environment.

Read more about how MX can support GDPR-aligned file exchanges without overstating what software alone can achieve.

05. What types of files can I send securely with MX?

MX can support everyday business documents as well as files that are too large or sensitive for email. The platform is not limited to one sector or format. What matters is that the file needs to move between known parties through a controlled and auditable process.

Common examples include:

• Legal and professional services: Contracts, disclosure bundles, case material and confidential client documents.
• Finance and accounting: Board packs, working papers, transaction records and regulated reports.
• Engineering and manufacturing: CAD assemblies, BIM models, drawings, specifications and supplier packages.
• Healthcare and research: Imaging datasets, research archives and information that requires careful access handling.
• Media and technology: High-resolution video, software builds, project archives and large source files.

MX does not impose a fixed upper file size limit, so teams do not need to divide a large package solely to fit a consumer service cap. The NCSC cloud security guidance also highlights the importance of identity, access control, observability and ongoing protection when cloud services handle business information.

For especially heavy payloads, see how MX supports secure large file sharing without turning the exchange into a storage project.