Is it used for company work?
Answered without reading a single conversation. Coding is matched to company repositories (direct evidence); chat to company Projects, connectors and custom GPTs (a proxy). Anything without company context is unattributed, never "personal".
Work-linked coding activity, 30 days
82%
Sessions tied to the 14 allowlisted repositories
observedratioGitHub + Claude Code
Work-linked chat activity
41%
Sessions inside company Projects, connectors or custom GPTs
proxyratioClaude Projects, connectors, custom GPTs
Active seats with no company link
57
A list for enablement, not for sanction
partialcountAll connections
Attribution by tool, 30 days
share of active sessionsGitHub Copilotobservedrepo scope
78%
14%
Claude Codeobservedcommit trailers, PRs
91%
9%
Claude chatproxyProjects, connectors
46%
54%
ChatGPT Enterpriseproxycustom GPTs · CSV stale
31%
69%
■ Linked to a company artifact■ Unattributed, no company context▨ Not measurable with this access
Shares are per tool and are not combined. Copilot's hatched share is IDE chat with no repository open, which this access cannot attribute.
Signals used, and the one we refuse
| Signal | Tools | Evidence | Status |
|---|---|---|---|
| Activity inside company repositories | Copilot | observed | live |
| AI co-author trailers on commits in company repos | Claude Code, Copilot agent | observed | live |
| Sessions inside company Projects | Claude | proxy | live |
| Use of company connectors (Drive, Slack, Jira) | Claude, ChatGPT | proxy | split unconfirmed |
| Use of company-built custom GPTs | ChatGPT | proxy | CSV, stale |
| Conversation content via Compliance APIs | any | never collected | by design |
Time-of-day and weekend patterns are deliberately not used. They are weak evidence and they read as surveillance.