Data policies
Data training policy
Consumer users (Free, Pro, and Max plans): Starting August 28, 2025, we’re giving you the choice to allow your data to be used to improve future Claude models. We will train new models using data from Free, Pro, and Max accounts when this setting is on (including when you use Claude Code from these accounts).- If you’re a current user, you can select your preference now and your selection will immediately go into effect. This setting will only apply to new or resumed chats and coding sessions on Claude. Previous chats with no additional activity will not be used for model training.
- You have until October 8, 2025 to make your selection. If you’re a new user, you can pick your setting for model training during the signup process. You can change your selection at any time in your Privacy Settings.
Development Partner Program
If you explicitly opt in to methods to provide us with materials to train on, such as via the Development Partner Program, we may use those materials provided to train our models. An organization admin can expressly opt-in to the Development Partner Program for their organization. Note that this program is available only for Anthropic first-party API, and not for Bedrock or Vertex users.Feedback using the /bug command
If you choose to send us feedback about Claude Code using the /bug command, we may use your feedback to improve our products and services. Transcripts shared via /bug are retained for 5 years.
Data retention
Anthropic retains Claude Code data based on your account type and preferences. Consumer users (Free, Pro, and Max plans):- Users who allow data use for model improvement: 5-year retention period to support model development and safety improvements
- Users who don’t allow data use for model improvement: 30-day retention period
- Privacy settings can be changed at any time at claude.ai/settings/data-privacy-controls.
- Standard: 30-day retention period
- Zero data retention: Available with appropriately configured API keys - Claude Code will not retain chat transcripts on servers
- Local caching: Claude Code clients may store sessions locally for up to 30 days to enable session resumption (configurable)
Data flow and dependencies

Cloud execution
The above data flow diagram and description applies to Claude Code CLI running locally on your machine. For cloud-based sessions using Claude Code on the web, see the section below.
- Code storage: Your repository is cloned to an isolated VM and automatically deleted after session completion
- Credentials: GitHub authentication is handled through a secure proxy; your GitHub credentials never enter the sandbox
- Network traffic: All outbound traffic goes through a security proxy for audit logging and abuse prevention
- Data retention: Code and session data are subject to the retention and usage policies for your account type
- Session data: Prompts, code changes, and outputs follow the same data policies as local Claude Code usage
Telemetry services
Claude Code connects from users’ machines to the Statsig service to log operational metrics such as latency, reliability, and usage patterns. This logging does not include any code or file paths. Data is encrypted in transit using TLS and at rest using 256-bit AES encryption. Read more in the Statsig security documentation. To opt out of Statsig telemetry, set theDISABLE_TELEMETRY environment variable.
Claude Code connects from users’ machines to Sentry for operational error logging. The data is encrypted in transit using TLS and at rest using 256-bit AES encryption. Read more in the Sentry security documentation. To opt out of error logging, set the DISABLE_ERROR_REPORTING environment variable.
When users run the /bug command, a copy of their full conversation history including code is sent to Anthropic. The data is encrypted in transit and at rest. Optionally, a Github issue is created in our public repository. To opt out of bug reporting, set the DISABLE_BUG_COMMAND environment variable.
Default behaviors by API provider
By default, we disable all non-essential traffic (including error reporting, telemetry, and bug reporting functionality) when using Bedrock or Vertex. You can also opt out of all of these at once by setting theCLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC environment variable. Here are the full default behaviors:
| Service | Claude API | Vertex API | Bedrock API |
|---|---|---|---|
| Statsig (Metrics) | Default on.DISABLE_TELEMETRY=1 to disable. | Default off.CLAUDE_CODE_USE_VERTEX must be 1. | Default off.CLAUDE_CODE_USE_BEDROCK must be 1. |
| Sentry (Errors) | Default on.DISABLE_ERROR_REPORTING=1 to disable. | Default off.CLAUDE_CODE_USE_VERTEX must be 1. | Default off.CLAUDE_CODE_USE_BEDROCK must be 1. |
Claude API (/bug reports) | Default on.DISABLE_BUG_COMMAND=1 to disable. | Default off.CLAUDE_CODE_USE_VERTEX must be 1. | Default off.CLAUDE_CODE_USE_BEDROCK must be 1. |
settings.json (read more).