SEAL for Slack
Encrypted file sharing where your team already talks.
One /seal command set, ephemeral responses, nothing sensitive in channel history.

Channel history is forever. Your files shouldn’t be.
Everything posted in a Slack channel is searchable by everyone who ever joins it. SEAL for Slack keeps the convenience and removes the permanence: files are encrypted before they reach SEAL storage and shared as expiring capability links, while every command response is ephemeral, visible only to you, never written into channel history.
Under the hood it is the same SEAL: zero-knowledge backend, one wire format, links that open on seal.net for anyone, including people outside your workspace.
Share links, OTPs and owner tokens never land in channel history.
Send the bot a file; 1h, burn, max=3, password=… or geo=US,DE in the same message set its rules.
Ownership keys on (workspace, user); owner tokens encrypted at rest.
A direct message, and /seal for the rest.
Install once
Add the SEAL app to the workspace; every member gets the /seal command set.
Send the bot a file
In the direct message with SEAL. The bot encrypts it and answers with a link for the recipient and a manage link for you, visible only to you.
Links stay yours
Responses are ephemeral. You decide what enters the channel.
A workspace adds SEAL once; it runs on SEAL’s servers, as the Telegram bot does. /seal manages what you sealed: list, status, files, share links, revoke, your defaults and language.
What Slack sees.
The Slack client encrypts on the bot host, so file bytes transit Slack’s infrastructure in plaintext before encryption. That is the same honest boundary as any chat-bot integration. The SEAL backend stays zero-knowledge either way. For device-only E2EE, use seal.net or the CLI.
Questions, answered.
- Who is this for?
- Teams that already live in Slack and hand off files that carry weight: legal, finance, people ops, healthcare. If pasting a contract into a channel feels careless, seal it instead.
- How do I send a file?
- Open the direct message with SEAL and upload the file there: a slash command cannot carry a file. Paste a SEAL link into the same DM to receive its files there.
- Will people outside our workspace open the files?
- Yes. Recipients get a normal seal.net link that opens in any browser, no Slack and no account required.
One seal. Every platform.