Private one-on-one support chat that leaves no history

Someone reaching out for help may be on a shared phone, a family computer, or a device their partner checks. The safest conversation is one that never existed on the device at all. Btwinus is an encrypted, browser-only chat with no account, no server, and nothing left in the history when the tab closes.

The problem

Peer supporters, helpline volunteers, counsellors doing a first intake, and mentors in sensitive programmes all face the same tension. The person they are helping needs to be able to talk without creating evidence that they talked. A message thread titled "Domestic abuse helpline" on a phone that someone else unlocks is not a neutral artifact. Neither is an app icon, a login email, or a browser history entry.

At the same time, the supporter does not want to run infrastructure, keep transcripts they are then responsible for, or ask a person in distress to install anything.

Why ordinary tools leak

How Btwinus fits

Btwinus is one web page that runs in any modern browser, on any phone or computer, with no account and nothing to install. Starting a chat produces an encrypted invite link and a passphrase. The link carries a WebRTC handshake encrypted with AES-256-GCM, the key derived from the passphrase via PBKDF2 with 100,000 iterations, in the URL fragment, which browsers never send to a server. When both sides connect, messages travel directly between the two browsers. There is no server, no transcript, and no message history. When the tab closes, the conversation is gone from both devices.

For the person seeking support this means: open a link, type a few words, talk, close the tab. A private browsing window removes even the browser history entry. Nothing to uninstall, nothing to delete, no notification later.

Step by step for a support volunteer or counsellor

  1. Agree a time through whatever contact you already have. Btwinus is a live channel, so it works like an appointment. Even a short reply, "I'll be there at 8", is enough.
  2. Start the chat and send the link. Open btwinus.com, click Start a new chat, and send the invite link through the channel the person first used to reach you. On its own it reveals nothing about the conversation.
  3. Send the passphrase separately. If they reached you by email, send the passphrase by SMS, or read it out on a brief call. If you are agreeing a recurring window, you can agree the passphrase once in person.
  4. Receive the reply link. They open the link, enter the passphrase, and get a reply link copied to their clipboard. They send it back to you. Guide them through this gently; it is the only fiddly step.
  5. Connect and check. Paste the reply link. Both screens show a short authentication string. If you have a voice channel, compare it; matching codes mean no one intercepted the setup.
  6. Talk, then close. When you finish, both of you close the tab. Suggest they use a private browsing window if the device is shared. If your role requires case notes, write them in your own secure system afterwards, from memory.

For walk-in settings, a QR code of the invite link on a printed card or a screen, with the passphrase given by the receptionist, lets a person connect from their own phone without saying anything out loud.

Honest limitations

Btwinus is free and open source. An organisation can review the code before recommending it to the people it serves.

Give someone a way to talk that leaves nothing on their device. No account, no app, no history.

Start a private chat →

← All use cases