Your Message.
Your Lock.

Yes. The encrypted payload is a self-contained string. Anyone running CipherBrick - on any device, any supported browser - can decrypt it with the correct key and salt. No accounts, no sync, no server handshake.

No. The default mode works like any encryption tool: set a key, encrypt, share. There's also a simplified mode that handles the technical details automatically, so you only need to share a single password. Advanced options like hardware key support are there if you need them, but never required.

Any method you're comfortable with works. The simplest option for most people is verbally - a phone call or in person. Nothing written, nothing transmitted. You can also send the key through a separate channel from the encrypted message - even if someone sees the message, it's useless without the key.

If you want a more formal approach, CipherBrick includes a built-in Key Exchange Wizard. It lets both parties arrive at a shared key without ever transmitting it - each person shares only a public key, which is safe to send openly.

There is no recovery. CipherBrick has no servers, no accounts, and no recovery option - your data stays entirely in your control.

Think of it like a combination you set on a safe yourself. Nobody else ever knew it, so nobody can give it back. Whatever you used to encrypt - a password, a password pair, or a physical security key - keep it somewhere safe. If it's gone, the encrypted content is gone with it.

CipherBrick provides strong AES-256-GCM encryption as an additional layer on top of whatever channel you use. It does not replace a comprehensive compliance program, and we make no specific HIPAA/GDPR compliance claims. Consult your legal and compliance team for your specific regulatory requirements.