Privacy

GliderMCP products run locally. Your code, prompts, project files, and local runtime evidence are not sent to GliderMCP servers.

The MCP server you configure analyzes files or artifacts in your workspace and returns results to your MCP client.

Data stays local

GliderMCP product tooling runs on your machine. Requests are handled locally, and project files remain in your workspace.

• Source code: not sent to GliderMCP servers.
• Prompts: not sent to GliderMCP servers.
• Diagnostics and runtime evidence: not sent to GliderMCP servers.
• Website analytics: collected in aggregate through Google Analytics.
• Local logs: not retained by GliderMCP servers.

Limited website analytics

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.

You control retention

GliderMCP does not retain customer data on GliderMCP servers. Any files, logs, artifacts, or MCP client transcripts live in your local environment or in the client you choose.