Privacy: distil.

distil collects nothing

The distil MCP server runs entirely on your own machine and makes no network requests. There is no telemetry, no analytics, no account and no identifier. Conversation content passed to it is processed in memory and returned to the client that asked; it is not stored and not transmitted.

What it processes

distil optimises the context of an agent session: it measures where tokens go, masks results, budgets and compacts. That means the conversation payload you give it passes through the program. It stays in memory for the life of the call and is written nowhere.

The separate components that do use the network

The distil repository also ships a proxy binary and an optional HTTP summarizer. Both are separate from the MCP server, both are off unless you run or configure them, and both send data only to an upstream endpoint that you specify. If you point one at a model provider, your data goes to that provider under their policy, not ours. The MCP server itself contains no HTTP client at all.

Data retention and sharing

We retain nothing, because we receive nothing. There is no data to share, sell, profile or hand to a third party, and no retention period to state.

Who is responsible, and how to reach us

MunHQ operates this tool. Write to hello@munhq.com with any question about this policy, or to ask what we hold about you — the answer is nothing, and we are happy to say so in writing.

This policy covers the tool named above. The munhq.com privacy policy covers the website, and the terms cover both.