01
Invite rooms
An invite room creates a standalone link with private key material in the fragment. The recipient joins with a Shhhs token and the route is noindex/noarchive/no social preview.
- Standalone /room route
- Fragment invite material
- Noindex
Private Rooms guide
Private Rooms turn sensitive back-and-forth into a bounded product flow: two participants, ciphertext storage, plan limits, expiry, and standalone links that avoid loading the full app shell.
01
An invite room creates a standalone link with private key material in the fragment. The recipient joins with a Shhhs token and the route is noindex/noarchive/no social preview.
02
A direct room is created for another known Shhhs token. The room appears for both tokens without a manual invite fragment exchange.
03
Private Rooms are paid-only. Pro, Team, and Enterprise have explicit active-room and message-per-room limits to keep the product bounded.
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 should say local/client-side encryption and metadata-only operations. Do not claim formal E2EE, 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.