Your entries, inside the picture
Passwords, notes and 2FA secrets are sealed twice before they ever reach the image: AES-256-GCM and XChaCha20-Poly1305 stacked, with independent keys. Breaking one seal still leaves the other.
How they get into the picture
The data goes into the pixels themselves, a tiny fraction per pixel — far too little for an eye to catch. The method is called F5 matrix encoding. Its trick: it spreads the data so that out of seven positions it could use, at most one has to be changed. And the less that changes, the less the image differs from an untouched photo — including for the tools built to look for exactly that.
Which positions are used is decided by a random key that your device's security chip keeps sealed. Without that key nobody knows where to look. And there is no obvious BlindLock marker in the file.
The key is assembled, never stored
The key to your vault is stored nowhere — not with you, not on the BlindLock server. It is assembled fresh every time you open, from the key part of your security chip and a release from the licence server, bound to exactly this image. The release is a random number that means nothing on its own. Your machine fetches it fresh from the BlindLock server every time you open. BlindLock also asks for your PIN and your master password.
If the security chip or the release is missing, no key comes about at all. The vault stays closed.
Only technical data is exchanged: licence, device, platform and version details, and the server returns a 32-byte value that goes into your vault key. What your vault holds, the BlindLock server never learns — that never leaves your computer.
And if the BlindLock server is unreachable, that does not lock you out. At your last unlock it gave your device a signed pass, kept sealed by the security chip and good for seven days. For that long BlindLock opens without internet too.
Larger files sit somewhere else
Files live in separate encrypted containers with ChaCha20-Poly1305, hardware-sealed to your computer's security chip. Argon2id derives the key itself from the vault password, with at least 512 MiB. You set how large a container is when you create it.