Capsule

Send documents that expire, cap views, and can be revoked

Storage

Privacy

Security

Visit WebsiteSee on Product HuntTwitter ⧉

Hi Product Hunt 👋 I built Capsule because of a specific moment I kept having: attaching a signed contract to an email, hitting send, and realizing I now had no idea where that file would end up or who would open it. There is no undo on an attachment. The usual fix is a portal. But a client who receives three documents a year will not remember a portal password — they email and ask for the file, and you attach it, and you are back where you started. Portals do not fail technically. They fail because they put the cost of security on the person with the least reason to accept it. So Capsule puts the rules on the document instead of on the recipient. You set an expiry, a maximum number of opens, optionally a password or a verified email address. They click a link and read it. You can revoke it at any point, including after they have opened it, and every open is recorded with a timestamp — a record that survives the link expiring, because arguments about who saw what happen much later than the send. For the sensitive end of the spectrum there is optional end-to-end encryption: the document is encrypted in your browser and the key lives in the URL fragment, so it never reaches our servers. It is off by default, because turning it on means no previews, no search, and no recovery if the link is lost. That is a real trade and I would rather say so than bury it. Free to start, and Teams is a flat monthly price instead of per seat. Happy to answer anything — especially the skeptical questions about the encryption model.