You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
6
+
7
+
### **Where Your Data Goes (And Where It Doesn’t)**
8
+
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. We do not have access to this data, but AI providers may store it 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.
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 only collect feature usage and error data if you explicitly opt-in. This telemetry is powered by PostHog and helps us understand feature usage to improve Roo Code. This includes your VS Code machine ID and feature usage patterns and exception reports. We do **not** collect personally identifiable information, your code, or AI prompts.
14
+
15
+
### **How We Use Your Data (If Collected)**
16
+
17
+
- If you opt-in to telemetry, we use it to understand feature usage and improve Roo Code.
18
+
- We do **not** sell or share your data.
19
+
- We do **not** train any models on your data.
20
+
21
+
### **Your Choices & Control**
22
+
23
+
- You can run models locally to prevent data being sent to third-parties.
24
+
- By default, telemetry collection is off and if you turn it on, you can opt out of telemetry at any time.
25
+
- You can delete Roo Code to stop all data collection.
26
+
27
+
### **Security & Updates**
28
+
29
+
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.
30
+
31
+
### **Contact Us**
32
+
33
+
For any privacy-related questions, reach out to us at [email protected].
34
+
35
+
---
36
+
37
+
By using Roo Code, you agree to this Privacy Policy.
vscode.workspace.workspaceFolders?.map((folder)=>folder.uri.fsPath).at(0)??path.join(os.homedir(),"Desktop")// may or may not exist but fs checking existence would immediately ask for permission which would be bad UX, need to come up with a better solution
// since we sent off a placeholder api_req_started message to update the webview while waiting to actually start the API request (to load potential details for example), we need to update the text of that message
// NOTE: this comment is here for future reference - this was a workaround for userMessageContent not getting set to true. It was due to it not recursively calling for partial blocks when didRejectTool, so it would get stuck waiting for a partial block to complete before it could continue.
0 commit comments