Privacy policy

The short version

This site has no accounts, no signup forms, and no newsletter. We never ask for your name or email. What's left is small: standard web analytics on the website, and anonymous usage counters on the MCP server. Neither identifies you.

On the website

Analytics. We use Google Analytics 4 to see which pages get read. It sets cookies and collects the usual usage data (pages visited, browser, coarse location); Google processes it on our behalf. Retention is Google's standard 14 months. A content blocker stops it completely and the site works fine without it.

Search. When you use the search box, your query goes to our backend (Supabase) to compute a match against the tool dataset. The query is used for that response and not stored.

On the MCP server and API

The MCP server (mcp.gtmtools.dev) is keyless: no account, no token, no cookies. Per call we record the tool name, whether it succeeded, latency, the client software's self-reported name (e.g. "claude-code"), which filter keys were used, the result count, and — when a category filter matches our fixed category list — that canonical category. Never your query text, never which tool you looked up, never your IP address. We use these counters to see which capabilities get used and to catch errors, and we keep them as aggregate statistics. They contain nothing that identifies a person, so there is nothing to delete on request.

Who touches the data

Serving you requires infrastructure providers, and like any web host each one sees standard request logs (IP address, user agent) transiently: GitHub Pages hosts the website, Vercel fronts the MCP endpoint, Supabase runs the backend, and Google runs the analytics. We don't sell data to anyone, share it with anyone else, or combine it across these providers.

Questions

Email privacy@gtmtools.dev. If this policy changes, the new version appears here with a new effective date.