Privacy

Bridge is designed to transfer data directly between connected devices whenever a direct WebRTC connection is possible. Files are not intentionally stored on Bridge's application server.

How a transfer works

When you open Bridge on one device, our server creates a temporary session with a random code. The second device joins by scanning the QR code or typing that code. The server then passes a small amount of connection setup information between the two browsers so they can find each other. After that, files, photos, videos, text and links travel over an encrypted browser-to-browser connection (WebRTC). The server does not receive them.

When a relay is used

For some network configurations, WebRTC may use a relay server to establish connectivity. This can happen on strict corporate, hotel or mobile networks. If a relay (a TURN server) is used, your data passes through it in encrypted form. The relay forwards traffic and is not designed to store it, but we won't pretend the data never leaves your devices in that case. Bridge tells you when a connection goes through a relay.

What the server sees

• The temporary session code, when it was created and whether a second device has joined.
• Connection setup messages, which include network addresses your browser offers for the connection. These are relayed and not stored.
• Standard technical request data such as IP address, used in memory for rate limiting to prevent abuse.

The server never receives the contents of your files, text or links, and it does not log file names.

What we keep

Nothing permanent. Sessions live in memory only. They expire automatically after 10 minutes without activity, and end immediately when either device ends the session. There are no accounts, no file history and no cloud storage. Received files exist only in the receiving browser's memory until you download them or close the tab.

Remembered devices

If you choose "Remember this device", your two devices exchange a random secret over their encrypted connection and each keeps it in its own browser storage. Our server never receives the secret. While Bridge is open, it only sees an unreadable code derived from it, which lets it tell the other device that you'd like to connect. You can forget a device at any time from My devices; clearing your browser's site data forgets them too.

Tools that use our server

Most Bridge tools work entirely in your browser. A few conversions can't be done well there: PDF to and from Word, Excel and PowerPoint, HTML to PDF, and background removal. For these, your file is sent over an encrypted connection to our conversion service, converted, returned to you, and deleted right away. We don't keep copies, don't look at the contents, and don't log file names. Each of these tool pages says so clearly.

Analytics

This version of Bridge does not include analytics or tracking scripts, and it loads no third-party fonts or scripts. If anonymous usage counts are added in the future, they will never include file contents, file names, text, links or personal information.

Encryption

WebRTC connections are always encrypted (DTLS). In production, Bridge is served over HTTPS and its connection setup channel uses secure WebSockets.