Teams running AI agents in production

Sell agent logs to AI, after checking the platforms your traces pass through

Subject
Ai agent software data terms
Date read
Basis
19 vendors' own documents, 20 read

An agent leaves a trail in every tool it touches: the observability platform that stores its traces, the agent builder that runs it and the model API that answers it. We read 20 documents from 19 of these vendors, newest on 2026-10-28: 6 write that they will not train on what you send them.

Source: Ai agent software data terms: every row, with its source

Tell us about the agent logs you keep

Your agents

What do your agents mostly do?

  • Each agent log enquiry is read by one person
  • Nobody on the platform board is told you wrote
  • Never paste a trace, a prompt or a key into this form

What happens next

  1. Say what your agents do, which platforms hold their traces and how long you have kept them.

  2. We check those platforms' clauses and the logging rules that apply to your agents.

  3. You hear back on which deal suits your traces: licensing them while the company operates; selling them as a closing company's records, which its directors can do only until a liquidator or administrator is appointed (a solvent members' liquidation included) and the office-holder then does, with one catch: a sale made after a winding-up petition is void if the company is then wound up, unless the court allows it (in a US case a bankruptcy trustee sells); or a route set with the adviser who referred you.

No agent platform, model provider or buyer has paid to be on this site or knows its pages were read, and no link here is an affiliate link. Each answer is our reading of a published page and is not legal advice on your own agreements. What we charge: if a company licenses its agent logs to a buyer we introduced, our fee is 12.5% of the deal when we act as its exclusive agent and about 10% when the logs go into a bundle or the pool, agreed in writing before anything is signed; anything a buyer pays us is credited to the company.

What each agent platform's terms say about your traces

Last updated

One row per agent builder, observability tool or model API, read from its terms, data controls or privacy page and linked to the page read. Not stated means that document did not answer the question.

What each agent platform's terms say about your traces
Agent platform or APIWho owns what you sendKeeps aggregated or de-identified dataTraining on your tracesExport window at exitSource
Adathe businessreservednot statednot statedAda Customer Terms of Use
Amazon Bedrocknot statednot statednot statednot statedAmazon Bedrock, data protection
Anthropic (API)not statednot statedwill not trainnot statedIs my data used for model training?
Arize AIthe businessreservednot statednot statedArize AI Terms of Service
Braintrustnot statednot statednot statednot statedBraintrust Terms of Service
Cognigythe businessreservednot statednot statedCognigy terms
CrewAInot statednot statednot statednot statedCrewAI Terms of Use
Cursornot statedreservedwill not trainnot statedCursor Privacy Policy
Galileonot statedreservedmay trainnot statedGalileo Terms of Service
Heliconenot statednot statednot statednot statedHelicone Terms of Service
Kore.aithe businessnot statednot statednot statedKore.ai Terms of Service
LangChain (LangSmith)the businessreservednot stated30 daysLangChain Terms of Service
Lindynot statednot statedwill not trainnot statedLindy Terms of Service
Microsoft (Azure AI Foundry)not statednot statedwill not trainnot statedAzure AI Foundry, data, privacy and security
OpenAI (API)the businessnot statedwill not trainnot statedData controls in the OpenAI platform
Replitnot statednot statednot statednot statedReplit Terms of Service
Vellumthe businessnot statednot statednot statedVellum Terms of Service
Weights & Biases (Weave)not statednot statednot statednot statedWeights & Biases master terms
Writernot statedreservedwill not trainnot statedWriter Terms of Use
Method and citation

Each vendor's own published terms were read through estate-fetch and stored whole (sha256 on every row). For every document, four questions were answered from the vendor's own words: who owns the business's data, vendor keeps aggregated or anonymised use, training AI on the business's data, export at exit. Every stated answer carries the sentence it rests on, checked against the stored text; 'not stated' means the document read does not address the question. A vendor with several documents reads 'varies' where they disagree. 19 vendors, 20 documents.

“What each agent platform's terms say about your traces”, Sell Agent Logs to AI, https://sellagentlogstoai.com/ (updated 2026-10-28).

Read next

Every figure sourced and dated.

The questions we get

Can a company sell the logs its AI agents produce?

It can license what it owns and is free to share. On this board 7 of 19 vendors say the data you send stays yours, but a trace also holds whatever your users and customers typed, so personal data has to come out before anyone licenses it.(Ai agent software data terms: every row, with its source)

Do model APIs train on our agents' prompts and completions?

The large ones we read say not by default. OpenAI's data controls say data sent to its API is not used to train its models unless you opt in, and Anthropic says it will not use inputs or outputs from its commercial products to train its models by default.(Ai agent software data terms: every row, with its source)

Does an observability tool keep a copy of our traces?

Some keep a version. Arize says it owns de-identified, aggregated or anonymised data derived from customer data, LangChain may disclose operational metadata externally only once it is aggregated or anonymised, and Galileo takes a right to use customer data to train its algorithms internally.(Ai agent software data terms: every row, with its source)

How long can I get my traces back after leaving LangSmith?

LangChain's terms let a customer export its data during the subscription or within thirty days after it ends, on written request and subject to the retention period it configured. Most other platforms we read state no export window, so pull the traces you want before you leave.(Ai agent software data terms: every row, with its source)

Does the EU AI Act make us keep agent logs?

For high-risk AI systems, from the dates the amended Act now sets: Article 19 makes providers keep the automatically generated logs for at least six months, and Article 26 asks the same of deployers, to the extent the logs are under their control and unless other law says otherwise. Regulation (EU) 2026/1744 moved those duties to 2 December 2027 for systems listed in Annex III and 2 August 2028 for those under Annex I.(Ai agent software data terms: every row, with its source)

Who takes agent traces and trajectories?

Magma says it packages an agent's interaction data for AI labs and pays a revenue share as it licenses; Ooak Data turns real company data into reinforcement learning environments for agents; OpenAI offers some organisations complimentary daily tokens for traffic they share with it.(Ai agent software data terms: every row, with its source)

Sources

This site's own datasets, every figure quoted from its source and dated:

  1. LangChain Terms of Service (LangSmith)
  2. Braintrust Terms of Service
  3. Helicone Terms of Service
  4. Arize AI Terms of Service
  5. Galileo Terms of Service
  6. Weights & Biases master terms (Weave)
  7. Vellum Terms of Service
  8. Lindy Terms of Service

The question this page is here to answer

Who takes a company's agent logs, traces and trajectories for AI training, what does each name, and through what door does an owner reach it?

6 of the 19 agent platforms we read write that they will not train on what you send. Tell us where your traces sit and we will write back about yours, as a licence, a closing company's sale, or an introduction through your adviser.

Answered by Sell Agent Logs to AI, which reads every enquiry this page takes.

Ask about my agent logs

Ask about my agent logs