22 November 2026 · Udaysinh
Tightlip: sending a password without leaving it in the chat
A link that carries a password, a note or a photo, encrypted in your browser and gone after it is read.
Most passwords at a small business travel the same way. Someone types the Wi-Fi password, the Gmail login or the hosting account into WhatsApp, and there it stays, in the chat history of every phone in the group, for years.
Tightlip is the tool we built so that stops happening. You paste a password, a login, a note or a photo, choose how many times it can be opened and when it expires, and get a link. Send the link. When the views run out or the time is up, the link stops working.
The encryption happens in the sender's browser before anything is uploaded. The key is in the part of the link after the # sign, which browsers do not send to the server, so what we store is ciphertext we cannot read. The recipient's browser decrypts it when they press Reveal. You can add a password on top and send it some other way, so someone who finds the link alone still gets nothing.
No account is needed to send or open a link. Opening the page, or a chat app building a preview of it, does not spend a view. That was the first thing to go wrong in every similar tool we tried.
The server is written in Rust and the encryption runs in the browser as WebAssembly. The threat model, including what a compromised server could still do, is written out in plain words on the security page. We would rather you read the limits than take our word for it.
We use it ourselves to hand logins to clients when a website goes live. If your team in Pune or anywhere else still shares passwords over chat, try it on the next one. It is listed with our other products in the Lab.