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.
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 provider CLIs such as Claude Code, Codex, OpenCode, and Cursor using credentials you configure. When an agent runs, your server sends requests directly to that provider. 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, Linux, and Android apps send the limited product-usage events described below to Mixpanel unless you turn usage analytics off in Settings. The desktop apps tag those events with an anonymous per-install identifier; the Android app sends them without one. Shared chat web pages may send the strictly limited share events described below, without creating a persistent viewer 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, anonymous usage analytics are on by default, without a first-run prompt. On macOS, Windows, and Linux you can turn them on or off at any time under Settings → General → Usage analytics; on Android, in Settings. Your choice is stored on the device and preserved across updates and restarts. The iOS and iPadOS apps do not send Mixpanel events or other custom usage analytics and do not create or store an analytics identifier.
These apps send a small, fixed set of named product-usage events to Mixpanel — for example launching the app; creating, opening, resuming, forking, or reordering a chat; sending a message; using a slash command or skill; opening split view, the terminal, a file preview, search, digests, or Team Network; opening the share dialog, choosing a snapshot or interactive share type (chat_share_snapshot_selected, chat_share_interactive_selected), creating a snapshot or interactive share, or revoking a share; creating or managing a scheduled job; and testing, adding, or switching a server. Each event carries only a fixed envelope: on macOS, Windows, and Linux an anonymous per-install identifier (a random ID generated on your device, not tied to your name, account, email, or hardware), the event time, and a coarse platform value (mac, windows, linux, or desktop); the Android app sends the same envelope with an empty identifier. A few server-connection events add a single success/failure flag. The app posts directly to Mixpanel with IP-based geolocation disabled (ip=0), sends no cookies or referrer data, and does not use autocapture or session replay. Events do not include message, prompt, or chat content; chat titles; file names, contents, or paths; working directories; URLs; server names or addresses; access or share tokens; chat, session, job, route, or share IDs; job, agent, folder, skill, or command names; schedule expressions or run times; terminal output; or destination metadata. Mixpanel remains a third-party processor and may handle network request metadata under its own privacy policy.
Shared chat web pages may send a separate, strictly limited set of Mixpanel events: shared_chat_snapshot_activated or shared_chat_interactive_activated after authentication succeeds and the conversation is displayed, and shared_chat_message_sent only after the server accepts an interactive message, including queued messages. Rejected or unconfirmed sends are not counted. These shared-page events do not create or store a persistent viewer identifier and do not confirm that the viewer is a different person from the person who created the share. Their payload does not include chat content, prompts, responses, titles, URLs, files, tokens, identities, session IDs, share IDs, request IDs, or other identifiers. Requests omit credentials, use a no-referrer policy, and set ip=0 to disable Mixpanel IP-based geolocation; like any network request, ordinary transport information such as IP address and browser Origin may still be visible to the processor. Refreshes and reconnects are de-duplicated with a one-way digest kept in sessionStorage and not uploaded. Shared-page analytics support aggregate usage counts only, not unique viewer counts or cross-device per-user funnels. We do not enable general web analytics, autocapture, advertising pixels, or session replay on shared chat pages, and no shared-page event is sent when Global Privacy Control, Do Not Track, a same-origin prior opt-out, or unavailable browser storage prevents it.
Turning analytics off stops future events from that app and, on macOS, Windows, and Linux, deletes the per-install identifier from your device, so later activity cannot be linked to earlier events. It does not automatically delete event records Mixpanel has already received. Because the identifier is random and not tied to your name or account, we cannot identify you from those records.
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.
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, and the strictly limited shared chat page events described above, 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 and removes the per-install identifier from your device, but does not by itself delete event records already received. Because that identifier is random and not linked to a person, we generally cannot associate those app events with you; shared chat page events do not create a persistent viewer identifier.
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.