Launching Privacy Bar: browser extension with NIST post-quantum encryption (ML-KEM) and zero servers
Hey Product Hunt community! đź‘‹
I'm putting the finishing touches on Privacy Bar, a client-side Chromium extension built on a strict "Servers are Evil" philosophy.
The core idea: Every security operation—from password generation to file encryption—should happen entirely in local browser memory with zero cloud backends, zero remote vaults, and zero tracking calls.
What we're bringing to the launch:
Vault-less Password Engine: Synthesizes deterministic credentials on the fly from a Master Key (no database to breach or sync).
Post-Quantum Key Encapsulation: Implements NIST-standardized ML-KEM (FIPS 203) directly in browser memory.
Client-Side Steganography & Encryption: Local text/file encryption and image payload weaving.
Zero-Knowledge Memory Guards: Volatile memory handling with automatic 5-minute auto-wipe guards.
We're scheduling our full launch soon, but I wanted to ask the PH tech community:
When evaluating privacy or security extensions, what is your biggest dealbreaker?
Would love to hear your thoughts, answer technical questions, and get your feedback!
Replies