Your files tell the story of your business. Proposals, designs, contracts, patient records, every exchange needs speed, control, and proof. My MX Data is built for that exact moment: secure file sharing for business where the right person gets the right version, and every action is recorded for accountability. Teams can keep drafting in their usual tools, then hand off through MX with named user access, end to end audit trails, and protection designed with future threats in mind.
Table Of Content
- Security by design, not by settings
- Why the right security features matter at scale
- Features to outcomes, at a glance
- Short FAQs
- Is MX a replacement for my cloud drive
- Does MX help with GDPR and ISO 27001
- How does MX handle very large files
- How is MX different from link based sharing
- Five habits that raise your sharing security
- Always use named recipients
- Apply expiry and download limits by default
- Keep decisions with the file
- Route sensitive deliveries through MX
- Adopt quantum-aware protection
- Fit MX into your existing workflow
- Here’s what counts
- Essential Reads
- Sources
Security by design, not by settings
Here is what makes MX a protective layer teams can rely on.
- Named user exchange: Files go to specific people, not open links. Named usersOnly verified, specified recipients can access the file. This prevents link forwarding and accidental exposure. reduce uncontrolled spread across the 800 plus external domains many businesses already touch. Source
- Strong cryptography: 256 bit AES protects files in transit and at rest, while the ASR model and quantum secure patented methodology are built to reduce long term exposure in a market where post quantum adoption is still very early. Source
- Evidence on tap: Audit trailsEvery view, download, and action is captured with time, user, and origin details for accountability. show who accessed a file, when, and from where.
- Fine grained controls: Expiry, download limits, and recipient permissions keep exposure windows shorter and the blast radius smaller.
- Data sovereignty: Storage regions can be chosen for shards to support contractual and regulatory obligations. Data sovereigntyThe ability to specify jurisdictions for processing and storage to align with regional requirements. is available for enterprise needs.
Why the right security features matter at scale
Cloud sharing is pervasive, so small improvements pay back quickly. Thirty nine percent of business data in the cloud supports sharing. Source The average enterprise uses fifty seven sharing tools and exposes data to hundreds of external domains. Source In that kind of sprawl, controls that move with the file matter more than broad tenancy settings alone.
Features to outcomes, at a glance
Security that translates into business results.
| MX Feature | What it does | Business impact |
|---|---|---|
| ASR model | Anonymise, Shard, RestoreData is anonymised, split into cryptographic shards, and restored only for authorised recipients. | Resilience against decryption attempts, reduced single point exposure |
| Named users | Restricts access to specified people, with no public link sharing | Less oversharing, clear accountability |
| Audit trails | Tracks views, downloads, and actions with context | Proves control for clients, regulators, and boards |
| Expiry and limits | Time bound access, optional download caps | Smaller attack window, better hygiene |
| Data sovereignty | Specify shard locations by region | Supports contracts and regulatory obligations |
| Unlimited file sizes | Optimised speed for very large datasets | Designs and media move fast, no size workarounds |
Short FAQs
Quick answers to common security questions.
No. MX specialises in secure, controlled exchange, not long term storage or real time editing. Keep your storage and editors, then use MX as the traceable delivery layer. See enterprise file sharing.
MX supports unlimited file size transfer with speed optimisations and version control. See Large File Sharing and speed guidance.
MX exchanges are restricted to named users and carry end to end logs. Files are protected with 256 bit AES, the ASR model, and a quantum secure patented methodology. Learn more about encrypted sharing.
Five habits that raise your sharing security
Set these defaults across teams and vendors.
Always use named recipients
Replace public links with named user access. It cuts accidental forwards and clarifies responsibility.
Apply expiry and download limits by default
Shorter access windows lower risk. It also facilitates audit readiness for regulated projects.
Keep decisions with the file
Use MX Conversations so context never splinters across chat apps. Faster approvals, fewer reworks.
Route sensitive deliveries through MX
Finance, healthcare, legal, and IP-heavy work should use auditable handoffs rather than email attachments or open links.
Adopt quantum-aware protection
Prepare for harvest-now, decrypt-later threats with the MX ASR model and quantum secure patented methodology. See Quantum Proof Encryption.
Fit MX into your existing workflow
MX complements the tools you already use. Draft in Google Docs or Office, store in your DMS, then send sensitive outcomes through MX. Use the API to capture metadata in engineering or finance systems, and rely on version control so recipients always see the latest file. For a deeper tour, visit the Features page, compare against WeTransfer, or read how the same model carries into Accelerating File Transfers and Secure Collaboration Essentials.
Here’s what counts
Security features only matter if they make sharing faster to do right. My MX Data delivers controlled, auditable exchanges with named users, end to end logs, expiry controls, data sovereignty choices, and a quantum-aware ASR model that helps teams protect sensitive outcomes at scale.
