Glider products run locally. Your code, prompts, project files, and local runtime evidence are never sent to Glider servers.
The MCP server you configure analyzes files or artifacts in your workspace and returns results to your MCP client. The products send anonymous usage telemetry (versions, OS, tool names, error categories) so we can improve them; this is documented in full on the What we collect page and can be turned off.
Glider product tooling runs on your machine. Requests are handled locally, and project files remain in your workspace.
To learn how the products are actually used — so we can fix the right bugs and remove tools nobody uses — the MCP servers send a small amount of anonymous usage data: a random install id (no machine fingerprinting), product and version, OS and architecture, runtime version, tool names with a duration bucket and success/error outcome, error categories (exception type names only, never messages), and coarse workspace shape counts. Country is derived at our edge from the network request and the IP address is never stored.
It never includes your source code, file paths, file or symbol names, prompts, command arguments, or raw error messages.
Telemetry is on by default and easy to turn off: run the server with the --no-telemetry flag (or set DO_NOT_TRACK=1 in the environment that launches it). The full field-by-field list and opt-out details are on the What we collect page at /privacy/telemetry.
The public website uses Google Analytics to understand aggregate page usage. This analytics does not include your source code, prompts, diagnostics, project files, or local MCP traffic.
Glider does not retain customer data on Glider servers. Any files, logs, artifacts, or MCP client transcripts live in your local environment or in the client you choose.