Live Feed/GitHub/Fact Record
GitHub logo
GitHub
feature 96% Confidence Gate October 12, 2026

Client telemetry user attribution and configurable capture

GitHub has introduced a new telemetry setting that allows enterprise administrators to attribute Copilot activity to specific users. This feature enables identity tracking without the collection of prompts, responses, or tool content.

Verified State Diff

Comparison Mode:
- Previous State
Enterprise administrators lacked a native mechanism to attribute specific Copilot activity to individual users within telemetry logs without potentially exposing prompt/response content.
+ Verified New State
Enterprise administrators can enable the 'telemetry.capture.identity' setting to attribute Copilot activity to specific users while explicitly excluding prompts, responses, and tool content from telemetry data.

Impact & Verification Analysis

WHO IS AFFECTED

GitHub Enterprise administrators and organizations using GitHub Copilot.

WHY IT MATTERS

It enables organizations to perform usage analysis and compliance auditing for AI tools while adhering to strict data privacy and security governance policies regarding code exposure.

Full Fact Overview

The introduction of the 'telemetry.capture.identity' setting provides a granular control mechanism for enterprise environments concerned with data privacy and compliance. By decoupling user identity from the actual content of the AI interaction (prompts and responses), GitHub is addressing enterprise requirements for auditability and usage tracking while maintaining strict data minimization policies. This architectural change allows organizations to monitor Copilot adoption and productivity metrics without exposing sensitive code snippets or proprietary logic to telemetry logs.

Multi-Source Evidence Chain (1)

Client telemetry user attribution and configurable captureGitHub
TRACKED ENTITY
Explore all historical GitHub changes
View GitHub Hub ➔