Legal
Privacy Policy
AgentsDock is a self-hosted workspace. You run your own AgentsDock server, and your chats, files, terminals, and credentials stay on infrastructure you control. This policy explains what the AgentsDock apps (macOS, Windows, Linux, iOS, iPadOS, and Android) do and do not collect.
1. Who we are
AgentsDock ("AgentsDock", "we", "us") provides desktop and mobile client applications that connect to an AgentsDock server that you install and operate yourself. Because the server runs on your own machine or cluster, you are the controller of the content you create with it.
2. Information the app does not collect
The AgentsDock client apps are designed to minimize data collection. We do not operate a cloud backend that receives your content, and specifically we do not collect, transmit to us, sell, or share:
- Your chat messages, prompts, or agent responses;
- Your source code, files, media, or command output;
- Your model provider API keys or access tokens;
- Your terminal sessions or scheduled jobs.
This content is stored on the AgentsDock server you run (by default under ~/.agentsdock) and is exchanged directly between the app and your server over a network connection you configure, such as your local network or Tailscale.
3. Information stored on your device
To connect to your server, the app stores configuration locally on your device, including your server URL and, where applicable, an access token (kept in the operating system's secure storage, such as the Apple Keychain). This information stays on your device and is used only to reach the server you specify. You can remove saved server profiles and credentials in the app. Uninstall behavior varies by platform: desktop app data and operating-system secure storage, including Keychain entries, may remain until you clear them through the applicable operating-system controls.
Source snapshot note: website analytics initialization is disabled here. The policy below describes the official product and website; deployments of this source must review their own analytics configuration and privacy disclosures.
4. Third-party services
Depending on how you use AgentsDock, the following third parties may be involved. Their handling of data is governed by their own policies:
- AI model providers. Your AgentsDock server runs command-line agents such as Claude Code and Codex using API keys you provide. When an agent runs, your server sends requests directly to that provider (for example, Anthropic or OpenAI) under your own account. AgentsDock does not proxy, resell, or observe these requests. See the applicable provider's privacy policy.
- Apple. If you install the app from the App Store or TestFlight, Apple may collect information related to distribution, and any crash diagnostics you choose to share are handled by Apple under Apple's privacy policy.
- Mixpanel. The macOS, Windows, and Linux apps send the limited product-interaction events described below to Mixpanel, tagged with an anonymous, non-identifying per-installation identifier, unless you turn usage analytics off in Settings. The Android app sends the same events with no such identifier. The iOS and iPadOS apps do not send events to Mixpanel. See Mixpanel's Privacy Policy.
- Google Analytics. Our marketing website uses Google Analytics as described below. Google Analytics does not run inside the AgentsDock apps. See Google's Privacy Policy.
5. Analytics and tracking
The AgentsDock apps do not include third-party advertising SDKs, do not track you across other apps or websites, and do not sell personal data.
In the macOS, Windows, Linux, and Android apps, limited usage analytics are on by default, without a first-run analytics prompt. You can turn them off at any time in Settings. The iOS and iPadOS apps do not send Mixpanel events or other custom usage analytics and do not create or store an app analytics identifier.
The macOS, Windows, Linux, and Android apps send a small, fixed set of product-interaction events to Mixpanel, such as launching the app, opening a chat, sending a message, opening a terminal or file viewer, using search or digests, scheduling a job, and testing, adding, or switching a server. Each event includes the app platform, the event time, and limited success/failure flags where relevant. On macOS, Windows, and Linux, each event is also tagged with an anonymous, randomly generated per-installation identifier so we can measure unique installations and retention; that identifier is stored only in the app's local storage on your device, is not linked to your name, account, machine, server, or any content, and is deleted if you turn analytics off. On Android, events are sent with an empty distinct_id and no persistent identifier. On all platforms, Mixpanel is called with IP-based geolocation disabled (ip=0). Events do not include chat content, prompts, agent responses, source code, file names or contents, working-directory paths, server names or addresses, access tokens, terminal output, scheduled-job content, screen recordings, automatic UI capture, or IP-derived location. Mixpanel remains a third-party processor and may handle network request metadata under its own privacy policy.
Turning analytics off in the macOS, Windows, Linux, or Android app stops future Mixpanel events from that app; on macOS, Windows, and Linux it also deletes the per-installation identifier from your device. It does not automatically delete event records Mixpanel already received. On macOS, Windows, and Linux, previously received events from one installation share that anonymous per-installation identifier and can therefore be associated with each other — but not with your identity, account, or content — and reinstalling or clearing app data begins a new identifier. On Android, previously received events carry no such identifier and generally cannot be associated with one installation.
Our marketing website (agentsdock.net) uses Google Analytics to measure traffic — such as page views and clicks on outbound links — so we can understand how the site is used. Google Analytics is scoped to the website and does not run inside the AgentsDock apps. Google may process request information and identifiers under its own privacy policy.
Selected desktop usage events also include only the built-in Agent family (Codex, Claude, Cursor, OpenCode, or Gemini). This is not a model name, API endpoint, account, or custom connection name. Explicit model and permission changes, archive actions, file-open requests, language/font changes, restart requests, and diagnostic-copy/report actions are measured without the selected values or diagnostic content.
Accepted desktop message events may also include a coarse connection type: the default provider route or an AgentsDock-managed Custom API connection. This is separate from the Agent family and does not identify the API endpoint, model, key, account, connection name, or authentication method. Missing connection information is omitted rather than inferred. Failed submissions and model-switch commands are not counted as accepted messages.
Authenticated shared-chat browser pages use a separate limited tracker for three actions: viewing a read-only snapshot, activating an interactive chat, and having a message accepted (including queued messages). These events use an empty distinct_id, no persistent visitor identifier, and no chat/share/request IDs or hashes in the transmitted payload. Tab-local markers reduce duplicate counts after reload/reconnection; a new tab can count again, so activation is not a count of distinct people. Browser Do Not Track, Global Privacy Control, an existing same-origin analytics opt-out, or unavailable storage suppress this tracker. Requests omit credentials and referrers, disable IP-based geolocation, and contain no invitation tokens, URLs, titles, messages or files. Mixpanel may still receive ordinary network metadata such as IP and Origin. No SDK autocapture or session replay is used.
6. Data retention and deletion
Because your content lives on your own server, you control its retention. You can delete chats, files, and jobs from within the app, and you can remove all stored server state by deleting the server's data directory (by default ~/.agentsdock). Client connection settings and credentials can be removed in the app. Uninstalling alone may not clear desktop app data or operating-system secure storage, so complete client-data removal may also require clearing those stores through your operating system.
Mixpanel events from the macOS, Windows, Linux, and Android apps are managed under our Mixpanel project's retention controls and retained only while needed to measure feature-adoption and platform-reliability trends. We periodically review that need and delete analytics when they are no longer needed. Turning analytics off stops future events from that app but does not by itself delete event records already received. On macOS, Windows, and Linux, events carry an anonymous per-installation identifier that lets us associate an installation's events with each other, but not with your identity, account, or content; on Android, events carry no such identifier and generally cannot be associated by installation.
7. Security
We recommend running your AgentsDock server over a private network or an encrypted connection such as Tailscale, enabling server authentication, and keeping your device and server operating systems up to date. No method of transmission or storage is completely secure, but the self-hosted design keeps your data within your own environment.
8. Children
AgentsDock is a developer and research tool and is not directed to children under the age of 13, and we do not knowingly collect personal information from children.
9. Changes to this policy
We may update this policy from time to time. When we do, we will revise the "Last updated" date above and post the new version at this URL.
10. Contact
If you have questions about this policy or AgentsDock's privacy practices, contact us at contact@agentsdock.net or reach us on our Discord server.