3RTCPrivacy
Privacy at 3RTC
3RTC has no accounts, no ads and no analytics. Your video, voice, chat and images travel directly between the devices in your room. Here is exactly what is shared, and with whom.
What goes directly between devices
Video streams, voice, chat messages, images, reactions and playback sync are sent straight from one device to the others in your room over WebRTC, which encrypts everything in transit. None of it passes through or is stored on 3RTC’s servers.
What the connection server sees
To introduce devices to each other, 3RTC runs a small connection (signaling) server. It handles your room code, the display name you choose, a random session ID and the network details your browser needs to connect (which include IP addresses). It keeps this only while your room is open, and its logs record room codes and session IDs, not names or messages.
Other services involved
| Service | Why | What it receives |
|---|---|---|
| Google STUN servers | Helps devices find a direct route to each other | Your IP address |
| YouTube | Plays YouTube videos inside the room | What YouTube normally receives when you watch an embedded video, under Google’s privacy policy |
| noembed.com | Looks up a YouTube video’s title | The video link |
| Google Fonts | Loads the app’s fonts | Your IP address and browser details |
| Vercel | Hosts the website | Standard web request information |
The people in your room
Because devices connect directly, people in the same room can see each other’s IP addresses, as with any peer-to-peer app. Only share your room code with people you trust.
What is stored on your device
Your browser keeps your display name and settings (audio, volume, layout) in local storage so you don’t have to set them again, and the installed app caches its own files so it opens quickly. 3RTC sets no tracking cookies. Clearing your browser data removes all of this.