Send files securely
Secure online file sending
Send files securely, with control after they leave
Move sensitive documents and large packages through a named, encrypted exchange. Permissions, expiry and activity records help the sender stay informed once the transfer begins.
Control the handoff
How to send files securely without losing visibility
Each of these is a decision somebody makes, or a default somebody accepts. Making them explicit at the point of sending is what separates a secure send from an encrypted one.
- A known recipient. Access belongs to a verified person, not to link possession.
- A controlled window. Availability has an end date chosen for a reason.
- Defined permissions. What the recipient can do is set, not assumed.
- Recorded evidence. The exchange leaves something you can refer back to.
How it works
Four steps, the same every time.
The sequence does not change with the size of the file or the seniority of the recipient. That consistency is what makes it survive a deadline.
Choose the recipient
Name the person or group who should receive the file.
Set the conditions
Apply permissions, expiry and identity checks proportionate to the material.
Send the whole thing
Move the file, bundle or complete folder without an arbitrary size limit.
Follow the outcome
See delivery, access and downloads from the same exchange record.
Three people, three requirements
A secure send has to work for everyone it touches.
Products are usually chosen by one of these three and used by all of them. A route that satisfies only the buyer tends to be abandoned within a quarter.
The sender
Needs to create the exchange in seconds, apply the right settings without deliberating and get confirmation it arrived.
The recipient
Needs to understand what they received, authenticate without help and reach a person if something fails.
The reviewer
Needs to answer a question months later without reconstructing the exchange from a mail thread.
Compared with the usual alternatives
Five common ways to send a sensitive file, and what each leaves out.
Every method here works in the sense that the file arrives. The differences are in who could open it, how long they can, and what you can establish afterwards.
Email attachment
Simple and universal. The file is copied into mail systems you do not control, cannot be recalled once delivered, and can be forwarded without your knowledge. Size limits also push the largest files elsewhere.
Password-protected archive
Better than nothing, and undermined in practice because the password usually travels the same way as the file. It also produces no record of who opened the archive.
Public share link
Convenient and forwardable by design. Possession becomes entitlement, expiry is optional, and a visit count tells you access happened without telling you who.
Consumer transfer service
Solves the size problem and little else. Recipients are typically unnamed, retention is set by the provider, and the exchange sits outside your own governance entirely.
Controlled exchange
Access is granted to a named person, availability is bounded by a decision, permissions are explicit and the activity is retained with the transaction. More deliberate at the point of sending, and considerably easier to explain later.
Layered protection
AES-256 encryption, with the patented ASR method available where the material warrants more.
ASR anonymises, shards and restores data as an additional structural safeguard alongside encryption. It is a separate method, not another word for the same thing.
Try one real send
Send something you would normally hesitate to attach.
Start a seven-day trial for up to five users. No payment card, and the recipient does not need an account of their own to receive it.