Privacy

No tracking

This site sets no cookies, loads no analytics, and stores nothing about your visit. There is no account system, no newsletter, and no third-party script. Nothing you read here is recorded.

Peer-to-peer traffic stays peer-to-peer

Demos and games open WebRTC data channels and media tracks. Once two browsers connect, that traffic goes straight from one to the other, encrypted in transit by DTLS, which WebRTC makes mandatory. No server reads it, because there is no server beyond the static files that load the page. This site never uses a TURN relay, so nothing in the data path is routed through a third party.

Who sees your IP address

Opening a direct connection means revealing network addresses. Three parties can see yours.

The host. Loading any page reveals your IP address and user agent to whoever serves the files, under their own logging policy.

Public STUN servers. To find a route between two networks, your browser asks a public STUN server to reflect your public address back to you. This site uses stun.l.google.com:19302 and stun.cloudflare.com:3478. Google and Cloudflare see your IP address at that moment, under their own policies.

The other peer. A direct connection means the browser on the other side learns your public IP address, and yours learns theirs. This is inherent to peer-to-peer, not a choice this site makes. If keeping your IP address private matters to you, connect only with people you trust.

Signaling through ntfy.sh

Connecting by shared link publishes your session description to a topic on the public ntfy.sh network. That description lists your local and public IP candidates and your browser media capabilities. Topics on ntfy.sh are public: anyone who knows or guesses the topic name can read the message while it lives, and it is discarded shortly after the connection opens.

The two other connection modes never contact ntfy.sh. Manual mode has you copy the code and pass it along yourself. URL mode packs it into the link fragment, which browsers never send to a server.

What never leaves your browser

Moves, drawings, chat, camera and microphone data, and any file you send in a demo travel over the encrypted channel directly to the other peer. None of it reaches this site, and none of it is stored anywhere.