Data, privacy, and network access

This page lists what the extension sends to CodeRabbit, the hosts it connects to, and what it keeps on your computer. Use it to review the extension for security approval, to configure a firewall or proxy, or to remove all local data.

​

What a review sends

For each file in the review, the extension sends:

• the file path
• the full current content of the file
• the diff
• whether the file is new, renamed, or deleted

Each review also sends:

• the first of .coderabbit.yaml, .coderabbit.yml, or .coder.yaml at the root of the workspace folder, if there is one
• for a follow-up review, the files and diffs from the previous review, and CodeRabbit’s internal state from it
• your CodeRabbit user ID, username, and email, your user ID at your Git provider, and a client ID for the editor installation
• the selected organization’s ID and its Git provider
• the origin remote URL, or the first remote’s URL if there is no origin, with any credentials removed, and your Git provider’s host URL
• the editor type and the extension version
• the head and base commits

With self-hosted CodeRabbit, reviews go to your instance instead of CodeRabbit Cloud. Fix with AI sends nothing to CodeRabbit. It hands the finding’s prompt to the agent you chose, inside your editor, and that agent’s own data terms apply.

​

Keep secrets out of reviews

The extension doesn’t scan files for secrets, so it sends a file such as .env unless the rules below keep it out. Its built-in exclusions skip *.pem, *.pub, and Terraform state files, but not .env files, other key files, or credential files. Which of those files a review sends depends on Git:

• With coderabbit.respectGitIgnore on, which is the default, an untracked file that .gitignore covers isn’t sent.
• A tracked or staged file is sent with its full content, even if .gitignore lists it.
• A new file that Git doesn’t ignore is sent with its full content.

To keep a secrets file out of reviews, add it to .gitignore before Git tracks it, and don’t commit or stage it. An ignore rule doesn’t exclude a file that Git already tracks. For uncommitted changes to such a file, clear its checkbox in Uncommitted changes and start the review with the review button, because CodeRabbit: Start Review from the Command Palette reviews every uncommitted file. All changes and Committed changes have no checkboxes, so in those scopes a changed tracked file that holds secrets is sent. Path filters such as !**/.env* keep a file out of the review itself, but CodeRabbit applies them after the upload, so the file is still sent.

​

How CodeRabbit uses your code

CodeRabbit uses the uploaded files to review your changes. With the Essentials plan or higher, it can also clone the repository from your Git provider for codebase context; see Which review configuration applies for when. Your code isn’t used to train models. Review caching follows the same rules as for other reviews; see Caching, including how to turn it off. For data security and retention, see the FAQ.

​

Network access

The extension needs outbound HTTPS and WebSocket traffic on TCP port 443. It needs no inbound firewall rules. The telemetry host comes from the public configuration; k.coderabbit.ai is the default. If storage.googleapis.com is blocked, the update check fails silently and nothing else breaks. With self-hosted CodeRabbit, sign-in and reviews go to your instance URL and <instance-url>/ws, and the extension doesn’t contact the app, ide, or telemetry hosts, or cli.coderabbit.ai outside CLI setup. It still contacts storage.googleapis.com for the update check, and us.i.posthog.com on uninstall if that computer was ever signed in to CodeRabbit Cloud. In a workspace you haven’t trusted, the extension ignores the self-hosted URL and uses the CodeRabbit Cloud hosts instead; see Restricted Mode. The extension has no proxy setting of its own. It relies on your editor’s proxy support for extensions, such as http.proxy in VS Code. In a remote window, connections start on the remote machine, so its proxy settings apply. Your proxy must allow WebSocket connections to ide.coderabbit.ai, to ide.eu.coderabbit.ai in the EU region, or to your instance. For the CodeRabbit CLI, see CLI network requirements.

​

Data stored on your computer

The CodeRabbit app data folder is in your home folder on the machine where the extension runs:

• macOS: ~/Library/Application Support/CodeRabbit/
• Windows: %APPDATA%\CodeRabbit\
• Linux: ~/.config/coderabbit/

​

Telemetry

Usage events, such as sign-ins, applied suggestions, and Fix with AI handoffs, follow your editor’s telemetry setting, such as telemetry.telemetryLevel in VS Code. Error events replace error messages and stack traces with a generic label. These are sent regardless of the editor’s telemetry setting, and no setting turns them off:

• an install event, once per installation, after you sign in
• a user identification call each time you sign in to CodeRabbit Cloud
• the creation of your extension profile, when you sign in to CodeRabbit Cloud
• an uninstall event, sent to us.i.posthog.com after the extension is removed, if user-data.json exists

With self-hosted CodeRabbit, the extension sends no usage events, and the install event goes to your instance. When the extension sets up the CodeRabbit CLI, it passes your editor’s telemetry choice to the CLI installer and the CLI.

​

Remove local data

To remove the stored reviews, sign-in data, and files the extension keeps, do these steps in order: These steps don’t clear everything. The extension’s global state in the editor, such as the client ID and which prompts you dismissed, and any CodeRabbit settings you changed other than the self-hosted URL, can remain. Reset those settings in your editor’s settings. The extension doesn’t uninstall the CodeRabbit CLI or its skills. Remove them separately as described in the CLI documentation.

​

What’s next