Hi Product Hunt — we're building SecretBridge.app for a familiar handoff: someone needs a password or API key, but you don't want the value sitting in chat history.

You can try the browser flow immediately, without an account: paste a value, choose expiry and reveal controls, and create an encrypted link. Optional passphrases add a separate check. The complete link is sensitive access material, so share it carefully and send any passphrase separately.

For teams, the Slack and Microsoft Teams integrations add recipient handoffs and receive channels. Someone can give a sender a random receive ID instead of putting their address in a public directory. Installation depends on your organisation's app policies; the Teams custom-app route can need an admin.

Receiving is free. Each verified platform user gets one free receive-channel creation per UTC month; paid seats unlock platform sending and more channel creation, subject to safety limits. Personal purchases are scoped to that verified user; organisation seats are explicitly assigned.

The security boundary matters: anonymous browser links encrypt and decrypt in the browser, with key material in the URL fragment. Native platform modes have different boundaries and can involve server-side decryption. Expiry and burn restrict future service access; they cannot erase a copy someone already saved.

We'd value practical feedback: does this make the next credential handoff easier, and where does your team's current process get in the way?

Hi Product Hunt — we're building SecretBridge.app for a familiar handoff: someone needs a password or API key, but you don't want the value sitting in chat history.

We'd value practical feedback: does this make the next credential handoff easier, and where does your team's current process get in the way?

SecretBridge.app

Browser-encrypted secret links, plus Slack and Teams

Browser-encrypted secret links, plus Slack and Teams