{"version":"2.1.295","anchor":"telemetry-attributes-email-and-terminaltype-change-in-a-re","canonical_anchor":"telemetry-attributes-email-and-terminaltype-change-in-a-re","heading":"Usage data leaves out your email in a restricted mode","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/telemetry-attributes-email-and-terminaltype-change-in-a-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Usage data leaves out your email in a restricted mode\n\nIn a certain restricted mode, usage data no longer includes your email and reports a fixed terminal type\n\n**Unclear.** The condition that switches on the restricted mode is not stated, so it is unclear who gets this behaviour.\n\n**What**\n\nClaude Code attaches some details to the usage data it reports. In a certain restricted mode this now changes:\n\n- `user.email` is no longer included. Before, it was added whenever an email was known.\n\n- `terminal.type` is reported as a fixed value instead of the terminal Claude Code detected.\n\nOutside that mode, both behave as before.\n\n**Why**\n\nThis is a privacy-related change: in that mode, less identifying information goes out with usage data.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}