Skip to content
  • P2P
  • E2EE
  • No accounts
  • Nothing stored
  • Free

P2PE2EENo accounts

No ID. No Trace. Just
Connection.

Private chat, file transfer and voice & video calls that run directly between two browsers. End-to-end encrypted. Nothing to install, nothing stored, no account.

  • Free
  • Desktop & mobile
  • Ends when you close the tab

Session spec // v2

Ready
AccountsNone
EncryptionAES-256-GCM
Key exchangeECDH P-256, per session
TransportWebRTC, peer-to-peer
Message storageNone — memory only
File transfersUp to 500 MB
CallsVoice & video
PriceFree
  • No accounts
  • No phone number
  • No message storage
  • End-to-end encrypted
  • Peer-to-peer
  • Files up to 500 MB
  • Voice & video
  • Free

01How it works

Three steps. Zero sign-ups.

No account to create, no app to install, no phone number to hand over. Start a session, share it with one person, and talk.

  1. Step 1: Create

    Generate a private link or a 6-digit code. Your browser creates fresh encryption keys for this session only.

  2. Step 2: Share

    Send the link through any channel you trust, or read the code out loud. NulBridge never sees the secret part of the link.

  3. Step 3: Connect

    Their browser connects to yours, peer to peer. Compare the safety code, then chat, send files or start a call.

Read the full walkthrough

02What travels where

Straight from your browser to theirs.

A signaling server introduces the two browsers. After that, messages, files and calls travel between them, encrypted before they leave your device.

SIGNALINGCONNECTION SETUP ONLYENCRYPTED P2PMESSAGESFILES · CALLSYOUR BROWSERTHEIR BROWSERMESSAGE STORAGEDOES NOT EXIST
Fig. 02Your conversation travels between the two browsers, encrypted end to end. The signaling server only helps them find each other, and there is no message storage at all.
Encrypted P2P link
Messages, files and calls. Encrypted in your browser with keys that never leave it.
Signaling server
Sets up the connection. Sees IP addresses and peer IDs, never message content or keys.
Message storage
Doesn’t exist. Nothing is written to a server or a database, so nothing is left to leak later.
Network addresses
As with any WebRTC app, each side sees the other’s IP address, and so do the signaling and STUN servers. A relay, if needed, only forwards encrypted traffic.

03Features

Everything one private conversation needs.

The tools you expect from a messenger, built for two people and one session. Minus the account.

  • Encrypted chat

    Every message is encrypted in your browser before it is sent. Typing indicators and delivery receipts included.

  • File transfer

    Send files up to 500 MB in encrypted chunks, straight to the other browser. Images get an inline preview.

  • Voice & video calls

    Start a call from the chat. Audio and video go between your devices, encrypted by WebRTC.

  • Safety codes

    Both screens show the same short code. If the codes match, nobody is sitting in the middle.

  • Ephemeral by design

    No history and no backups. Close the tab and the conversation is gone, for both of you.

  • No install

    Runs in current desktop and mobile browsers. No app, no account, no phone number.

04Compared

NulBridge vs. a typical messenger

Different tools for different jobs. Your everyday messenger keeps your history and delivers messages while you’re offline. NulBridge deliberately doesn’t.

Built for one thing: a private, temporary conversation.
FeatureNulBridgeTypical messenger
Account or phone numberNoYes
Messages stored on serversNeverOften
App installNoUsually
End-to-end encrypted by defaultYesVaries
Works when the other person is offlineNoYes
Group chatsNo — one-to-oneYes
Message historyNone, by designYes

“Typical messenger” describes popular chat apps in general, not any specific product.

05Use cases

For conversations that shouldn’t stick around.

Open a bridge, say what you need to say, close the tab. Nothing lingers in an inbox, a chat history or a cloud folder.

  • Case 01

    Share a password or API key once

    Paste it, let them copy it, end the session. It never sits in an inbox or a chat log.

    • Chat
  • Case 02

    Send a sensitive document

    Contracts, scans, medical records: sent in encrypted chunks straight to the other browser.

    • Files
    • Up to 500 MB
  • Case 03

    Call without swapping numbers

    Voice or video with someone you would rather not give your phone number to.

    • Voice
    • Video
  • Case 04

    Talk to a client or a source

    A private line for one conversation, with no account on either side. Compare the safety code before anything sensitive.

    • Chat
    • Safety code
  • Case 05

    Move files between your own devices

    Laptop to phone without uploading to a cloud drive or emailing yourself.

    • Files
  • Case 06

    Support sessions without accounts

    Help someone by chat or on a call without asking them to sign up for anything.

    • Chat
    • Calls

06Security

Security you can verify.

Well-studied, standard cryptography from your browser’s built-in Web Crypto API, and a safety code that lets you check the result yourself.

  • Key exchange

    ECDH P-256

    Fresh keys every session

    Both browsers create new key pairs for each session and discard them when it ends, so recorded traffic can’t be decrypted later. That’s forward secrecy.

  • Encryption

    AES-256-GCM

    Every message, every chunk

    Each message and file chunk is encrypted and authenticated before it leaves your device, on top of the DTLS encryption WebRTC already applies.

  • Link secret

    256-bit

    The key stays in the link

    Browsers never send the part of a link after the # to a server. NulBridge mixes it into the session keys, then removes it from the address bar.

  • Verification

    4F2A-9C1B-77DE

    Interception shows up

    Both screens show a safety code like this one. Compare it out loud or in person: if the codes match, nobody is in the middle.

What it can’t do

Hide your IP address from the person you connect to, or protect a compromised device.

Read the security model

Not yet independently audited

07FAQ

Questions, answered.

The short version. The full FAQ covers files, calls, mobile browsers and what to do when a connection won’t go through.

01

What is NulBridge?

NulBridge is a free web app for private one-to-one conversations. You open a private link or enter a 6-digit code, and two browsers connect directly to each other over WebRTC. You can chat, send files and make voice or video calls with end-to-end encryption, without an account and without installing anything.

02

Do I need an account or an app?

No. NulBridge runs in current versions of Chrome, Edge, Firefox and Safari on desktop and mobile. There is nothing to sign up for and nothing to download, and nobody asks for your name, email address or phone number.

03

Are my messages or files stored anywhere?

No. Messages and files exist only in the memory of the two browser tabs. Nothing is written to a server or a database, and when either tab closes the conversation is gone for good. There is no history and no recovery.

04

How are messages encrypted?

Each session creates fresh ECDH P-256 key pairs in both browsers. The shared secret is combined with the secret from your private link, or with your 6-digit code, through HKDF-SHA-256, and every message and file chunk is then encrypted with AES-256-GCM before it leaves your device. This runs on top of the DTLS encryption that WebRTC already applies to the connection.

Ready when you are

Open a bridge.

Free. No account. Nothing stored.