|
1 | | -# Roo Code Privacy Policy |
| 1 | +# Zoo Code Privacy Policy |
2 | 2 |
|
3 | | -**Last Updated: September 11th, 2025** |
| 3 | +**Last Updated: May 13th, 2026** |
4 | 4 |
|
5 | | -Roo Code respects your privacy and is committed to transparency about how we handle your data. Below is a simple breakdown of where key pieces of data go—and, importantly, where they don’t. |
| 5 | +Zoo Code respects your privacy and is committed to transparency about how we |
| 6 | +handle your data. Below is a simple breakdown of where key pieces of data |
| 7 | +go—and, importantly, where they don't. |
6 | 8 |
|
7 | | -### **Where Your Data Goes (And Where It Doesn’t)** |
| 9 | +## **Where Your Data Goes (And Where It Doesn’t)** |
8 | 10 |
|
9 | | -- **Code & Files**: Roo Code accesses files on your local machine when needed for AI-assisted features. When you send commands to Roo Code, relevant files may be transmitted to your chosen AI model provider (e.g., OpenAI, Anthropic, OpenRouter) to generate responses. If you select Roo Code Cloud as the model provider (proxy mode), your code may transit Roo Code servers only to forward it to the upstream provider. We do not store your code; it is deleted immediately after forwarding. Otherwise, your code is sent directly to the provider. AI providers may store data per their privacy policies. |
10 | | -- **Commands**: Any commands executed through Roo Code happen on your local environment. However, when you use AI-powered features, the relevant code and context from your commands may be transmitted to your chosen AI model provider (e.g., OpenAI, Anthropic, OpenRouter) to generate responses. We do not have access to or store this data, but AI providers may process it per their privacy policies. |
11 | | -- **Prompts & AI Requests**: When you use AI-powered features, your prompts and relevant project context are sent to your chosen AI model provider (e.g., OpenAI, Anthropic, OpenRouter) to generate responses. We do not store or process this data. These AI providers have their own privacy policies and may store data per their terms of service. If you choose Roo Code Cloud as the provider (proxy mode), prompts may transit Roo Code servers only to forward them to the upstream model and are not stored. |
12 | | -- **API Keys & Credentials**: If you enter an API key (e.g., to connect an AI model), it is stored locally on your device and never sent to us or any third party, except the provider you have chosen. |
13 | | -- **Telemetry (Usage Data)**: We collect anonymous feature usage and error data to help us improve Roo Code. This telemetry is powered by PostHog and includes your VS Code machine ID, feature usage patterns, and exception reports. This telemetry does **not** collect personally identifiable information, your code, or AI prompts. You can opt out of this telemetry at any time through the settings. |
14 | | -- **Zoo Code Observability (Authenticated Subscribers Only):** If you sign in to Zoo Code and have an active subscription, Zoo Code will send LLM usage telemetry to the Zoo Code backend (zoocode.dev). This includes task ID, AI provider name, model name, token counts (input/output/cache), and estimated cost. This data is linked to your authenticated Zoo Code account. You can stop this collection at any time by signing out via the Zoo Code badge in the chat area. |
15 | | -- **Marketplace Requests**: When you browse or search the Marketplace for Model Configuration Profiles (MCPs) or Custom Modes, Roo Code makes a secure API call to Roo Code's backend servers to retrieve listing information. These requests send only the query parameters (e.g., extension version, search term) necessary to fulfill the request and do not include your code, prompts, or personally identifiable information. |
| 11 | +- **Code & Files**: Zoo Code accesses files on your local machine when needed |
| 12 | + for AI-assisted features. When you send commands to Zoo Code, relevant files |
| 13 | + may be transmitted to your chosen AI model provider (e.g., OpenAI, Anthropic, |
| 14 | + OpenRouter) to generate responses. If you select Zoo Code Cloud as the model |
| 15 | + provider (proxy mode), your code may transit Zoo Code servers only to forward |
| 16 | + it to the upstream provider. We do not store your code; it is deleted |
| 17 | + immediately after forwarding. Otherwise, your code is sent directly to the |
| 18 | + provider. AI providers may store data per their privacy policies. |
| 19 | +- **Commands**: Any commands executed through Zoo Code happen on your local |
| 20 | + environment. However, when you use AI-powered features, the relevant code and |
| 21 | + context from your commands may be transmitted to your chosen AI model provider |
| 22 | + (e.g., OpenAI, Anthropic, OpenRouter) to generate responses. We do not have |
| 23 | + access to or store this data, but AI providers may process it per their |
| 24 | + privacy policies. |
| 25 | +- **Prompts & AI Requests**: When you use AI-powered features, your prompts and |
| 26 | + relevant project context are sent to your chosen AI model provider (e.g., |
| 27 | + OpenAI, Anthropic, OpenRouter) to generate responses. We do not store or |
| 28 | + process this data. These AI providers have their own privacy policies and may |
| 29 | + store data per their terms of service. If you choose Zoo Code Cloud as the |
| 30 | + provider (proxy mode), prompts may transit Zoo Code servers only to forward |
| 31 | + them to the upstream model and are not stored. |
| 32 | +- **API Keys & Credentials**: If you enter an API key (e.g., to connect an AI |
| 33 | + model), it is stored locally on your device and never sent to us or any third |
| 34 | + party, except the provider you have chosen. |
| 35 | +- **Telemetry (Usage Data)**: We collect feature usage and error data to help |
| 36 | + us improve Zoo Code. This telemetry is powered by PostHog and includes your |
| 37 | + VS Code machine ID, feature usage patterns, and exception reports. The VS Code |
| 38 | + machine ID is a persistent identifier and may be considered personal data in |
| 39 | + some jurisdictions; we use it only for product analytics and error grouping. |
| 40 | + We retain telemetry only as long as needed for product analytics and debugging. |
| 41 | + Telemetry does **not** collect your code or AI prompts, and you can opt out at |
| 42 | + any time through the settings. |
| 43 | +- **Zoo Code Observability (Authenticated Subscribers Only):** If you sign in to |
| 44 | + Zoo Code and have an active subscription, Zoo Code will send LLM usage |
| 45 | + telemetry to the Zoo Code backend (zoocode.dev). This includes task ID, AI |
| 46 | + provider name, model name, token counts (input/output/cache), and estimated |
| 47 | + cost. This data is linked to your authenticated Zoo Code account. You can stop |
| 48 | + this collection at any time by signing out via the Zoo Code badge in the chat |
| 49 | + area. |
| 50 | +- **Marketplace Requests**: When you browse or search the Marketplace for Model |
| 51 | + Configuration Profiles (MCPs) or Custom Modes, Zoo Code makes a secure API |
| 52 | + call to Zoo Code's backend servers to retrieve listing information. These |
| 53 | + requests send only the query parameters (e.g., extension version, search term) |
| 54 | + necessary to fulfill the request and do not include your code, prompts, or |
| 55 | + personally identifiable information. |
16 | 56 |
|
17 | | -### **How We Use Your Data (If Collected)** |
| 57 | +## **How We Use Your Data (If Collected)** |
18 | 58 |
|
19 | | -- We use telemetry to understand feature usage and improve Roo Code. |
| 59 | +- We use telemetry to understand feature usage and improve Zoo Code. |
20 | 60 | - We do **not** sell or share your data. |
21 | 61 | - We do **not** train any models on your data. |
22 | 62 |
|
23 | | -### **Your Choices & Control** |
| 63 | +## **Your Choices & Control** |
24 | 64 |
|
25 | 65 | - You can run models locally to prevent data being sent to third-parties. |
26 | | -- Telemetry collection is enabled by default to help us improve Roo Code, but you can opt out at any time through the settings. |
27 | | -- You can delete Roo Code to stop all data collection. |
| 66 | +- Telemetry collection is enabled by default to help us improve Zoo Code, but |
| 67 | + you can opt out at any time through the settings. |
| 68 | +- You can delete Zoo Code to stop all data collection. |
28 | 69 |
|
29 | | -### **Security & Updates** |
| 70 | +## **Security & Updates** |
30 | 71 |
|
31 | | -We take reasonable measures to secure your data, but no system is 100% secure. If our privacy policy changes, we will notify you within the extension. |
| 72 | +We take reasonable measures to secure your data, but no system is 100% secure. |
| 73 | +If our privacy policy changes, we will notify you within the extension. |
32 | 74 |
|
33 | | -### **Contact Us** |
| 75 | +## **Contact Us** |
34 | 76 |
|
35 | | -For any privacy-related questions, reach out to us at support@roocode.com. |
| 77 | +For any privacy-related questions, reach out to us at support@zoocode.dev. |
36 | 78 |
|
37 | 79 | --- |
38 | 80 |
|
39 | | -By using Roo Code, you agree to this Privacy Policy. |
| 81 | +By using Zoo Code, you agree to this Privacy Policy. |
0 commit comments