{"version":"2.1.283","anchor":"metrics-exporter-redacts-attributes-under-hipaa-policy-or-wh","canonical_anchor":"metrics-exporter-redacts-attributes-under-hipaa-policy-or-wh","heading":"Metrics sent to Anthropic are trimmed under a HIPAA policy or before policy loads","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/metrics-exporter-redacts-attributes-under-hipaa-policy-or-wh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Metrics sent to Anthropic are trimmed under a HIPAA policy or before policy loads\n\nMetrics sent to Anthropic keep only allowed details when a HIPAA policy applies, or when your organisation's policy hasn't loaded yet\n\n**Unclear.** It is not clear which attributes are on the allowed list.\n\n**What**\n\nWhen Claude Code sends usage metrics to Anthropic, each measurement carries attributes, extra details describing it. These attributes are now filtered down to an allowed list in two cases:\n\n- a \"hipaa\" policy is in effect for your organisation\n\n- your organisation's policy limits have not loaded yet, or checking them fails\n\nWhen filtering applies, measurements are grouped by the details that remain. Before, all attributes were sent.\n\n**Why**\n\nDetails that could identify someone are dropped for organisations under HIPAA rules, and by default until Claude Code knows which policy applies.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}