Privacy Policy

Munim · last updated 4 September 2026

Munim is an open source command line tool that runs on your own computer. It is not a hosted service. There is no Munim server, no Munim account, and no operator of Munim who can see your data.

The short version. Your credentials stay in your operating system's keychain. Data from the services you connect goes between your computer and those services directly. If you use the features that reason about that data, it is also sent to the AI model provider you choose and configure. Nothing is ever sent to the authors of Munim.

What Munim handles

Credentials. When you connect a service, the resulting OAuth token or API key is stored in your operating system's keychain, filed under an identifier for the client it belongs to. Munim's code never returns a raw credential to the code that uses it; adapters receive an already authenticated connection.
Service data. Whatever the service returns while you are using it: DNS records, deployment details, project names. If you connect Gmail, that includes message content and metadata your instructions cause it to read, and drafts your instructions cause it to write.
Run logs and reports. A record of what was done, written to ~/.munim/runs and ~/.munim/reports on your computer.

Where it goes

To the service itself. Munim talks directly from your computer to each provider's own endpoint. Nothing is proxied.

To the AI model provider you configure. This is the part worth reading twice. Munim's checking and reasoning features build an agent using the Strands Agents SDK, and that agent runs on a model host you choose: Amazon Bedrock, Google Gemini, Anthropic, OpenAI or a local model through Ollama. When you invoke those features, the data the agent is working with is sent to that provider under your own API key and their terms. If Gmail is connected and you ask the agent to work with mail, mail content reaches that provider. Choosing a locally hosted model keeps it on your machine.

Nowhere else. Munim contains no analytics, no telemetry, no crash reporting and no update check. It sends nothing to its authors. You can confirm this by reading the source.

Google user data

Munim's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically: Google user data is used only to provide the features you invoke. It is not sold, not transferred to anyone except the AI model provider you configure in order to perform those features, not used for advertising, and not used to train any model by Munim. Munim's authors have no access to it.

Keeping and removing it

Everything lives on your computer for as long as you leave it there.

munim disconnect "<client>" <service> removes one stored credential.
munim disconnect --all removes every stored credential.
Deleting ~/.munim removes the run logs, reports and the client list.
Revoking Munim's access at the provider, for example at Google account permissions, invalidates the credential regardless of what is on your machine.

Children

Munim is a tool for people administering their own or their clients' web infrastructure. It is not directed at children and collects nothing from anyone.

Changes and contact

Changes to this policy will be published on this page with a new date, and in the project's commit history, which is public.

Questions: open an issue at github.com/vishalsg42/munim/issues, or use the contact address on the consent screen.