User guide
How humans use Shhhs for temporary secret handoffs.
Core model
Shhhs is built around temporary handoffs. A sender creates a protected object, shares only the intended access material, and the object expires by time, views, burn action, or owner cleanup.
- Use short TTLs for routine handoffs
- Use opening gates for higher-risk recipient flows
- Use request links when the other person needs to send a secret to you
Accounts
Free use is token-first and local. Paid accounts add stronger account-management controls such as passkeys and recovery codes. Shhhs support can help with billing metadata but cannot recover secret content.
- Save the account token locally
- Register passkeys where available
- Generate and store recovery codes for paid accounts