When No Governed Record Exists to Produce

An analyst is a custodian on an active litigation hold. They use the firm's licensed AI workspace daily, under retention controls, with an export counsel can run. One afternoon they open the same site in a second browser profile, sign into a personal account, and work through a set of client files there.

‍

The corporate workspace holds no copy of that conversation. There is no administrative path to preserve it, collect it or produce it. The hold is in place, the custodian is working, and the record the hold was meant to capture does not exist anywhere the organization can reach.

‍

Is a Personal-Account Conversation Discoverable?

‍

Counsel will tell you that AI prompts and outputs are treated as electronically stored information like any other, and that the analysis turns on whether the material is within the organization's possession, custody or control rather than on which account produced it.

‍

The practical consequence is that lacking administrative access does not remove the duty. Where the conversation concerns the organization's business and is relevant to the matter, the obligation attaches and the absence of a collection mechanism is a problem to solve rather than an excuse. Whether a specific conversation falls inside a specific duty is a question for counsel, and the pattern is worth understanding before that question arrives.

‍

What Makes the Consumer Tier Worse Than Email?

‍

Two things. An in-place hold on an enterprise system prevents deletion without the user knowing or cooperating, and no equivalent exists for a personal account. Consumer tiers also frequently permit the user to delete history and may apply their own retention window, so the material can disappear through ordinary product behavior rather than through anyone's decision.

‍

How Would You Even Know?

‍

Detection is the part the legal analysis cannot answer, and it is the harder problem. The signal is an absence, and absences are invisible by default.

‍

Nothing fires when somebody works in a personal tenant. The corporate workspace does not report a missing conversation, because it has no way to know one should exist. The directory records the custodian as active and entitled. The network sees a session to an approved vendor. Every control reads the afternoon as ordinary, and it was ordinary except in the one respect that matters, which regulated data reaching these tools covers as a general problem.

‍

The Finding Is a Reconciliation

‍

Take the custodians on hold, take the hours each was visibly working, and ask whether the governed workspace holds a conversation attributable to them in that window. A custodian who was demonstrably at their desk and generated no governed record either did not use the tool or used it somewhere else, and the second possibility is the one worth checking. An AI Interaction Data Fabric performs that comparison because no single source holds both halves.

‍

Which Sources Does That Reconciliation Need?

‍

Three, and each contributes something the others cannot.

‍

• Directory State: Who is a custodian on an active hold, and whether their corporate access was working that day.
• The Workspace Compliance Interface: Whether any governed conversation exists attributable to that person in the relevant window.
• Session Observation: Whether a personal-tenant session occurred, from a browser agent or a network sensor that can resolve the account.

‍

The second is the source that establishes the negative, and it is frequently unavailable because the compliance export is a licensing tier or a configuration somebody has to enable. Enabling it produces records from that point forward and nothing retrospective, which makes it one of the cheaper things to arrange in advance, and producing evidence on somebody else's timeline is where the absence surfaces.

‍

Who Owns This Problem?

‍

Nobody cleanly, which is why it stays open. It is a records failure discovered through security telemetry, and those two functions rarely talk about the same thing.

‍

Counsel owns preservation and cannot see tenant-level session detail. Security owns the telemetry and is not usually told who is on hold. Records management owns retention policy and has no view of which tools people reach. Each position is reasonable and the union has a hole in it, which an obligation split across functions describes as a general pattern.

‍

What Is the Smallest Fix?

‍

A list of hold custodians reaching whoever watches AI activity, which is a feed rather than a project. Counsel already produces the list for other purposes, and routing it to the function that can observe sessions turns an invisible situation into a checkable one without changing anyone's responsibilities.

‍

What Should Change in the Hold Notice?

‍

The scope, because most notices were written before these tools existed and enumerate email, files and messaging.

‍

A notice naming AI assistants explicitly, and stating that work-related conversations in personal accounts fall within the preservation duty, puts the custodian on notice and creates a record that they were told. It does not prevent the situation and it changes what the organization can say afterward, which is the difference between an oversight and a documented instruction somebody did not follow.

‍

Does the Notice Need to Ask Them to Export?

‍

Frequently yes, since a personal account can only be collected with the individual's cooperation. Asking the custodian to export their own history and provide it is awkward, achievable and considerably better than discovering later that nobody asked. Where they decline or the material is already gone, the request itself is evidence of a reasonable effort.

‍

What If You Cannot Preserve It at All?

‍

Document the attempt, because good-faith effort is relevant to how a failure to preserve is treated and an undocumented attempt is indistinguishable from no attempt.

‍

A record showing when the hold was issued, that AI tools were named in scope, that the custodian was asked to preserve and export, that the corporate workspace was searched and found nothing, and that the consumer tier offered no administrative collection path is a materially different position from silence. Counsel will decide what it is worth. The security function's job is making sure it exists.

‍

Which Argues for Reconciling During the Hold Rather Than After

‍

A shortfall found while the matter is live can still be addressed, since the custodian is available and the material may not yet have aged out of a consumer retention window. The same shortfall found during production is a disclosure to make rather than a problem to fix, and the interval between those two states is measured in the weeks nobody was checking.

‍

Does This Only Apply to Litigation?

‍

No, and litigation is the version with the sharpest consequences rather than the widest reach. Any obligation requiring a record to be findable behaves the same way.

‍

A data subject access request has to reach conversations containing that person's information, and a personal tenant holds none the organization can search. Regulatory examinations request records of decisions and the reasoning behind them, which increasingly lives in AI conversations. Internal investigations depend on reconstructing what somebody knew and when. Retention schedules specifying how long business records are kept apply too, since they apply to material the organization cannot delete because it cannot reach it.

‍

Which of Those Is Most Likely to Arrive First?

‍

A subject access request, because they are routine rather than exceptional and the response window is short. An organization discovering during a thirty-day window that it cannot search the tenant where relevant conversations occurred has a disclosure to make about the limits of its search, and obligations already in force compound the pressure.

‍

Does the Same Reconciliation Work?

‍

Yes, and it is cheaper for these cases because the population is smaller. A subject access request names one person, so the comparison is whether governed records exist for that individual across the relevant period rather than across a custodian list. The mechanism is identical and the scope is narrower.

‍

What Can Be Established This Week?

‍

Four questions, and none requires a matter to be live.

‍

Whether the compliance export is enabled on your licensed AI workspaces, since it produces nothing retrospectively. Whether hold notices name AI tools in scope. Whether anyone receives the custodian list who can observe AI sessions. Finally, whether a personal-tenant session in a sanctioned tool is detectable in your environment at all, because where the answer is no, the reconciliation cannot run and the honest position is that the situation would go unnoticed. An AI data fabric closes the last one, and the first three are process changes available immediately.

‍

The Absence Is the Finding

‍

A hold custodian working in a personal tenant of a sanctioned tool produces material that may be discoverable and cannot be reached, and the lack of administrative access does not remove the duty. Nothing in the environment reports it, because the signal is a conversation that should exist in the governed workspace and does not. Establishing that requires joining who is on hold to whether a governed record exists for the hours they were working, which no single system can do. Kovrr's AI Security and Governance Platform resolves which tenant an AI session belonged to and joins it to identity, which is what turns an invisible absence into a checkable question.

‍

To see whether personal-tenant use of your sanctioned AI tools is detectable in your environment, book a demo mapped to your own estate.