Give out a FlyaDoc address. People fly files to you.

Get your address

FlyaDoc is an addressing service for the digital age, a fax number for files. Claim your own address, like yourname@flyadoc.com, share it, and anyone can fly you a file, whether a document, a photo, an audio note or a video, straight to your box. It lands locked before it leaves their browser, and opened on any browser you sign in on. DocButterfly holds a key to your box so that it can do that, which means DocButterfly can open your files. Every time it does is listed in your box.

And every transfer is witnessed. Both sides fingerprint the file themselves, and DocButterfly records that the two fingerprints matched, so you each end up holding a receipt that says the same bits arrived. It never opens the file.

How it works

1. Claim your address

Pick a FlyaDoc address, a short handle that is yours. It is the one thing you hand out, the way you used to hand out a fax number.

2. Share it

Put your address on a card, in a signature, on a form. Anyone can fly you a file from their browser, whenever it suits them. Your box takes a file while you are away, so you never have to be there.

3. It lands locked

The file is locked before it leaves the sender's browser and waits in your box until one of your own browsers opens it. It can flow on to your own Dropbox, OneDrive, Google Drive, SharePoint or SFTP if you set that up.

Set up your FlyaDoc box to claim an address and choose where your files land. Setup starts by creating a free account, because an address has to belong to somebody: receipts name the owner, and token billing needs an account to bill.

Or send a file live

FlyaDoc also hands a file straight from you to another person, with a signed receipt if either of you asks for one. It does not read the file, and it does not keep the file.

What FlyaDoc is

A way to hand a file to a person and keep proof it arrived. You get an address that reads like an email address and is not one, they fly a file to it, and it is locked in their browser before it leaves.

What makes it different from sending a file any other way is the witness. Both browsers fingerprint what they handled and report that fingerprint, and DocButterfly writes down whether the two matched. It is not a claim that DocButterfly checked your file, because it never had your file. It is a record that the two of you handled the same bits, and you both hold it.

How a live handover works

1. You send it

Pick a file and get a link, or a six-character code to read out. A document, a photo, an audio note, a video: whatever you need to hand over.

2. They receive it

They open the link or type the code while you are both on the page, and the file goes straight from your browser to theirs. Each side computes a digest of what it handled and reports that digest back.

3. A receipt, if you want one

Both of you see whether the two digests matched. Whoever asked for a receipt is emailed a signed copy; if nobody asked, no receipt is written.

Both of you have to be there at the same moment for the handover above. If the other person is not around, your FlyaDoc box takes a file while you are away: they drop it at your address, it is locked before it leaves their browser, and opened on any browser you sign in on.

Any kind of file

FlyaDoc is not just for paperwork. It carries the whole range of things people actually send each other:

Documents
Images
Audio
Video

What DocButterfly witnesses, and what it does not

DocButterfly is the neutral witness in the middle. It knows the exchange took place; it never has what was in it. When one of you asks for a receipt, the signed record holds:

  • The parties: the two accounts that sent and received.
  • The hashes: the digest both sides independently reported, and the size.
  • The connection: the encryption fingerprints each browser saw, so the safety code can be checked later.
  • A transaction id: the reference that resolves back to that record.

It never holds the file. It does see the file's name and size, because each browser reports them alongside its digest so the two sides can be matched, and the receipt you are emailed names the file. DocButterfly's transaction lookup leaves the file name and both email addresses out. If neither of you asks for a receipt, none is written.

Read the receipt wording carefully

It is deliberate. The receipt says both parties reported the same digest. It does not say DocButterfly checked the file, because DocButterfly never had the file. That is the honest claim, and it is the only one we make. If the two reported digests do not match, the receipt says that instead; it never reads as "complete" when the halves disagree.

Part of DocButterfly

FlyaDoc rides on the same platform as the rest of DocButterfly. Once a file lands, the same account can convert it, read it, pull the fields out of it, get it signed, or file it in a vault you control, from the portal or from your own code over a REST API. See how FlyaDoc works, or read about DocButterfly.

Get started

Here is what happens, in order:

  1. You claim a FlyaDoc address, like yourname@flyadoc.com, and get a box that takes files while you are away.
  2. Anyone can fly you a file. It is locked in the sender's browser before it leaves, and opened on any browser you sign in on.
  3. Sending is billed in tokens, and the sender pays the whole send to a box: a send of up to one gigabyte is 76 tokens, which covers both halves of the transfer and both receipt copies. A new account starts with a monthly allowance of 500 tokens at no charge, enough for 6 sends that size.

The account comes after you know all that, and it exists for two reasons: sending is billed in tokens, and a receipt has to name who sent and who received. Both take an identity.

Create a free account
What a receipt records
  • Who sent and who received
  • The digest both sides reported
  • A transaction id you can reference
  • Written only when one of you asks
  • Never the file itself
Read the documentation