Employees selling work files to AI platforms: what employers should do

Why are employees selling work files to AI platforms?#

Employees sell work files to AI platforms because some platforms pay individuals for documents, conversations, code and examples of expert work. A support engineer may see an offer to upload resolved tickets, a project manager may be asked for real proposals, and a developer may be invited to share code with its review history.

Many employees do not see this as taking anything. The deck or the runbook feels like their own work, and a platform's sign-up flow rarely asks who owns it. The result is company records, sometimes with customer details inside, leaving through a channel nobody approved.

The pull is real. TechCrunch reported in October 2025 that Mercor's CEO described AI labs tapping former senior employees of investment banks, consulting firms and law firms because the firms themselves do not want to hand over data; Mercor says it tells contractors not to upload former employers' documents. Expert knowledge is in demand, and the line between what a person knows and what their employer's files contain is exactly where a policy needs to speak.

Treat this as a policy gap rather than a wave of bad actors. Most people stop once the rule is clear and a legitimate path exists.

Who owns the files an employee created at work?#

Files an employee created at work generally belong to the employer. Employment agreements, invention assignment terms and confidentiality agreements usually cover documents, code and records produced in the job, and copyright in work made within the scope of employment generally belongs to the employer.

Ownership is only part of the risk. Trade secret protection generally depends on the owner taking reasonable measures to keep information secret; DOJ guidance notes those measures need not be absolute and cites examples such as confidentiality agreements and need-to-know access. A company that knows uploads are happening and does nothing may weaken a later claim. Customer information in those files raises a separate problem: the upload can breach customer contracts and may trigger privacy obligations for the company.

Each case turns on the specific agreements and the laws that may apply, so involve counsel before acting on a particular situation.

What should the policy clause say?#

The policy clause should name the behavior plainly, cover paid and unpaid uploads, and apply during and after employment. Place it in the confidentiality or acceptable use policy and reference it from the data licensing policy, so all three point to the same rule.

• 1Scope: company records, work product, customer and vendor information, code and internal communications, in any form.
• 2Prohibited acts: uploading, selling, licensing, sharing or otherwise providing them to any AI platform, data marketplace, training-data program or model developer, paid or unpaid.
• 3Exception: only through the company's approved data licensing process, with written authorization.
• 4Duration: the obligation applies during employment and continues after it ends.
• 5Personal content: skills, general knowledge and material that contains no company or customer information remain the employee's own.
• 6Reporting: employees approached by such platforms about work materials tell a named contact.

A detection checklist for security and HR teams#

Detection relies mostly on signals companies already collect. The goal is to notice patterns early and respond proportionately, not to monitor every keystroke.

Check your monitoring notices before relying on any of these signals. Some states require employers to tell employees about electronic monitoring, and collective bargaining or employment agreements may add rules, so confirm with counsel that your acceptable use policy and notices cover the logs you plan to review.

What to do when you find an upload#

When you find an upload, act in a measured order: preserve, assess, contain, then fix the cause. A rushed accusation can create employment claims and does nothing to get the files back.

• 1Preserve the evidence: logs, alerts and any platform account details, without altering them.
• 2Bring in HR and counsel before contacting the employee.
• 3Identify what was uploaded and whether it includes customer, personal or trade secret information.
• 4Ask the platform to remove the material through its process for reports from rights holders, if it has one.
• 5Assess with counsel whether customer contracts or breach notification laws require you to notify anyone.
• 6Close the gap: update the policy, brief the team and adjust controls.

The company-controlled alternative#

The company-controlled alternative is to license records through the company itself, under a policy, with approvals and de-identification. That replaces an unmanaged leak with a governed process, and it protects the employees whose names, emails and notes appear in the records.

Explain the difference to employees directly. An individual upload sends raw work files, often with customer details, to an unknown party with no limits on use. A company license sends a prepared, de-identified package to a known buyer under written permitted use and deletion terms, after the company approves the release. The records are licensed, not sold, and the company keeps ownership.

Employees usually want to know whether their work will be used and whether they will be identifiable. A short notice or FAQ that answers those questions does more to stop side uploads than a warning alone.

Illustrative: a software company finds runbooks on a data platform#

Illustrative: the security team at a fictional B2B software company receives a DLP alert showing that a support engineer uploaded files to a site that pays for expert work samples. The files include internal runbooks, ticket macros and several exported Zendesk conversations containing customer names.

HR and the general counsel review the alert before speaking to the engineer, who explains that the platform said contributors could share their own work. The company asks the platform to remove the files, counsel reviews the customer contracts for notice duties, and the engineer closes the account.

The company then adds the policy clause, blocks the platform category at the web proxy and publishes an employee FAQ. Later, leadership runs a metadata-only fit check on its own support history to see whether a company license makes sense.

How SourceX approaches employee-created records#

In a SourceX transaction the supplier is the company that holds the records, acting through its authorized signer, not an individual employee. Within the SourceX five-step transaction, the Rights and Preparation steps review employee-created records and remove personal details before the supplier approves any release.

Each release is documented in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization, which gives the company a clear answer for employees and customers about what left and under which terms.