Telemetry
We collect minimal, privacy-preserving operational metrics to improve reliability, performance, and user experience.
Overview
Telemetry is enabled by default but can be easily opted out of. No personally identifiable information is collected, and sensitive data is excluded or anonymized.
What We Collect
Extension Lifecycle
Installation, session starts, version info, platform/OS.
Model Usage
Model/provider name, input/output token counts (no content).
Feature Usage
Feature names (e.g., MCP tools, context rules). Tool names for MCP only.
Performance Metrics
API latency, error counts, retry counts, and provider (no model or token data).
Anonymous Errors
Error categories and severity only (no stack traces or messages).
Session Data
Anonymous session IDs, message counts for engagement metrics.
We Do NOT Collect
- Source code contents or repository data
- Prompts or outputs: raw prompt text or model responses
- Secrets: API keys, access tokens, cookies, auth headers
- File paths or filenames
Events We Track
extension_install
Once on first install. Includes version, platform, VS Code version.
user_login
Once when a user logs in.
session_start
Each VS Code start. Includes version, anonymous session ID.
message_sent
When user sends a message. Model name, token count (no content).
prompt_sent
When a prompt is sent to a model. Provider, token counts (no content).
feature_used
When features are used (e.g., settings_opened, login_button_clicked, telemetry_toggled).
performance_metric
Metric name, latency, error count, retry count, provider, and version. No model id or token data.
error_occurred
Error type, severity, context, and version (no stack traces, no model id).
code_edited
Change type and session ID.
code_read
Session ID only.
checkpoint_restore
When code is restored from a checkpoint.
inference_timing
Inference duration with start and end timestamps only.
new_chat
When a new chat is started.
user_logout
Once when a user logs out.
session_end
When the extension is deactivated (e.g., VS Code closes).
ollama_detection
When installed Ollama models are auto-detected.
ollama_model_import
When an Ollama model is imported via one-click import.
Privacy & Security
All telemetry events are validated against a strict schema before transmission to prevent accidental data leakage. Errors are categorized by type without specific messages or stack traces.
Opt-out Options
1. Codistry settings
Click the settings gear at the top of the Codistry panel → "General" tab → uncheck "Enable Telemetry".
2. VS Code global telemetry
Codistry also respects VS Code's own switch: File → Preferences → Settings → "Telemetry Level" → "off".
Once opted out, no telemetry events are emitted. Codistry respects VS Code's global telemetry settings automatically.
Data Storage & Retention
Telemetry data is sent to PostHog (hosted at us.i.posthog.com) and retained according to our data retention policy.