Temporary file sharing

Files with an end date.

Expire in minutes or days, burn after one download, revoke whenever you like.

Files that should not outlive their purpose.

On most sharing services, a link keeps working until someone remembers to turn it off, and that doesn’t often happen at all. But a file sent for one meeting or one decision usually outlives its original purpose by years and lingers in inboxes, chat histories and download folders long after it is forgotten.

We make seals to fix this. The files you share with seals have an end that you, not fate, choose in advance. And after it, the encrypted file is deleted from storage.

A set lifetime

From 5 minutes to 7 days.

Burn after one download

One download, then the ciphertext is deleted.

Revoke at will

Access closes at once for every link.

Set the end first.

  1. Drop the files

    On seal.net, in Telegram or from the CLI.

  2. Choose the end

    A lifetime, single use, or both.

  3. Send the link

    It works until the end you chose, then it stops for everyone.

A lifetime chosen up front.

The sender picks a lifetime from 5 minutes up to 7 days before the seal is created. When the time of a seal is up, it stops opening for every link in the hands of everyone, and a background worker deletes the ciphertext of the seal.

A recipient who comes too late sees that the seal is gone instead of a page that pretends that the file still exists somewhere.

A number of opens.

Seals can also have single use, which means that the ciphertext is deleted after the seal is downloaded exactly once. So you know that no one gets a second copy, however they manage to keep or circulate the link.

For greater control, the sender can pick a cap on opens from one up to 10 from the CLI, the SDK, Telegram or the browser extension, and the seal closes when that count runs out.

The SEAL server counts an open each time it hands out a download, so the limit works whichever app the recipient opens the link from.

Ending it early.

You can revoke a seal before its time is up. At the moment the seal server processes the revocation request, access closes at once for every link, and the ciphertext is deleted. And you can revoke a file of your choice, and the rest of the seal keeps working.

The signed access log of the seal shows its owner every open with the time and country of each so that it is clear if the file was taken before it was revoked.

When a week is not enough.

If a seal needs to live longer, its owner can purchase a paid tier that extends the lifetime of the seal by 3 to 12 months. The free tier gives every seal up to 1 GB and up to 7 days with every type of access rule included.

Someone who receives a link to a temporary seal does not need an account and does not need to download an app, only to open the link before the time is up, using any browser.

Questions, answered.

What happens when a seal expires?
It stops opening for everyone, and a background worker deletes its ciphertext from storage. A late visitor sees that the seal is gone.
Can a file be downloaded only once?
Yes. With single use, the first download closes the seal and its ciphertext is deleted.
Can I allow a few downloads instead of one?
Yes, up to 10, from the CLI, the SDK, Telegram or the browser extension. The web form offers single use.
Can a seal last longer than 7 days?
Yes, with one paid tier: it extends the seal by 3 to 12 months.
Read the documentation

One seal. Every platform.