← Back to UniFi MCP

# Privacy Policy

Last updated: March 24, 2026

UniFi MCP does not collect, store, or transmit your personal data. All communication stays between your AI agent and your local UniFi controller. We have no servers, no analytics, no telemetry, and no tracking.

## How UniFi MCP Works

UniFi MCP is a set of Model Context Protocol servers that run locally on your machine. They connect directly to your UniFi controller on your local network. Your AI agent (Claude Code, Claude Cowork, or other MCP clients) communicates with the MCP server over a local stdio or HTTP connection.

    Your AI Agent <--local--> MCP Server (on your machine) <--your network--> UniFi Controller

## What We Don't Collect

- No telemetry. We do not collect usage data, error reports, or analytics of any kind.
- No network traffic. We do not monitor, log, or transmit your network traffic or device data.
- No credentials. Your UniFi username, password, and API keys are stored only in your local environment variables or config files. They are never sent to us or any third party.
- No personal data. We do not collect names, email addresses, IP addresses, or any identifying information.
- No cookies or tracking. There is no web interface, no cookies, no tracking pixels.

## Data Flow

### Local Mode (default)

All data stays on your machine and your local network:

1. Your AI agent sends a tool call to the MCP server (running locally)
2. The MCP server queries your UniFi controller over your local network (HTTPS)
3. The controller responds with the requested data
4. The MCP server formats and returns the result to your AI agent

No data leaves your network.

### Relay Mode (optional)

If you choose to enable the cloud relay, your tool calls are proxied through a Cloudflare Worker:

- The Cloudflare Worker processes tool calls in transit but does not store them
- Communication is encrypted (WSS/TLS)
- Access is scoped by a token you generate and control
- No inbound ports are exposed on your network
- You can revoke relay access at any time by rotating or deleting your token

## Third-Party Services

Service | When Used | What It Sees
--- | --- | ---
Your UniFi Controller | Always | Tool requests over your local network
Cloudflare Workers | Only if you enable relay | Tool calls in transit (encrypted, not stored)
PyPI | During installation | Standard package download
GitHub | During plugin installation | Plugin source code download

We do not integrate with any analytics, advertising, or data broker services.

## Your Controller Credentials

- Credentials are stored in your local environment variables, `.env` file, or Claude Code `settings.json`
- They are read at startup and used to authenticate with your controller
- They are never logged, transmitted externally, or stored in any persistent database
- API keys (if used) follow the same local-only pattern

## Data Retention

UniFi MCP stores nothing. There is no database, no cache, no log files, and no session state. All data lives on your UniFi controller. When the MCP server process stops, no data persists.

## Changes to This Policy

If we change this privacy policy, we will update the date at the top and commit the change to the repository. Since UniFi MCP has no data collection, changes would only reflect new features or clarifications.

## Contact

For privacy questions, reach the maintainer via the GitHub repository or the email listed on the maintainer's profile.