How Anonymous Voice Chat Works

This page explains, in plain language, how the technology behind StrangerCall creates real-time anonymous voice connections and what that means for privacy and safety.

Peer-to-peer connections

When network conditions allow, audio is exchanged directly between two browsers (peer-to-peer). This means media does not pass through our servers, reducing latency and limiting what we can see or store.

WebRTC — the browser standard

We use WebRTC, the browser API built for real-time audio and video. WebRTC handles device access, encryption, and network traversal. It uses signaling (via our Socket.IO server) to coordinate connection setup but the media path is handled by the browser and network.

STUN and TURN — why they matter

To establish direct connections across home routers and mobile networks, WebRTC uses STUN and TURN servers:

No profiles & temporary sessions

StrangerCall does not create persistent profiles. Sessions are ephemeral: after a call ends the temporary session data is discarded. We retain minimal metadata (selection filters, timestamps, anonymized logs) solely for moderation and service reliability.

Privacy and security

WebRTC encrypts media streams end-to-end between peers using SRTP. While TURN relays media when needed, traffic remains encrypted in transit. Our privacy policy explains what metadata we keep and how we use it; review it here.

Common troubleshooting

Benefits of voice-only anonymous chats

FAQ

Can strangers hear me without my permission?

No — the browser asks for microphone permission and you control it. If you deny permission the site cannot access your microphone.

Is the audio encrypted?

Yes — WebRTC encrypts media streams between peers. Even when relayed via TURN, the data is encrypted in transit.

Learn more

Is StrangerCall Safe? →

Back to homepage