Private Rooms

A private room for sensitive exchanges between two Shhhs tokens

Use a Private Room when one secret link is not enough. Start with an invite link or create a direct room for a known Shhhs token; recipients use their own token instead of sharing yours. The room is built for temporary credential exchange, not permanent messaging.

Two ways to start

Use an invite link when the recipient should join from any Shhhs token. Use a direct token room when you already know the other Shhhs token and want the room to appear for both participants.

  • Invite link with private browser fragment
  • Optional room passphrase
  • Direct token-to-token room
  • Two participants only

Standalone room links

A room link opens only the room, not the full workspace console. Production invites use chat.shhhs.net so mobile recipients get a focused PWA-style surface instead of the whole product console.

  • Focused recipient screen
  • Private route noindex
  • Preview-safe by default
  • chat.shhhs.net room surface

Encrypted messages with clear metadata boundaries

Invite rooms keep key material in the browser fragment, optionally wrapped by a passphrase before the recipient can open it. Direct rooms wrap access for each token. The Worker stores encrypted messages and operational metadata such as timestamps, status, limits, and participant references.

  • Message plaintext is not stored by the Worker
  • Admin views stay metadata-only
  • No AI processing on room messages
  • Passphrase unlock stays client-side

Limits are part of the product

Private Rooms are intentionally bounded. Pro, Team, and Enterprise accounts get active-room and per-room message limits so sensitive exchanges stay scoped.

  • Pro: 10 active rooms and 250 messages per room
  • Team: 50 active rooms and 500 messages per room
  • Enterprise: 200 active rooms and 1,000 messages per room

Where Private Rooms fit

Use Private Rooms when a credential handoff needs questions, confirmation, or short back-and-forth: a client sends access, an operator asks one follow-up, or an agent-assisted workflow needs a bounded place to coordinate.

  • Client credential clarification
  • Vendor onboarding
  • Password reset coordination
  • Incident access handoff
  • Agentic secret exchange

Mobile path before native apps

Standalone room links are the first mobile surface: a participant opens only the room on a phone, without the full console. Native apps can later build on the same token-to-token room model.

  • Open only the room surface
  • Token-to-token handoff
  • PWA/deep-link friendly

Not a replacement for team chat

Slack, Teams, WhatsApp, and email are built for memory, search, previews, and forwards. Shhhs Private Rooms are for short sensitive exchanges that should expire. Private Rooms give Shhhs a paid use case that ordinary password send tools rarely cover.

  • Temporary encrypted chat
  • No permanent team history
  • No message previews
  • Paid product differentiator

FAQ

Is Shhhs Private Rooms a normal chat app?

No. It is a short-lived encrypted handoff room for secrets and operational context, not a permanent messenger.

Can Shhhs read room messages?

Room message content is encrypted locally before upload. The server stores ciphertext and operational metadata only; optional room passphrases are used client-side to unlock the room key.

Can a recipient open only the room?

Yes. A standalone room link opens the room experience without loading the full Shhhs console.

When should I use a Private Room instead of Send?

Use Send for one-way delivery. Use a Private Room when the secret handoff needs short, temporary back-and-forth between two tokens.