Privacy and telemetry
What the MCP server and the feeds keep
The MCP server keeps nothing you ask it
The DNS, SPF and propagation tools query public resolvers live and return the answer. The domain you looked up is not written down, and neither is any other argument you pass: not the provider you asked about, not the stack you were planning.
Three things are counted, so that whether the server is used at all stops being a guess:
- how many times a client completes a handshake, with the product name it declares for itself;
- how many times each tool is called, by tool name;
- the client's User-Agent, which names the software making the call.
No IP address, no other header, no argument value, and nothing that identifies a person. None of it counts installs, and no arrangement of it could: the MCP server holds no session and issues no key, so a client reconnecting after a restart is indistinguishable from one arriving for the first time. Read the numbers as activity.
The one exception
send_feedback stores a report an assistant chooses to send: what it wrote, the time and the client's User-Agent, never the IP address. Closed reports are deleted 90 days after they are closed, and any report a year after it arrives. The IP address is used only as a rate-limit key and is never written.
The REST API and its keys
The REST API uses a free key you create yourself. There is no email, no name and no sign-up form. inetGeek keeps a SHA-256 hash of the key (it is shown once and cannot be recovered), a ten-character prefix, an optional label you typed, the creation date, and the date it was last used, updated at most once a day. It does not keep your IP address, your requests or what you asked for. The IP address is a rate-limit counter key, as above, and is not written.
A revoked key is deleted 30 days later; a key unused for a year is deleted. A label is stored as typed, so do not put personal data in it.
The HTTP feeds
The static feeds are served from the edge cache. The three live DNS endpoints are rate-limited per IP address using a counter; the address is not stored.
This docs site
These pages are static files. The search index is built into the site and runs in your browser; searching sends nothing anywhere. See the site privacy policy for what the rest of inetgeek.com does, including analytics, which load only after consent.