what void processes, and what isn't here.
what isn't here
no accounts, no email, no passwords. no message or call history. no tracking cookies, no analytics, no advertising partners. void doesn't sell data and doesn't share it with third parties — there's nothing to share.
what is processed
the server sees your IP address — technically required to set up the connection and to defend against abuse (rate limits, protection against guessing room codes). the IP is kept only in the server's memory — for an hour at most, never written to disk, never shared. in the logs it's replaced with an anonymous tag that changes every day; room codes and participant ids appear there only as tags too.
while you're in a room, the server holds your nickname in memory — to show it to the others. leave, and it's forgotten.
what stays in your browser
localStorage keeps your settings: language, nickname, microphone and speaker choice, volume levels. they exist only so your browser can remember your choices between sessions; of these, only the nickname reaches the server — and only for the duration of a call. no traces of your calls are left in the browser. clear the settings by clearing site data.
how the conversation travels
voice, chat, and files travel directly between participants over WebRTC. the server only helps you find each other at the start (this is called signalling) — after that, it's not in the path. all content is encrypted with DTLS-SRTP; the server does not hold any keys.
you can check that nobody sits in the middle — not even the server — with the security code: five symbols in the room. if everyone sees the same ones, the call is yours alone. compare them out loud, not in the chat.
to find a direct path, the browser asks public STUN servers (google, cloudflare) for its outside address — that's how WebRTC works. they see only the IP; the call never goes through them.
when relay kicks in
sometimes a direct connection between participants isn't possible — usually because of corporate networks or mobile carriers with CG-NAT. that happens to roughly one pair in three: then encrypted packets pass through our relay server (TURN). the relay sees only connection metadata: both sides' IP addresses and the session duration — under a one-time id, without your nickname or the room code. only room participants can use the relay. the content stays encrypted — the relay cannot decrypt voice or messages, the keys live only with you and the other person.
if you send a bug report
a report leaves only when you press "send" in the settings yourself — it goes to the developer's mailbox. it contains your description, a contact (if you gave one), the version, your browser and the app's technical log. the room code and participant ids are replaced with anonymous tags, the IP with the daily tag.
contact
privacy questions — on telegram: @casheaterr