Privacy

Tide Engine keeps as little as it can about the people who use it. This page covers this website, the tide command and the relay that introduces players to each other. Games you make with Tide are yours: the engine adds no analytics or tracking to them.

This website

The site counts page views and package downloads, as daily totals, with no cookies for visitors, no visitor IDs and no third-party analytics:

Daily totals are kept for 400 days. Your IP address is used only to limit how many requests one address can make, held in memory for minutes and never stored. Requests sent through the early-access form keep the GitHub username and the description you enter, privately, to review them.

The tide command

tide sends one small anonymous event per command: which command, its target, the version, the operating system and CPU, whether CI runs it, how long it took, whether it worked and if not the kind of failure, and how many files and packages the game has, in ranges. Events carry a random ID for the installation. They never hold paths, project or file names, code, error messages, or user or machine names. They're kept on this site's server for 13 months, with the time they arrived rounded to the hour.

Turn it off with tide telemetry off, TIDE_TELEMETRY=0 or DO_NOT_TRACK=1. Usage data lists every field.

The multiplayer relay

When players host or join a room, the relay introduces them so their games can connect to each other. It sees each player's IP address to do that, and counts connections per address to limit abuse. It keeps addresses in memory only while they're connected, or for about a minute after their last request, and doesn't write them to disk or to its logs. Rooms and lobbies live in its memory while they're open; it keeps no lasting record of them or of who played with whom.

Once introduced, players' games connect directly, so the players in a match can see each other's addresses, as in most online games. Where a direct connection isn't possible, their traffic goes through a relay server (TURN) run by Cloudflare.

Who runs it

The website and the relay run on Fly.io, and the domain's DNS and the TURN servers on Cloudflare. They handle network traffic under their own privacy policies.