Delta is built by Zed Industries. Your use of Delta is governed by the General Terms of Service, which also cover the Zed editor, and the Delta Product Terms. Delta and Zed share the same Privacy Policy.
Delta stores repository and thread data to provide synchronization and collaboration. Data Storage & Deletion explains what Delta stores, where it lives, and how to request deletion. The sections below cover data sent to model providers and product telemetry.
AI requests
When you send a message to an agent, Delta sends a model request to your selected model provider. Requests to hosted models go through Zed Cloud; requests to a provider you connected yourself, with an API key or a subscription sign-in, go directly to that provider. For ChatGPT and Grok subscriptions, Zed Cloud stores the OAuth grant and gives Delta short-lived access tokens; the model request itself still goes directly to the provider. The request can include conversation history, collaborator messages and comments, attached images, tool calls and results, terminal or command output, and file content the agent reads while working. The agent can also search your other threads and read their transcripts with a tool, so a request can carry content from past threads, in bounded excerpts. The thread you are working in is excluded from that tool.
Claude Agent turns run Claude Code on your computer. Claude Code sends its requests directly to Anthropic under the Claude subscription or Anthropic Console account you signed in with, and Anthropic’s terms for that account apply. Delta stores the turn’s output in the thread like any other turn. By default, Delta’s own model doesn’t summarize Claude Agent threads; turn on Summarize Claude Agent and Other Agent Threads in Settings > Thread to allow it.
A request includes the context provided to the agent for its current work. Delta does not automatically send every file in the repository.
Delta uses the same model providers, request paths, and provider agreements as Zed. See AI Privacy for provider-specific data handling, retention, and training commitments.
Delta redacts recognized secret values before storing thread content or sending it to a model provider. See Secret redaction.
Data use and training
Delta stores repository and thread data to synchronize your work across machines and enable collaboration. Delta does not use your code or conversations to train AI models.
Model providers handle AI requests under the same agreements and policies as Zed. See AI Privacy for provider-specific no-training and retention commitments.
For Delta’s own storage and deletion practices, see Data Storage & Deletion.
Telemetry
Delta uses Zed’s telemetry infrastructure. Because signing in is required to use Delta, Delta telemetry is associated with your authenticated account. Delta does not currently provide a setting to disable telemetry.
Delta collects product-usage metadata such as which features are used, agent outcomes, model selection, and thread or Delta worktree activity. This telemetry does not include your conversations, source code, repository names, remote URLs, or terminal output. When Delta shows you an error, the error’s message text is included in telemetry.
See Telemetry in Zed for information about the shared telemetry infrastructure and data handling. The opt-out controls described there do not apply to Delta.
Crash and error reporting
Delta reports crashes and visible errors to Sentry, and there is no setting to disable this. Error reports carry the error’s message text, where in Delta’s code the error occurred, the app version, and similar diagnostic metadata. Crash reports include the crash message and a memory dump of the app at the moment it crashed, which can contain thread content. When you are signed in, reports carry the same identifier as telemetry, your Zed and GitHub usernames, and internal identifiers for the thread and Delta worktrees involved (the identifiers, not their contents).