Privacy Policy

Last updated: October 13, 2026

Chess Voice lets two people talk by voice while playing on chess.com or lichess.org. It has no servers of its own, no accounts, no analytics and no tracking. This page explains exactly what it touches and where that data goes.

What the extension accesses

Where your data goes

DataSent toWhy
Your voiceThe other person in your room, encrypted (WebRTC DTLS-SRTP). Usually directly; if your networks block a direct link, it passes through a PeerJS relay server (eu-0.turn.peerjs.com / us-0.turn.peerjs.com), which forwards the encrypted audio but can't decrypt itThat's the voice chat
Your username and whether you're mutedDirectly to the other person in your roomShown on their widget
A scrambled room ID (a hash of the game ID or room name) and your IP addressThe public PeerJS server at 0.peerjs.com, run by the open-source PeerJS projectTo introduce the two browsers so they can connect
Your IP addressA Google STUN server (stun.l.google.com) and, when needed, the PeerJS relay serversSo your browser can learn its public network address and connect through restrictive networks

Your voice is never sent to the developer, and the PeerJS servers can't listen to it. The extension doesn't record or store audio.

What's stored on your device

The widget's position and whether it's collapsed are saved in your browser's extension storage. While you're granting microphone permission, the room you were joining is briefly kept in session storage. None of this leaves your device.

What the developer collects

Nothing. The developer receives no data from the extension, and doesn't sell, share or use data for advertising, credit or any purpose other than the voice chat itself.

Your choices

You can mute, deafen or leave at any time. You can revoke microphone access in Chrome's site settings for the extension, and you can remove the extension to delete everything it stored.

Contact

Questions or problems: siphyshu@gmail.com