Secure document sharing

The NDA comes before the first byte.

A signed agreement, a password, single use and a signed record of every open.

Documents that stay inside the deal.

When sending a term sheet or an M&A case file, you usually just leave it as a plain email attachment. And from the moment you do that you know nothing about where it goes. The recipient may forward it to a whole cast of advisors. The document may be leaked. Or it might just be forgotten in some email server’s attic.

It’s not that the people sending these emails like to lose control of their documents. It’s that they haven’t had a way to avoid that till now.

They also want the recipient to sign some kind of agreement before seeing anything, and they want a record showing that the recipient did.

NDA before access

The recipient signs before any file opens.

The signing on record

A signed log entry with the time and a hashed name.

Encrypted on your device

The server holds ciphertext, not your documents.

From document to signed access.

  1. Add the documents

    Drop the files on seal.net and open the settings.

  2. Turn on the NDA

    Type the agreement or attach it as a file, and add your email.

  3. Send the link

    The recipient reads the agreement, types a name and signs before anything opens.

  4. Keep the record

    The owner page shows the signing and every download. Download the log as JSONL.

The NDA gate.

When the recipient visits the link, she sees the agreement. She has to scroll through the whole thing to continue. The recipient also types in her first and last name, and draws a signature.

You write this agreement, or if you have it written as a document, you can attach that. When you set up the seal, you also specify an owner email.

If the document shown to the recipient is a normal NDA from a file attached by the sender, we also show a digest of that file on the page that the recipient signs. If you attached a document, their signature covers that exact document.

The record of the signature.

The signing of the agreement becomes its own entry in the access log of the seal, with the time and salt hashes of the first and last names. The same access log records every subsequent open and download, with the time, country, and network subnet.

Each log entry is signed with the Ed25519 key of the SEAL server, at the instant when it’s written.

More conditions on the same seal.

If you want, you can also put a password on top of the agreement. The password needs to have 6 to 10 characters. The main difference between passwords and agreements is that you’ll usually have to send the password to the recipient over another channel, the way you’d send a password via SMS.

When you create a seal, you can specify a lifetime of 5 minutes to 7 days. The server will delete any seal set to single use after it’s been downloaded once.

What the SEAL server holds.

Because the server enforces the gate rather than just showing a document with a disclaimer at the top, nothing in the seal is released to the recipient until they have signed the agreement. All the server has to do is not give them the first bit, and they have no way to get anything.

Questions, answered.

What does the recipient sign?
The wording you typed or the document you attached. An attached document is shown with its digest, so the signature covers that exact document.
Can the recipient see the files before signing?
No. The server releases no file of the seal until the agreement is signed.
What is recorded about the signing?
A signed entry in the access log with the time of signing and salted hashes of the typed name. Later opens and downloads are logged too.
Can I combine the NDA with a password?
Yes. Add a password of 6 to 10 characters and send it over another channel. Single use and an expiry work on the same seal.
Can I revoke access after the document was opened?
You can revoke the seal or a single file at any time, and nothing more can be downloaded. Copies already downloaded stay with whoever downloaded them.
Read the documentation

One seal. Every platform.