Skip to content

Proof page · how it protects

Honest encryption for shared teams.

No zero-knowledge claims. Server-side XSalsa20-Poly1305 (libsodium secretbox) with system-managed keys is the trade-off that makes sharing, recovery, and admin reset possible.

Four facts, each with a consequence

  1. Managed encryption, honest trade-off

    Vault keys are wrapped server-side with the system key and contents sealed with XSalsa20-Poly1305. That is what makes sharing, recovery, and admin reset possible. Zero-knowledge end-to-end encryption is an explicit, deferred non-goal.

  2. Sharing with a floor, not a free-for-all

    Organization roles set the floor: member reads, admin writes, owner deletes. Shares only raise permission above that floor, and expiring links close themselves.

  3. Recovery instead of lockout

    Lost master passwords do not mean lost vaults. Recovery contacts or an admin reset bring the team back without shared spreadsheets.

  4. Health you can act on

    Reports flag weak, reused, and aging passwords so every vault gets a concrete next step.

Roles are the floor

Member reads, admin writes, owner and root delete. Emergency access and expiring shares build on top — they never punch through the floor.

Role permission floor
RoleVault power
memberread
adminwrite
owner / rootdelete