Documentation Index
Fetch the complete documentation index at: /docs/llms.txt
Use this file to discover all available pages before exploring further.
Data usage
Learn about Anthropic’s data usage policies for Claude
Data policies
Data training policy
Development Partner Program
Feedback using the /feedback command
Session quality surveys
Yes: uploads your conversation transcript, any subagent transcripts, and the raw session log file from disk to Anthropic. Known API key and token patterns are redacted before upload. Source code, file contents, and other conversation content are uploaded as-is. Shared transcripts are retained for up to 6 months. On Amazon Bedrock, Google Cloud’s Agent Platform, Microsoft Foundry, and signed-in Claude apps gateway sessions, Yes writes the same payload to a local archive under ~/.claude/feedback-bundles/ instead of uploading; nothing leaves your machine until you forward that file.
No: declines without sending anything
Don’t ask again: declines and stops this follow-up from appearing in future sessions
Data retention
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.
claude.ai/settings/data-privacy-controls
Standard: 30-day retention period
Zero data retention: available to qualified accounts for Claude Code on Claude for Enterprise. ZDR is not included in the standard Enterprise plan; it is enabled on a per-organization basis by your account team after confirming eligibility
Local caching: Claude Code clients store session transcripts locally in plaintext under ~/.claude/projects/ for 30 days by default to enable session resumption. Adjust the period with cleanupPeriodDays. See application data for what’s stored and how to clear it.
Data access
Local Claude Code: Data flow and dependencies
Cloud execution: Data flow and dependencies
Code and data storage: Your repository is cloned to an isolated VM. Code and session data are subject to the retention and usage policies for your account type (see Data retention section above)
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
Session data: Prompts, code changes, and outputs follow the same data policies as local Claude Code usage
Telemetry services
you sign in with a Claude Pro or Max subscription
you’re running Claude Code v2.1.198 or later
you’re connecting directly to the Claude API
your organization doesn’t have a zero data retention or HIPAA agreement
Default behaviors by API provider
WebFetch domain safety check
Was this page helpful?