Request secrets without exposing an inbox.

Private by design

The product is built around short-lived handoffs and clear deletion windows.

• No AI processing on your secrets
• No tracking inside secret content
• No recovery promise that weakens privacy

Packages match the workflow

Use free for simple text, Pro for recurring individual handoffs, and contact us for Pro workspaces when APIs and operations matter.

• Pro adds recurring paid controls
• Workspace is contact-based while plans are updated
• Workspace adds APIs and admin controls when enabled

Common use cases

Use Shhhs for passwords, API keys, SSH keys, recovery codes, client credentials, vendor onboarding, and temporary project access.

• Send a password once
• Request credentials from a client
• Burn access after a handoff

Why it is different from chat

Chat and email retain history, previews, search indexes, and forwards. Shhhs creates a temporary handoff with explicit expiry and metadata boundaries.

• Preview-safe public links
• Time and view limits
• No secret content in audit or support

Buyer guide

Free is enough for a simple text handoff. Paid packages fit client work, files, opening codes, and request intake. Pro and Workspace make sense when secret handoffs become a repeated operating workflow.

• Free for simple text
• One-shot packages for client handoffs
• Pro and Workspace for recurring operations

Automation without leaking prompts

The CLI, API, and MCP adapter let scripts and local agents create encrypted handoffs without placing plaintext secrets in prompts, terminal history, tickets, or permanent logs.

• Hidden CLI input
• Encrypted API payloads
• MCP handoffs for agents

FAQ