GAMENEST

Privacy

Updated . This notice covers gamenest.info, the GameNest app, and the GameNest relay.

Visiting the site

The site has no accounts, analytics scripts, or forms that send information to GameNest. GameNest does not set tracking cookies on this site.

GitHub Pages hosts the site. GitHub says it logs and stores visitor IP addresses for security. See the GitHub Pages data collection notice and GitHub Privacy Statement.

The GameNest app

The app has no accounts and no sign-in. When you host or join a lobby, it shares a few details with the people in that lobby.

Your display name is shown to everyone in the lobby you host or join. The host also receives two more things. One is your profile ID, a random identifier that the app creates the first time it runs, keeps on your device, and sends when you join, so the host can recognise your installation. The other is the list of game IDs installed on your device, so the host can tell you when a realtime 3D game needs installing. Board games run on the host, so that list does not decide what you can play.

The app saves what it needs on your device. On desktop, a settings file in the GameNest folder holds your display name, profile ID, port, capacity, and interface choices, and completed chess games are saved in a games data folder there as standard PGN files, which include the player names. Those stay until you delete them. macOS uses Application Support instead, and Android uses the app's own storage; Android also ships its games inside the app, so it downloads no packs.

Other files are temporary. A realtime 3D match writes a small launch file holding its join code, and the app removes it when the match ends. Cached art and other game assets are kept in a cache that drops the oldest files once it passes its size limit.

Not every build checks for updates, and the check can be turned off. When it runs, the app asks GitHub for the release list once at startup, and again when you download a game pack or an app update you asked for. GitHub receives those requests, including your IP address.

Join codes and the relay

Hosting with a join code, or joining with one, sends the connection through the GameNest relay. The relay receives the IP address of each connection and the six-character join code, and passes lobby and board-game traffic between host and guests without encryption. The app adds no encryption to that traffic, so the relay is in a position to read it. On that connection, guests do not learn the host's address and the host does not learn theirs.

The relay records operational events. A room opening or closing is recorded with that room's join code, and a client blocked after repeated failed joins is recorded with its IP address. Those records go to the server's system journal, which is kept on disk across restarts, has no configured age-based expiry and is subject to storage limits. A separate copy is written to the server's syslog file, which is configured to rotate weekly and keep four rotated files.

Realtime 3D matches work differently. A relay join code gets you into the lobby, but the match needs a direct, encrypted connection to the host, so the relay does not carry the gameplay. To start one, the host's app sends each seated guest the host's direct connection address, usually a LAN or Tailscale address, inside the match join code. A guest receives that address even when it reached the lobby through the relay, and if the address is not reachable from where the guest is, the match cannot connect.

Downloads and Discord

Download links open GitHub Releases. Community links open Discord. Their privacy policies apply when you use those services. See the Discord Privacy Policy.

Questions

For privacy questions, email contact@gamenest.info. For gameplay help, use the GameNest Discord. Keep personal information out of public channels.

Back to home