Privacy Policy
No account profile. No ad graph. No readable secrets.
What SEES stores, what infrastructure can observe, and why privacy here starts with removing data instead of promising to behave.
PrincipleIf SEES does not need it to operate the vault, SEES should not collect it.
01 / COLLECTED
You do not need an email, phone, or profile.
SEES does not ask for an account identity. The app may still involve standard connection metadata such as IP address and user agent because every web service needs that to respond.
No emailNo tracking cookiesNo adsNo profile
02 / STORED
Remote storage contains opaque or encrypted material.
- Encrypted blobs for notes and activity data.
- Opaque identifiers used to find vault records without exposing plaintext content.
- KDF metadata like salt and iteration count, which are needed but not secret.
03 / THIRD PARTIES
Storj stores ciphertext; hosting serves the app.
Storage provider
Storj and hosting infrastructure may process operational metadata for delivery and security. They do not receive your passphrase or decryption key.
Last updated: 23 July 2026