Thomson Reuters v. Ross: the first AI fair use ruling explained
Thomson Reuters v. Ross is a 2025 federal district court decision in which, as widely reported, fair use was rejected for copying a publisher's proprietary Westlaw content to build a competing AI tool. It is one fact-specific ruling, was headed to appeal, and does not settle AI training law.
What did the court decide in Thomson Reuters v. Ross?
In 2025 a US federal district court ruled on fair use in a dispute between Thomson Reuters, owner of the Westlaw legal research service, and Ross Intelligence, a legal-research company. As widely reported, the court rejected the fair use defense for the specific use at issue: copying editorial content from Westlaw to help build a competing AI research tool. The decision was then sent up for appeal, so its final weight depends on what the appeals court does.
Read it as one data point, not a rule for every AI training question. The tool at issue was not a generative chatbot, the material was a publisher's proprietary editorial work, and the use competed with the original product. This is general information, not legal, tax or financial advice. We have not verified the current appeal status or the final outcome, and this page cites no court document. Confirm the current status of the case in the court's own docket and opinion, and with your counsel, before relying on any summary, including this one.
Why does a legal research case matter to business-data partners?
It matters because the content was business content, not consumer media. Westlaw's value comes from editors summarizing and organizing legal material for paying professional customers. That is the same kind of asset a services firm, software company or data publisher builds over years: structured, curated, commercially valuable work product.
Three practical lessons carry over to the companies you might introduce:
- Proprietary business content has commercial value that courts take seriously when it is copied without permission.
- Whether a use harms the original owner's market is a central question, which is why a working licensing market helps owners. The guide on why a functioning licensing market matters in AI fair use cases covers that thread.
- Developers who want clean inputs have a reason to prefer permissioned material, which is the supply side of what enterprise AI data licensing deals look like.
How does the case apply in common partner conversations?
You are not giving legal advice, but you will hear these reactions from owners, CFOs and advisors. Use the table to know what to check and where to point them.
| Situation | What to check | Typical outcome to confirm with counsel |
|---|---|---|
| Owner says "AI companies will just take it anyway" | Whether the company's records are even publicly available; most internal email, tickets and CRM data are not | Internal records sit behind the company's own access controls, so use depends on a license |
| CFO asks if the ruling makes licensing safer | The ruling concerned one fact pattern; it is not a safe harbor for any buyer or seller | Licensing terms are still set by contract, not by the case |
| Advisor asks whether a company's content is protected | Who authored it, any client or third-party rights, and employee agreements | Ownership and licensing rights must be confirmed company by company |
| Founder worries about being the test case | Nothing is binding until the company agrees price and terms and signs | The company controls scope, exclusivity and term |
| Publisher or data vendor asks about its own product | Whether it licenses the same data elsewhere | Prior AI-training licenses can disqualify the same data |
What did the ruling not decide?
Several things stay open, and honest answers here build trust with your contacts:
- It did not set one rule for generative AI. Other courts are weighing different facts, and results may differ.
- It did not address internal business records such as email or support tickets, which are rarely public.
- It did not tell any company that licensing is required or that unlicensed use is always unlawful.
- It did not settle the appeal posture; later decisions may narrow, confirm or reverse it.
For the regulator's view of the broader training question, see the summary of the US Copyright Office report on generative AI training.
What does this mean for a referral partner?
Your job is not to interpret case law. It is to recognize a company with records it created, rights to license them and a sponsor who will talk. The case is useful as background when an owner asks why buyers pay for permissioned data at all.
AI developers, including the kind described in what is an AI lab, increasingly need real-work records to train and test agents, a point developed in the explainer on AI agent benchmarks and private business tasks. Rights-cleared records reduce the dispute risk buyers worry about, which is part of why chain of title matters in the process.
Why does ownership still come first?
Under 17 U.S.C. section 201, copyright vests initially in the author, an employer is the author of work made for hire, and exclusive rights can be transferred or licensed separately. In plain terms, a company can license specific rights in material it owns while keeping the rest. That is the structure a data license uses, and it is why the first screen for any company is whether it created the records and holds the rights, not what any court has said about someone else's content.
Anything created by clients, contractors without assignments or third parties needs separate consent. Raise that early, because it is the most common reason otherwise strong candidates stall.
What should you say if a contact asks about the case?
How are partner rewards connected?
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. The reward is a share of SourceX's fee and is never deducted from what the company receives. Licensed professionals, such as lawyers, should check their own rules on referral fees and disclosure before registering.
Questions to take to your own counsel
- Does the current status of the Thomson Reuters v. Ross appeal change how we describe fair use to clients?
- Which of our client's records could be subject to third-party or client rights?
- Do our employee and customer agreements permit licensing this material?
- How should exclusivity for AI training be scoped in the agreement?
Confirm with your own counsel before acting.
Next step
Run one candidate through the company fit checker, a preliminary, non-binding screen that needs no contact details, and read how the process works end to end. If the company looks right, register as a partner and make the introduction.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Was Thomson Reuters v. Ross a generative AI case?
As widely reported, the tool at issue was a legal research product, not a generative chatbot, and that difference is one reason lawyers caution against reading the ruling too broadly. Courts hearing generative AI cases look at different facts, so check current decisions with counsel before drawing conclusions.
Does the ruling mean companies must license their data?
No. A court decision about one use does not create a duty to license. Licensing is a voluntary contract between a company and a buyer. Companies decide whether to license, at what price and on which terms, and nothing is binding until they sign.
Is the case still on appeal?
It was reported as headed to appeal after the 2025 district court decision. Because the status can change, read the court's docket and recent legal commentary or ask counsel for the current position instead of relying on any summary page, including this one.
Does this case apply to internal email and support tickets?
The case involved a publisher's curated editorial content used to build a competing product. Internal records such as email, tickets and CRM data are different assets, mostly non-public. Their use by a buyer depends on a license and on the company's rights, not on that ruling.
Can a partner explain the case to prospects?
Partners can describe it briefly as background and should avoid legal conclusions. The safest framing is that it concerned one fact pattern and that the company's own counsel should advise on rights and risk before any agreement is signed.
Related pages
- Why a functioning licensing market matters in AI fair use cases
- Enterprise AI data licensing deals: what advisors should know beyond the headlines
- The US Copyright Office report on generative AI training, explained
- What is an AI lab? Frontier labs and model developers explained
- AI agent benchmarks explained: why labs want private business tasks
- Check Company Fit for Data Licensing
Free resources
- PDF bank statement to CSV converter — Turn Chase, Bank of America or Wells Fargo PDF statements into CSV, privately in your browser.
- Client data licensing eligibility checker — A transparent preliminary screen for one company.
- Enterprise value calculator — Enterprise value from equity value, debt and cash.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment