Configured Privacy Profile

Privacy-first environment configuration that minimizes data exposure and external communications.

When to Use This Setting

Apply this setting when you need to:

• Work with sensitive or proprietary codebases where data leakage must be prevented at the environment level
• Comply with organizational privacy policies that restrict telemetry and external network calls
• Create an air-gapped or minimally connected Claude Code session for security-critical work Consider alternatives when:
• You want to benefit from Claude Code telemetry for improving your experience and reporting issues
• Your project does not contain sensitive data and default privacy settings are sufficient

Quick Start

Configuration

Copy
name: configured-privacy-profile
type: setting
category: environment

Example Application

Copy
claude setting:apply configured-privacy-profile

Example Output

Setting applied. Changes:
- CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: 1
- CLAUDE_CODE_DISABLE_TERMINAL_TITLE: 1
- CLAUDE_CODE_DISABLE_TELEMETRY: 1

Core Concepts

Privacy Controls Overview

Aspect	Details
Telemetry	Disables all usage analytics and diagnostic data collection
Terminal Title	Prevents project names and paths from appearing in terminal title bars
Network Traffic	Blocks non-essential outbound requests that could leak project metadata
Local Processing	Ensures all auxiliary operations stay local to the development machine

Privacy Boundary Architecture

+---------------------------+
|     Claude Code Session   |
+---------------------------+
|  [X] Telemetry disabled   |
|  [X] Title updates off    |
|  [X] Non-essential blocked|
+---------------------------+
         |
    Allowed Traffic:
    - API calls to Anthropic
    - Explicit user-initiated
      web fetches
         |
    Blocked Traffic:
    - Analytics endpoints
    - Crash reporting
    - Feature flag checks
    - Background updates

Configuration

Parameter	Type	Default	Description
CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC	string	"1"	Block all non-critical network requests from the session
CLAUDE_CODE_DISABLE_TERMINAL_TITLE	string	"1"	Prevent session info from appearing in the terminal title bar
CLAUDE_CODE_DISABLE_TELEMETRY	string	"1"	Disable all usage telemetry and analytics collection
CLAUDE_CODE_DISABLE_UPDATE_CHECK	string	"1"	Prevent automatic version check requests to external servers
CLAUDE_CODE_LOG_LEVEL	string	"error"	Reduce logging to minimize sensitive data written to log files

Best Practices

1. Layer with file access restrictions - Privacy settings alone do not prevent Claude Code from reading sensitive files. Combine this profile with deny rules for .env files, credentials, and secrets directories.
2. Disable terminal titles in shared environments - In pair programming or screen-sharing sessions, terminal titles can inadvertently expose project names and file paths. This setting eliminates that risk.
3. Review log output locations - Even with telemetry disabled, Claude Code may write session logs locally. Review the log directory and configure log rotation or deletion policies appropriate for your security requirements.
4. Audit network traffic periodically - Use network monitoring tools to verify that the privacy settings are effective and no unexpected outbound connections occur during sessions.
5. Document compliance requirements - Maintain a mapping between your organization's privacy policies and the specific Claude Code settings that enforce them. This simplifies audit processes and onboarding.

Common Issues

1. Update notifications stop appearing - Disabling non-essential traffic also prevents version check notifications. Schedule manual update checks periodically to ensure you are running the latest version with security patches.
2. Debugging is harder without telemetry - When reporting bugs to Anthropic, the lack of telemetry data means support teams have less context. Be prepared to provide detailed reproduction steps manually.
3. Terminal title remains static - Some terminal multiplexers cache the last title update. After applying this setting, you may need to restart your terminal or multiplexer session to clear the cached title.