Private Rooms guide
Private Rooms turn sensitive back-and-forth into a bounded product flow: Pro workspace and Enterprise group rooms, ciphertext storage, plan limits, expiry, and standalone links that avoid loading the full app shell.
01
An invite room creates a standalone link on chat.shhhs.net with private key material in the fragment. When passphrase lock is enabled, the fragment carries a wrapped room key and the passphrase is needed locally before joining.
02
A direct room is created for known Shhhs participants. Pro workspaces and Enterprise can address multiple participants for bounded group rooms.
03
Private Rooms are paid-only. Pro and Enterprise add group capacity with active-room, participant, and message-per-room limits.
04
Rooms expire according to plan and lifecycle state. Users should burn or close rooms when the sensitive exchange is complete.
05
Use rooms for client credential clarification, vendor onboarding, temporary access coordination, incident handoff, or agentic coordination. Do not use them as permanent chat history.
06
Public copy may say room message content is end-to-end encrypted between participant browsers when backed by this client-side room-key flow. Keep the metadata boundary explicit and do not claim deletion guarantees or external certifications without evidence.
No. Public guides never include secret identifiers, room ids, full private URLs, fragments, filenames, or payload-derived text.
No. It is product documentation for deployed boundaries. External audits, DPAs, SLAs, and certifications require separate evidence and review.
No. Shhhs support can help with billing and metadata-only support, but cannot decrypt or recover secret content.