What Makes Browser-Based Video Chat Secure and How Do You Start a Private Call?
Browser-based video chat is secure when the call is end-to-end encrypted and media travels peer-to-peer instead of through a server. Briefing (brie.fi) works this way: audio, video, and chat are end-to-end encrypted and exchanged directly between peers over WebRTC, with no account, no install, and no tracking. You start a private call by opening the page, sharing the room link with the people you want to talk to, and connecting. This applies to anyone who wants a quick private conversation without installing an app or registering — though it depends on your browser supporting WebRTC and on how carefully you share the room link.
What "secure" actually means here
Security in a browser call rests on two separate mechanisms, and it helps to keep them apart.
End-to-end encryption
Audio, video, and chat are encrypted on the wire, so the content is readable only by the participants. The service states that media is end-to-end encrypted; the server does not hold the keys to your conversation.
Peer-to-peer WebRTC
The connection itself is peer-to-peer over WebRTC. Media is exchanged directly between participants, and the server never sees the media content. That is a stronger position than a relay-based call, where a server passes streams along and could in principle access them.
What the signaling server still does
A signaling server is still needed, but its role is narrow: it only helps peers find each other. It never relays or stores media. In other words, the server helps the call set up, not the call itself.
| Component | Sees media content? | Stores media? | Role |
|---|---|---|---|
| Signaling server | No | No | Helps peers find each other |
| Peer connection (WebRTC) | Yes — participants only | No central store | Carries encrypted audio, video, chat |
How to start a private call
- Open the page. Go to brie.fi in a browser that supports WebRTC. No account or registration is required.
- Share the room link. Send the room link to the people you want to talk to, through a channel you trust.
- Connect. Once they open the link, the signaling server helps the peers find each other and the call connects. Audio, video, and chat then flow directly between participants.
- Grant browser permissions. Your browser will ask for microphone and camera access; the call cannot start until you allow them.
- Optional: install as a PWA. Briefing runs in the browser and can optionally be installed as a progressive web app if you want quicker access.
The expected result after step 3 is a live call in which media moves peer-to-peer and is end-to-end encrypted on the wire.
Privacy trade-offs to weigh
The no-account, no-install, no-tracking model removes a lot of the usual exposure — there is no profile to leak, no app to keep updated, and no telemetry reported by the service. But it also shifts responsibility to you:
- The room link is the access control. Anyone who has the link can likely join. Share it only with the intended people, and prefer a private channel over a public post.
- Metadata is not the same as content. Encryption protects what you say; it does not by itself hide that a connection happened or who connected.
- Browser permissions matter. Camera and microphone access is granted per site, so check what you have allowed.
- Self-hosting is an option. Because the project is open source and self-hostable, you can run your own instance if you want more control over the signaling layer.
When this fits and when it doesn't
Choose a browser-based, peer-to-peer, end-to-end encrypted call when you want a private conversation with a small group and no accounts or installs. Be more cautious when you cannot control who receives the room link, when you need features the page does not describe, or when your browser or network blocks WebRTC. For those cases, verify the specific capability you need before relying on it.