How it works

A clear flow for secrets that should not live in chat.

Shhhs separates creation, delivery, opening, request intake, vault reuse, and Team operations so each handoff has the right amount of control.

Create an encrypted secret

Paste text or attach a file, choose TTL and views, and optionally require an opening code. Free stays simple; paid packages unlock files and stronger controls.

  • Text and file modes
  • TTL and view limits
  • Opening codes on paid packages

Share a private link

Send the generated link through the channel you already use. Messaging previews receive only a generic preview, never secret metadata.

  • Preview-safe links
  • No file names in social previews
  • Manual burn remains available

Recipient opens with the right gate

The recipient opens the link directly and enters the required passphrase or OTP when configured. The secret is removed by TTL, views, or burn.

  • Passphrase/opening code
  • Conditional OTP
  • Expires by policy

Request secrets from someone else

Paid users can create reverse links where a client or vendor uploads a secret to your console without exposing it in email.

  • Reverse intake
  • Owner-only reveal
  • Enable or disable links

Reuse trusted passphrases from a vault

Paid users can keep labeled passphrases in a secure vault, see only labels by default, and reuse the right phrase for recurring contacts.

  • Labeled passphrases
  • Blurred values
  • Passkey-gated access path

Operate with Team controls

Team adds API keys, admins, branded request portals, event notifications, and audit metadata without storing secret plaintext in operational views.

  • Scoped API keys
  • Multiple admins
  • Event notifications

Use Shhhs through an MCP server

The local MCP adapter exposes secret tools to compatible agents while keeping encryption on the client side. Agents can create encrypted pushes, request links, burns, and vault-assisted handoffs without sending plaintext to Shhhs.

  • Local encryption before upload
  • Scoped Team API keys
  • Tools for push, request, burn, and vault use

Share secrets between agents

Agentic secret sharing lets one agent produce a temporary encrypted handoff for another agent or workflow. The receiving side gets a controlled link or request flow instead of secrets pasted into prompts, logs, or transcripts.

  • Agent-to-agent handoff
  • No prompt plaintext storage
  • TTL, views, and burn controls

FAQ

Does a chat preview open the secret?

No. Known messaging and social preview bots receive a generic page and no public metadata.

Can I request secrets from clients?

Yes. Paid packages include request links where someone else uploads a secret that only the owner can reveal.

Does the vault expose passphrases?

Vault values are shown blurred by default and are intended for paid accounts with stronger account security.

Can agents use Shhhs?

Yes. Team/API usage includes a local MCP adapter so agents can exchange encrypted secrets without storing plaintext in Shhhs or agent prompts.