Privacy policy

The short version

• This website has no analytics, no tracking pixels, no advertising and no cookies.
• AgentDock is self-hosted software. When you run it, your data stays on your servers. The project and its maintainers never receive it.
• The software contains no telemetry, crash reporting or update checks.

Who this policy covers

"We" means the maintainers of the open-source AgentDock project. This policy covers two things, which are very different:

1. This website, the landing page and documentation you are reading.
2. The AgentDock software, which you download and run yourself.

This website

What we collect

Nothing that identifies you. The site is a static set of pages. It does not set cookies, does not run analytics or session recording, and does not load third-party scripts, embeds or fonts at runtime. The fonts are bundled with the site.

What the browser stores

If you switch the color theme, your choice (dark or light) is saved in your browser's localStorage under the key ad-theme, so the page does not flash the wrong theme on your next visit. It never leaves your device. Choosing "system" removes it.

Hosting and network logs

The site is served through Cloudflare, which processes standard request data (such as IP address, user agent and the requested URL) to deliver the pages and protect them from abuse. Cloudflare handles that data under its own privacy policy. We do not combine it with anything else or use it to profile visitors.

Links to other sites

Pages link to GitHub, npm, Homebrew, skills.sh and other services. Their own privacy policies apply once you follow a link.

The AgentDock software

You are in control

AgentDock runs on infrastructure you operate. The person or organization that runs an instance decides what is stored and is responsible for that data. We have no access to any instance, and there is no hosted AgentDock service and no AgentDock account.

No phone-home

The API, web app and runner contain no telemetry, analytics, crash reporting or update checks. The Docker images built from the repository also turn off Next.js telemetry (NEXT_TELEMETRY_DISABLED=1).

What an instance stores

An instance stores what it needs to show your fleet: user accounts, runners, projects, fleet state, GitHub issue and pull request metadata, agent session metadata (models, token counts, tool names, durations), costs, notifications and an audit log. It does not store prompts, model responses, tool input or output, live pane frames or terminal keystrokes. The full inventory, with retention periods, is in Data and privacy.

Credentials

AgentDock never handles Anthropic or OpenAI API keys and makes no model calls itself. Claude, Codex and GitHub credentials stay on each runner machine. Secrets an instance does store (such as a Telegram bot token or webhook secrets) are encrypted at rest with a key you generate.

Outbound connections

An instance only contacts third parties you configure: GitHub (for the optional GitHub App), Telegram (for the optional bot) and the webhook URLs you add. Runners contact your own server, GitHub through the gh CLI, and skills.sh when someone searches the skills catalog. The agent CLIs themselves talk to their providers under your own accounts.

Downloads

When you install the runner, npm, Homebrew or GitHub Releases serve the files and apply their own policies.

Children

The site and the software are developer tools and are not directed at children.

Changes

If this policy changes, the new version is published here with a new date. The history of this page is public in the project's repository.

Contact

Questions about this policy: open an issue at github.com/AndreyBegma/AgentDock/issues. For anything sensitive, see Security.