Skip to docs content
Conductor

Privacy

What we do (and don't do) with your data.

What data do we access?

For Cloud workspaces, Conductor stores session inputs and outputs on its servers so agents can keep working, chats stay synchronized, and members of your organization can collaborate in the workspace together.

For local workspaces, we don't access your chats. Your messages go directly to your model provider, and your session data stays on your Mac.

We also collect analytics data, such as which features you use and crash logs. This helps us fix bugs and learn which parts of Conductor to improve.

Where do you store my chats?

Cloud chat history is stored on Conductor's servers. Local chat history is saved in the Application Support directory ~/Library/Application Support/com.conductor.app.

What types of data does Conductor collect?

Conductor stores:

  • Account data, such as your email address and, if you integrate with GitHub, installation data
  • Cloud workspace data, including session inputs, outputs, and the workspace state needed to run and synchronize the workspace

We store analytics data in PostHog when an event occurs in the app, such as:

  • You create a workspace, select a model, or send a message, including metadata such as which model was involved and which app features you're using
  • A model provider returns an error, including the error message
  • An unexpected error occurs, including the error message and stack trace

PostHog stores data about your computer, such as your operating system and IP address.

Where does my network traffic go?

In Cloud workspaces, sessions run in Conductor-managed infrastructure. Conductor stores session inputs and outputs, model requests go to the provider you configure, and requests to MCP servers, GitHub, and other integrations go to those services.

In local workspaces, model traffic goes straight to your model provider.

What data do the model providers collect? Are my messages used for training?

You can find the privacy policies of our model providers here:

Is my data encrypted? Who can access my data?

Data Conductor stores, such as account and Cloud workspace data, is encrypted. Analytics data is stored on PostHog's servers.

Local chat data can be accessed by people and processes that can access your Mac user account.

Data sent to a model provider or integration is governed by that service's security, access, and privacy policies.

Enterprise data privacy

Enterprise data privacy is a local-only setting that disables features that require external AI providers, such as AI-generated chat titles and custom MCP servers. Enterprise data privacy cannot be used in cloud.

  • User level — toggle it in SettingsPrivacy. This applies to your machine only.
  • Repo level — set enterprise_data_privacy to true in .conductor/settings.toml. This applies to everyone working in the repo when the file is committed.
.conductor/settings.toml
"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"
enterprise_data_privacy = true
Info:

These settings are independent. If either one is enabled, Enterprise data privacy is enabled. You don't need to configure both.

On this page