Your data is encrypted on your device, keys never leave your device unencrypted, and the server in the EU sees only the encrypted contents of your vault, which it cannot decrypt. This is called zero-knowledge architecture. Here's what happens to your data — technically, but understandably.
AES-256-GCM
AES-256-GCM (Advanced Encryption Standard, 256-bit key, Galois/Counter Mode) is an international encryption standard and the encryption Geslar uses for your data.
256-bit key
2²⁵⁶ possible keys — a 78-digit number, so guessing the key is practically impossible.
GCM mode
Provides both encryption (data is unreadable) and authentication (data hasn't been tampered with). If a single bit changes, decryption fails.
Unique IV per operation
Each encrypt operation uses a fresh random initialisation vector. The same data encrypted twice produces completely different output.
Argon2id — from password to key
Your master password is not the encryption key. It goes through Argon2id (a memory-hard key derivation function):
Master password + random salt (128 bits, unique to your account).
Argon2id — deliberately slow and memory-hungry.
The result unlocks your randomly generated root key, which in turn unlocks your vault and item keys. The data itself is encrypted with AES-256-GCM.
Argon2id's memory requirement makes GPU attacks costly: every guess takes real memory and time. A weak password is still weak — so choose a long master password.
Only encrypted data is stored; your master password is never stored. You choose how long Škrinjar stays unlocked on a device; when that time runs out or you restart the browser, you need to unlock it again. When you lock your vault or close the browser, the key is wiped from memory.
Zero-knowledge architecture
What this means
The server never sees your data in readable form. We don't have your master password, your encryption key, or your decrypted data — we can't decrypt your vault even if we wanted to. Shared vaults can be opened by the members you share them with, and in business organizations the organization's vaults can be opened by the organization's owner and administrators. Geslar can't open them even then.
If someone breaks into Geslar's server
They get only the encrypted contents of your vault, without the key. Without your master password (or recovery key), the data is useless.
If someone steals your device
While Škrinjar is locked, they see only encrypted data. Without your master password (or recovery key) they can't open it — even with access to the disk.
If you forget your master password
When you register you get a recovery key — a second, independent way into your vault. It's shown only once, so store it somewhere safe. Without your master password and recovery key, not even Geslar can open your data.
CSPRNG — secure randomness
All random values in Geslar (keys, salts, IVs, generated passwords) come from a CSPRNG (cryptographically secure pseudo-random number generator) provided by the browser and operating system. The numbers are cryptographically secure — unpredictable, with no pattern an attacker could exploit.
How does Geslar compare?
Geslar
Argon2id (memory-hard KDF), AES-256-GCM and encryption on your device.
Older key derivation methods
Functions such as PBKDF2 mostly use processor time and little memory, so they are easier to speed up on GPUs.
Vendor lock-in?
If you use the extension, an encrypted copy of your vault is on your device. Also make a backup and export your data (e.g. to CSV) to import into another password manager. CSV is not encrypted, so keep it safe.