About Me
Building privacy-first encryption tools backed by strong cryptography, transparency, and real-world security expertise.
Who I Am
I'm a cryptographer and security protocol researcher with more than a decade of experience designing, analyzing, and breaking real-world security systems. My work spans key exchange protocols (TLS, PAKEs), secure messaging, encryption technologies, and trusted execution environments.
I created encrypt.lu and decrypt.lu to offer client-side encryption that respects users. No tracking. No access to your keys or plaintext. Just transparent, verifiable security — you encrypt on your device, and only you (or your recipient) can decrypt.
Outside academia and engineering, I'm a father of two and a strong believer in individual privacy, digital rights, and ethical technology. My wife — an architect with an eye for design — helps keep everything you see here clean, beautiful, and human.
If this project has been useful to you, feel free to support it. Every coffee helps me continue building independent, privacy-respecting tools.
Other Projects
I also maintain several other privacy-first tools and services:
Frequently Asked Questions
Is my data stored or visible to you?
No. Encryption and decryption happen entirely in your browser. We never see your password, your key, or the contents of your files. When you use the share feature, only encrypted ciphertext is stored; we cannot decrypt it.
Can I use this for large files?
Yes. Encryption and decryption run in a web worker so the UI stays responsive. Very large files (e.g. multi-GB) may hit browser memory limits; we show a warning and let you proceed at your own risk.
Why client-side only?
So that we never have access to your keys or plaintext. You stay in control; the server only handles encrypted blobs for the optional share feature.