Trust Center
Trust in Shhhs is based on verifiable boundaries: client-side encryption for supported secret content, metadata-only operations, no secret recovery, and no AI processing on secrets. Legal company details, external audits, SLA terms, and formal DPA links remain unpublished until reviewed.
01
Supported secret content is encrypted by the client before upload. Shhhs stores and transfers ciphertext plus the operational metadata required to enforce access and lifecycle rules.
02
Shhhs does not read, profile, train on, index, or sell secret content. Operational metadata exists only where needed for lifecycle, abuse control, billing, audit, and support boundaries.
03
A public external status provider is required before Shhhs publishes uptime history or incident automation claims. Until that URL is configured, this page does not claim an external SLA or uptime record.
04
Current public subprocessors are described by function and boundary. Shhhs does not use subprocessors to process plaintext secret content with AI or analytics.
05
Formal Terms, Privacy, DPA, acceptable-use, refund, and company-registration links remain gated until reviewed inputs are configured. Public pages avoid placeholders and unsupported legal commitments.
06
Responsible disclosure is accepted through the contact flow until a dedicated security contact or reporting URL is configured. Reports must use test data and must not include live secrets.
No. There is no AI processing on secret content.
No. Secret recovery would weaken the privacy model.
Support can help cancel billing after billing validation, but cannot restore account access or secret content.