{"version":"2.1.283","anchor":"first-party-metrics-attribute-values-reduced-to-an-allowlis","canonical_anchor":"first-party-metrics-attribute-values-reduced-to-an-allowlis","heading":"Usage metrics send fewer custom names for HIPAA organizations","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/first-party-metrics-attribute-values-reduced-to-an-allowlis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Usage metrics send fewer custom names for HIPAA organizations\n\nFor HIPAA-flagged organizations, or before policy limits load, usage metrics keep only known values and replace custom names with placeholders\n\n**What**\n\nClaude Code sends usage metrics to Anthropic. The details attached to each metric, such as terminal type, account ID format, customer type and tool, skill, plugin and MCP server names, are now filtered through a list of known values in two cases:\n\n- the organization is flagged as a HIPAA organization\n\n- the organization's policy limits have not loaded yet\n\nIn those cases a value that is not on the list is replaced with a placeholder, and a detail with no list at all is dropped. Before, these details were sent unfiltered.\n\n**Why**\n\nThis tightens privacy for regulated organizations: names of custom skills, plugins and MCP servers (MCP servers are add-ons that give Claude Code extra tools) no longer leave the machine in these metrics.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}