Client-side backup encryption
Cloud storage receives encrypted repository data, not readable customer files.
- Data encryption
- AES-256-GCM
- Encryption location
- Customer device
- Storage contents
- Encrypted repository objects
The vault key belongs to the client
The desktop app generates a random per-account master key. It wraps that key locally in a versioned envelope and uses it to open the Kopia repository. SaveState’s hosted API stores the encrypted envelope and a one-way possession verifier, not the plaintext master key.
Short-lived, account-scoped storage credentials authorize repository access. Possessing storage objects or an API database record is not enough to decrypt customer backup contents.
A precise security claim
SaveState calls this client-side encryption. The account password is still sent to the SaveState API over HTTPS for account authentication, so the product does not claim strict zero-knowledge authentication. The backup contents and their decryption material have a separate client-owned boundary.
Put this feature into a recovery plan
Install SaveState on Windows, protect a representative data set, and test the restore before it is urgent.
Choose a plan