The encryption model

Sensitive vault content is encrypted before it ever leaves the device that created it. The server is designed to persist only encrypted payloads and wrapped key material — never plaintext secrets.

Each vault item is protected by its own data key. That data key is wrapped by the vault's key, and the vault key is in turn wrapped by key material held by each authorized member. This layering means removing a member's access to a vault does not require re-encrypting every item in it — only re-wrapping the vault key.

The server can see metadata needed to route and authorize requests — item counts, timestamps, sharing relationships, and audit events — but not the protected content itself. This is a deliberate boundary: the server enforces authorization without needing to be trusted with your secrets.