Protocol / Distribute
Store ciphertext everywhere. Trust nowhere.
Remote infrastructure only receives encrypted material. Distribution improves durability without asking storage nodes, hosts, or operators to become trusted readers.
Stored material
Ciphertext
Fragments are unreadable without the key
Storage layer
Distributed object storage
Readable by SEES
Never
No server-held decryption key
01Sealed payload
02Upload object
03Distributed storage
04Fetch ciphertext
05Decrypt locally
Design ruleMinimize what infrastructure can know. Make the unavoidable trade-offs visible.
01 / UPLOAD
Only sealed vault material crosses the boundary.
The browser sends encrypted blobs and required metadata, not plaintext notes. Infrastructure can route and store the object, but it should not be able to understand what the object contains.
Ciphertext onlyNo plaintext transportOpaque objects
02 / DURABILITY
Distribution is for resilience, not permission.
Storj handles distributed storage while SEES keeps the trust boundary at the client. Nodes can hold pieces of data, but the decryption capability remains with the user.
Distributed storageClient-held keyNo readable nodes
03 / RETURN
Reads complete the same loop in reverse.
When you unlock a vault, the app fetches ciphertext, derives the same local key from your passphrase, and decrypts in the browser. The server remains a courier, not a reader.
Fetch encryptedDecrypt localServer stays blind
Continue the protocolIdentity
Need the complete threat model?Read security