Five ways in,
one record out.
People do not use AI in one place. A collector that watches a single surface produces a record with holes in it, and you cannot tell a gap in an audit ledger from suppressed evidence. Every collector below writes into the same chain and resolves to the same person.
Reads the prompt and the reply on ChatGPT, Claude, Gemini and Google AI Mode as they happen, along with every file dragged into the conversation and every artifact the model produces. Most unsanctioned AI use lives here. It needs no procurement and leaves no trace anywhere else.
Sits between your services and the model provider, recording the request and the response without changing how your code calls the API. Point a base URL at it and the traffic is governed; nothing else about the integration changes.
Records the code and context an engineer hands to an agent. This is often the most sensitive material in the building and the least likely to be reviewed. An agent that reads a private repository and sends it to a hosted model is a disclosure, whether or not anyone intended one.
Covers models running on your own hardware. Keeping inference in-house changes where the data goes. It does not change whether you have to account for it. A regulator asking what personal data was processed will not stop asking because the GPU was yours.
For AI use none of the above reaches: a vendor product, an internal pipeline, a batch job. Post events directly against a token scoped to the sources it may submit, so a leaked credential cannot fabricate events from a collector it was never meant to be.
A record about a device answers the wrong question.
Every collector sees different identifiers. A work email here, an OAuth subject there, a git address, a workspace member id. Evidarch resolves them to one person, so a review answers “what did this employee send to AI tools last quarter” across every surface at once. The alternative is five disconnected logs and somebody correlating them by hand under time pressure.
Only identifying signals merge two people
Email, OAuth subject, git email and workspace member id can link identities. Everything else, including a hostname, a device id or an IP, is context attached to the event. None of it is grounds for merging two people. Wrongly merging two employees in an audit record is a serious error, so the bar is deliberately high.
Where coverage genuinely stops.
Silence in an audit ledger is dangerous because it looks like compliance. These are the places Evidarch cannot see.
Personal devices
A phone you do not manage, on a network you do not run, is out of reach. Evidarch records the estate you control; it is not a surveillance net.
AI tools nobody deployed a collector for
A new assistant embedded in a SaaS product produces no events until it is covered — by the gateway, the compliance API, or a browser collector update.
A collector that stops reporting
Treated as a finding rather than an absence. The console raises a silent collector as a coverage gap, because a quiet source and a suppressed one look identical from outside.
Content typed but never sent
Capture happens on submission. A draft abandoned before sending was never an interaction with an AI system. Recording it would be monitoring for its own sake.
See what a week of real capture looks like.
Deploy against a single team before committing to an estate-wide rollout. Most organizations find the first surprise within days.