1---
 2title: Telemetry
 3description: "What data Zed collects and how to control telemetry settings."
 4---
 5
 6# Telemetry in Zed
 7
 8Zed collects anonymous telemetry to understand usage patterns and diagnose issues.
 9
10Telemetry falls into two categories:
11
12- **Client-side**: Usage metrics and crash reports. You can disable these in settings.
13- **Server-side**: Collected when using hosted services like AI or Collaboration. Required for these features to function.
14
15## Configuring Telemetry Settings
16
17You have full control over what data is sent out by Zed.
18To enable or disable some or all telemetry types, open Settings ({#kb zed::OpenSettings}) and search for "telemetry", or add the following to your settings file:
19
20```json [settings]
21"telemetry": {
22    "diagnostics": false,
23    "metrics": false
24},
25```
26
27## Dataflow
28
29Telemetry is sent from the application to our servers every 5 minutes (or when 50 events accumulate), then routed to the appropriate service. We currently use:
30
31- [Sentry](https://sentry.io): Crash-monitoring service - stores diagnostic events
32- [Snowflake](https://snowflake.com): Data warehouse - stores both diagnostic and metric events
33- [Hex](https://www.hex.tech): Dashboards and data exploration - accesses data stored in Snowflake
34- [Amplitude](https://www.amplitude.com): Dashboards and data exploration - accesses data stored in Snowflake
35
36## Types of Telemetry
37
38### Diagnostics
39
40Crash reports consist of a [minidump](https://learn.microsoft.com/en-us/windows/win32/debug/minidump-files) and debug metadata. Reports are sent on the next launch after a crash, allowing Zed to identify and fix issues without requiring you to file a bug report.
41
42You can inspect what data is sent in the `Panic` struct in [crates/telemetry_events/src/telemetry_events.rs](https://github.com/zed-industries/zed/blob/main/crates/telemetry_events/src/telemetry_events.rs). See also: [Debugging Crashes](./development/debugging-crashes.md).
43
44### Client-Side Metrics
45
46Client-side telemetry includes:
47
48- File extensions of opened files
49- Features and tools used within the editor
50- Project statistics (e.g., number of files)
51- Frameworks detected in your projects
52
53This data does not include your code or sensitive project details. Events are sent over HTTPS and rate-limited.
54
55Usage data is tied to a random telemetry ID. If you've authenticated, this ID may be linked to your email so Zed can analyze patterns over time and reach out for feedback.
56
57To audit what Zed has reported, run {#action zed::OpenTelemetryLog} from the command palette or click `Help > View Telemetry Log`.
58
59For the full list of event types, see the `Event` enum in [telemetry_events.rs](https://github.com/zed-industries/zed/blob/main/crates/telemetry_events/src/telemetry_events.rs).
60
61### Server-Side Metrics
62
63When using Zed's hosted services, we collect metadata for rate limiting and billing (e.g., token usage). Zed does not store your prompts or code unless you explicitly share them via feedback ratings.
64
65For details on AI data handling, see [Zed AI Features and Privacy](./ai/ai-improvement.md).
66
67## Concerns and Questions
68
69If you have concerns about telemetry, you can [open an issue](https://github.com/zed-industries/zed/issues/new/choose) or email hi@zed.dev.