Security
We built it so we
cannot read your files.
Privacy that depends on trusting a company is a promise. Privacy that comes from the design is a property. Ferry is built for the second kind.
How it works
Six decisions that protect a transfer.
Sealed in your browser
Each file is encrypted on the sending device. The server only ever handles bytes it cannot read.
Keys stay with you
Keys are made on your devices. For a link, the key sits in the part after the # symbol, which browsers never send to a server.
Direct when possible
Devices connect to each other first. A relay is used only when a direct path fails, and it carries encrypted traffic.
Verify the person
Paired devices show a short code that you can compare, so you know you are talking to the right device.
Short lives
Held files expire on a date you choose, up to 7 days, and you can remove one sooner.
Open source
The code is public under the MIT licence. Every claim on this page can be checked against it.
What we do not claim
Being honest about limits is part of security.
- Ferry has not had an independent security audit.
- It does not hold a SOC 2 or ISO 27001 certification.
- Anyone who has a link with its key can open the file, so share links with care.
- Ferry cannot protect a device that is already compromised.
Report an issue
Found a weakness? Tell us.
Report it privately, with steps to reproduce it, using the feedback page. Please give us a reasonable time to fix a problem before you publish it. See also the subprocessor list and the privacy policy.