🛡 Encryption standard
Until now, this level of encryption required apps, accounts, and trust in a company. Signal needs your phone number. PGP needs software. Enterprise tools need registration. Btwinus puts AES-256 end-to-end encryption directly in a shareable link. Anyone can use it, nothing is stored, and no one is in between.
Live demo
Alice and Gradi K. starting a private chat, no accounts, no setup
Click "Start a new chat". You instantly get two things: an encrypted invite link and a passphrase.
Send the link via WhatsApp, email, or any app. Send the passphrase a different way: a phone call, SMS, or say it in person. Keeping them apart means nobody can intercept both.
The other person opens your link, types the passphrase, and gets a reply link that is automatically copied. They send it back to you.
Paste their reply link and you're instantly connected. Everything is end-to-end encrypted. No accounts, no servers, no history. Gone when you close the tab.
Receive anonymous tips and communicate with whistleblowers without leaving a server trail. Nothing is stored, not even metadata.
Learn more →Privileged conversations that disappear on close. No law firm server, no cloud provider, just a direct encrypted connection.
Learn more →Discuss sensitive terms anonymously (salary, deals, disputes) with no transcript and no identity required.
Learn more →Employees, students, or customers send honest feedback without worrying about identity. No account means no trace.
Learn more →Share a password, API key, or crypto seed phrase once, directly browser-to-browser. Far safer than email, Slack, or WhatsApp.
Learn more →Crisis lines, peer support, therapy pre-sessions. Temporary secure chat that leaves no history behind.
Learn more →Yes. There is no subscription, no ads, and no premium tier. Everything runs in your browser, so there is nothing to pay for.
No. Open the link in any modern browser. No email, no phone number, no sign-up of any kind.
Nowhere. Messages travel directly between the two browsers over an encrypted WebRTC connection. When either person closes the tab, the conversation is gone.
The link is encrypted with the passphrase. If both travel through the same channel, whoever can read that channel has both. Sending the passphrase by phone, SMS, or in person means an attacker would have to compromise two channels instead of one.
Those need an app, a phone number, and a company’s servers to route messages. Btwinus needs none of that. It is built for one-off private conversations, not as a replacement for your everyday messenger.
Yes, in Chrome, Safari, Firefox, and Edge on iOS and Android. The invite link can be shown as a QR code so the other person only has to scan it.
No Btwinus server, and no relay. The handshake travels inside the link, and messages go straight between the two browsers. The one outside party is a STUN server (currently Google’s), which each browser asks for its own public address. It sees your IP, never any content. There is no fallback relay, so on some strict corporate or mobile networks a direct connection cannot be made and the chat will not connect.