Scrinium encrypts note bodies and titles on your device before local database storage or upload. Random account, vault and note keys protect the data; a key derived from your password wraps the Account Key. Account and sync metadata still exist on the server. The threat model explains the limits, including compromised devices and clients.
Unwrapped account and vault keys exist in browser memory while the vault is unlocked. Stored copies are encrypted. After a refresh or closing the tab, you need to unlock again. An unlocked browser can display readable notes, and a plaintext export remains readable outside the vault.
Your password runs through Argon2id (a memory-hard key derivation function) to produce a Master Unlock Key. That key encrypts your Account Key, which encrypts your Vault Key, which encrypts a unique Note Key for every note. Each note body and its title are sealed with XChaCha20-Poly1305.
The service stores an SRP verifier for login, wrapped account and vault keys, encrypted note blobs, your account email, and account and sync metadata. Email verification alone cannot decrypt your notes.
The sync service does not receive your master password, unwrapped decryption keys, or plaintext note bodies and titles. Search runs locally over notes decrypted in memory while the vault is unlocked.
A matching recovery key can unlock an existing local vault without the password. It does not download your cloud vault into an empty browser. Keep it outside this browser. Without the password, matching key, unlocked copy or readable export, the service cannot decrypt the notes for you.
After email verification, the connected browser uploads encrypted changes and pulls server updates. Another open browser may need Sync now to receive an edit. Conflicting edits use modification timestamps; they are not merged like a shared document. Keep backups separately because sync carries deletions too.