Share your thoughts securely with the world. Create end-to-end encrypted notes that self-destruct immediately after reading. Zero-knowledge architecture.
No reviews yetBe the first to leave a review for LockNotes
Maker
📌
Hey Product Hunt! 👋
I’m thrilled to introduce LockNotes, the latest release out of Webrizen.
We wanted to build a one-time secret app that didn't just function as a basic utility, but actually pushed the boundaries of both web cryptography and frontend design.
The Architecture (Zero-Knowledge):
Most anonymous messaging apps require you to trust the server. We removed trust from the equation. When you type a note, it is encrypted locally in your browser using AES-GCM 256-bit encryption. The decryption key is attached to your shareable URL as a hash fragment (#key). Because browsers never send hash fragments to the server, it is mathematically impossible for us to read your payload. When the recipient opens the link, an atomic PostgreSQL transaction instantly nukes the row before decrypting it locally.
The Design Language:
We wanted the user experience to be unforgettable. The creation page features a custom WebGL fragment shader animated with GSAP, designed to evoke the lush, ethereal skies and volumetric lighting of modern Japanese animation films. However, the moment the recipient opens the link to read the secret, the UI instantly snaps into a strict, high-contrast, DX-inspired technical grid to reflect the secure, raw nature of the decrypted payload.
Stack: Next.js, Supabase (with custom RPCs), GSAP/Framer Motion, and Transformers.js (for on-device AI toxicity filtering to prevent abuse).
I would love to hear your thoughts on the zero-knowledge implementation, the UI transitions, or the tech stack. I’ll be hanging out in the comments all day to answer your questions!
Report
would be cool if you could set a custom expiry time instead of it always being immediate, like give the recipient 5 minutes or an hour to re-read it if needed.
Sometimes an immediate nuke is too fast if the recipient accidentally switches tabs or needs to re-read a long string of data.
We love this idea and we are mapping out a feature where the sender can toggle between "Immediate Self-Destruct" and "Timed Self-Destruct (5m / 1h after open)".
Thanks for taking the time to share this... It's officially going into development!
Report
Sent a note to myself and it really did vanish after one read, which is kind of eerie but cool. The interface is clean and the zero-knowledge setup gave me peace of mind.
would be cool if you could set a custom expiry time instead of it always being immediate, like give the recipient 5 minutes or an hour to re-read it if needed.
@baran583733 Thanks for the feedback, Baran!
Sometimes an immediate nuke is too fast if the recipient accidentally switches tabs or needs to re-read a long string of data.
We love this idea and we are mapping out a feature where the sender can toggle between "Immediate Self-Destruct" and "Timed Self-Destruct (5m / 1h after open)".
Thanks for taking the time to share this... It's officially going into development!
Sent a note to myself and it really did vanish after one read, which is kind of eerie but cool. The interface is clean and the zero-knowledge setup gave me peace of mind.
@hakani8ik Hey Hakan! So glad you gave it a try!
That "eerie but cool" feeling is exactly what we were going for!
It's wild to think that once you hit refresh, that data is mathematically wiped out of existence across the entire database.
Hearing that the interface felt clean and the zero-knowledge architecture brought you peace of mind means the world to us.
That UX/security balance was exactly our goal. Thanks so much for the support!