Technical details

The Zap Screen communicates with every connected Zap Remote by sending messages via WebSockets through a central server hosted by us. The server acts only as a broadcaster and stores none of the posted content.

When the Zap Screen is opened, a random session ID is generated and included in the link used by players to connect to the session with the Zap Remote. No verification is made that the session ID isn’t already in use, so it is possible, though unlikely, that a session ID will be generated that is already in use by other players. There is also no authentication required to join a session, so anybody who knows a session ID is able to join that session. While we store none of the posted content, we make no guarantees about which other players might be connected to the same session, either through random chance or intentionally.

If you want privacy guarantees or for other reasons want to be in full control of your Zap Screen, consider using the source code available on GitHub to host your own version.