{"version":"2.1.293","anchor":"event-logging-batch-requests-get-redacted-before-sending-via","canonical_anchor":"event-logging-batch-requests-get-redacted-before-sending-via","heading":"Batches of logged events are redacted before they are sent","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/event-logging-batch-requests-get-redacted-before-sending-via","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Batches of logged events are redacted before they are sent\n\nRequests that send batches of logged events are now cleaned of sensitive content first, and refused if their contents cannot be read as events\n\n**Unclear.** It is not clear what decides when this check applies, so it may not cover every way Claude Code sends analytics.\n\n**What**\n\nClaude Code now recognises network requests that send a batch of logged events. These are the usage reports it sends for analytics. Before such a request goes out, Claude Code reads its contents as a list of events and redacts it, meaning it removes or masks sensitive parts. If the contents are not a valid list of events, the request is refused with an error saying it cannot be redacted.\n\nThe check runs again each time the request is redirected to another address, so a redirect cannot get around it.\n\n**Why**\n\nThis changes what analytics data can leave your computer this way. Event data sent through this route is cleaned first, and anything that cannot be cleaned is not sent at all.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}