- Many automation contracts give you title to your machine data and give the vendor a perpetual license to train on it.
- The clauses that decide it: data ownership, training use, de-identified and derived data, model ownership, and what happens at exit.
- A model trained on your data stays with the vendor; published terms do not unwind it when the contract ends.
- A vendor's non-exclusive license does not stop you licensing your own records to an AI buyer, but an exclusive one can.
Can my automation or robot vendor use our factory's machine data to train AI without paying us?
Often, yes. Automation World put it plainly in October 2026: "your contract likely gives you the title to your operational data while the vendor earns the unrestricted right to train their models on your facilities". The table shows what published terms and rules say, read on 19 November 2026.
| Vendor or rule | Stated terms | Records covered | Date checked |
|---|---|---|---|
| Vention, Factory Data and AI Development Terms | Perpetual, worldwide, non-exclusive, royalty-free license, including to train AI models; you keep title | Machine states, trajectories, cycle times, faults, alarms, sensor data, images and video | Updated 5 Oct 2026; read 19 Nov 2026 |
| Vention, same terms | Vention owns de-identified data, derived data and the models; models are not altered at exit | Anything derived from your Factory Data | Read 19 Nov 2026 |
| Boston Dynamics, Spot Terms and Conditions of Sale | May retain robot technical data indefinitely; may use log data in perpetuity to improve products | Geometric, terrain and image data; performance and application data | Read 19 Nov 2026 |
| EU Data Act (Regulation (EU) 2023/2854) | A data holder cannot use non-personal product data without the user's agreement | Data from connected products, including industrial machinery | In application since 12 Sep 2025 |
| Formic and Tutor Intelligence (robot fleets) | The fleet operator generates training data from its own robots' work | Task and production data from customer sites | Oct and Nov 2026 |
Vention's terms are the clearest example we found. Section 2 reads: "You grant Vention and its Affiliates a perpetual, worldwide, non-exclusive, royalty-free right and license to access, collect, receive, transmit, host, store, reproduce, process, analyze and otherwise use Factory Data". The permitted purposes include "developing, training, fine-tuning, testing, validating, evaluating, benchmarking and improving artificial intelligence and machine-learning models" (Vention). Royalty-free means no payment for that use beyond the equipment or subscription.
Boston Dynamics' Spot terms say it "may retain indefinitely any Robot Technical Data provided by Customer", defined as data "such as geometric, terrain and image information required to perform perception-guided movement and manipulation and inspection tasks" (Spot terms of sale).
Who owns factory data: the plant or the vendor?
Usually both hold something, and the split is the point. The plant keeps title to the raw records. Vention's terms say: "As between the parties, You retain all right, title and interest, if any, in and to Your Factory Data". The vendor then owns what it makes from them. The same terms say "Vention owns all right, title and interest in and to De-identified Data", owns derived data such as features, labels and embeddings, and that models trained on the data "are and will remain exclusively owned by Vention", usable "including for the benefit of other customers".
Automation World describes the same pattern across published robotics terms: "The customer keeps title to raw data and facility specifics. The vendor takes a perpetual, royalty-free license to operational telemetry through improvements and aggregated-data clauses." It adds that a no-train promise, where one exists, "is often scoped to personal data rather than operational data, derived data or customer artifacts".
Some robot companies now treat their own fleets as the data source. Formic "says its fleet has logged more than 750,000 hours of live production" (TNW), and Tutor Intelligence says "Every task the robots complete generates the real-world experience data that has been missing from the training equation" (press release). When the robot does the work at your site, the training value of that work goes to whoever the contract says.
Which clauses decide whether a vendor can train AI on our data?
Read the master agreement and every document it pulls in by reference: data terms, AI terms, privacy addenda and the order form. The training right often sits in a separate data or AI addendum, not in the main contract.
| Clause | What to look for | Example from published terms |
|---|---|---|
| Data ownership | Who holds title to raw machine data, images and logs | Vention: you keep title to Factory Data |
| Training use | Whether the license covers training shared or general models, not just running your system | Vention: training AI, robotics, foundation and world models |
| Aggregated or de-identified data | Whether the vendor owns data once it is stripped of your name | Vention owns de-identified data |
| Derived data and models | Who owns features, labels, site-specific models and fine-tunes | Vention owns derived data and all models |
| Commercial information | A promise not to infer your volumes, methods or economics | Vention: no customer-specific commercially sensitive information |
| Exit and deletion | What stops at termination, what is deleted, what survives | Vention: training on data that identifies you stops within 90 days; models stay |
| Retention | How long the vendor keeps raw data | Spot terms: robot technical data retained indefinitely |
Automation World suggests a contract allocate four things separately: "(1) source data; (2) training rights; (3) site-specific models and site memory; and (4) the runtime rights required to use those artifacts after termination". It also notes that "the hardest-fought clause is rarely data ownership. It is pool membership": whether your production data may train the model every other customer uses.
What can a plant negotiate before it signs an automation contract?
Large buyers already negotiate these terms; smaller plants often sign the standard paper. The points below are the ones most worth raising, in rough order of value.
Before you raise any of them, ask the vendor for a plain list of what its equipment and software send off site: which signals, how often, whether cameras record, and where the data is stored. Many plants find out for the first time that a cell camera or a cloud connector has been uploading images and fault data for years. That list tells you which records are already in the vendor's hands, which are still only yours, and which clauses matter most for your site. Ask the same question at every renewal, because data and AI addenda change more often than the master agreement.
- A consent gate on training: the vendor may use data to run and support your system, and needs written consent to train shared models.
- A priced training license: Automation World reports that "Some drafts now gesture at the honest resolution: a priced data license for training rights." If the vendor wants your data for its models, it can pay for it or discount the contract.
- Pool exclusion: your data does not train models offered to named competitors or to your sector.
- Site models: you own or keep a license to run site-specific models, configurations and fine-tunes after exit.
- Deletion at exit: raw data returned and deleted on a set date, with a certificate.
- A narrow definition of de-identified data, so that stripping your name does not hand over your process know-how.
- Audit: the right to ask what data was used and for which models.
The same questions apply to software that runs your shop floor: see vendor AI agent logs for the export and ownership side, and the MES guide for what an MES records.
Our customers own the part designs we machine. Can we still license CAM programs and production records for AI?
Sometimes, and only the parts you own. The geometry of a customer's part usually belongs to the customer, and purchase orders often extend that to tooling, programs and process data made for the part. Your own records about how the shop works, such as machine utilization, setup times, maintenance and scrap rates, are usually yours. Programs written for a customer's part sit in between and depend on the contract.
Buyers check this. One CNC parts buyer requires "You must have the right to license every part", and a Cad Crowd buyer says "You must own the projects or have permission to sell and share them." Customer permission in writing settles it; silence does not. The contract manufacturer guide and the machine shop guide go through purchase-order terms clause by clause.
What does the EU Data Act change for plant machine data?
This page is general information, not legal advice. The EU Data Act "applies since 12 September 2025" (EU Data Act explainer). It lets users of connected products, including "industrial or agricultural machinery", access the data they generate. The EU's own summary of the key rule: "the data holder cannot use any non-personal data generated by the product without the user’s agreement". In plain terms, a machine maker selling into the EU needs a contract with the plant before it uses the plant's machine data, and that contract is where the training right is granted or refused.
The Act reaches raw and pre-processed data, not everything a vendor builds from it. Automation World notes that "Recital 15 excludes information derived through proprietary complex algorithms" unless otherwise agreed. So the Act gives a plant access to its data and a say in its use, but the model layer stays a matter of contract. Vention's terms reflect this: section 12 preserves Data Act rights that "cannot lawfully be waived, excluded or restricted".
Outside the EU there is no general statute that gives a plant rights over machine data; the contract decides. Rules vary by country, so take advice on yours.
Before you license your own data, keep the rights
A vendor's non-exclusive license does not stop you licensing the same records to an AI buyer. Vention's license, for example, is "non-exclusive". An exclusive grant, or a clause that gives the vendor all derived and aggregated data, can. Check every automation, MES and CMMS contract before you sign a data license, because a buyer will ask whether anyone else holds rights in the records. For what buyers pay for plant records, see manufacturing data buyers.
We help you license your data. Origin is an independent data partner. Your company decides what is shared and signs any license itself. See what your factory data is worth.
Origin Data Partners works with companies that own data and helps get it bought. We are independent of the services on this page, and a buyer may pay us when a deal closes (how Origin is paid). See what your data is worth.
Common questions
What should a plant check in its own contracts before licensing shop floor data to an AI company?
Read four sets of paper: customer contracts and purchase orders (who owns part designs and derived data), NDAs, automation and software vendor terms (whether a vendor already holds a training or exclusive license), and export rules for defense or dual-use parts. List which records each contract touches. Only records that no contract restricts are ready to license, and counsel should review the list.
Can a factory license MES and production data that its software vendor also stores?
Usually yes. A vendor that hosts your MES or keeps a copy under a non-exclusive license does not own your production records, and storing them gives it no right to stop you licensing them. Check three things first: that you can export the data under the contract, that no clause grants the vendor exclusive rights, and that your license to an AI buyer does not breach confidentiality owed to the vendor.
Is maintenance history like work orders and alarm logs from our machines valuable to AI companies?
It can be. Mercor's manufacturing listing accepts "machine alarm logs and process data" or "work orders with inspection reports" as qualifying records, with several years of history. Value rises when each alarm links to the work order, the asset, the parts and the fix. If an automation vendor already trains on those logs under a royalty-free license, you may be giving away for nothing what a buyer would pay for.
I am the M&A adviser to a family-owned manufacturer selling the business. Do vendor data clauses limit licensing production records before or after the sale?
They can. A vendor license that survives a change of control keeps running for the new owner, and an exclusive or derived-data clause may already cover the records a buyer would license. In diligence, list every automation, MES and CMMS contract with a data or AI clause, and note what survives termination. A license to an AI buyer signed before closing needs the acquirer's agreement.
Our automation vendor offered a discount if we let it train on our data. Is that a fair trade?
It is at least an honest one: the vendor is pricing the training right instead of taking it in the boilerplate. To judge it, compare the discount with what your records could earn if licensed to an AI buyer, and check what the vendor gets beyond training: ownership of models and derived data, use for other customers, and how long the right lasts. A discount for a short, non-exclusive right is better than for a perpetual one.
Does de-identified or aggregated factory data still carry our process know-how?
Often it does. Removing your company name does not remove how your machines run: trajectories, cycle times, fault patterns and setups still describe your process. Vention's terms, for example, let it own de-identified data and still use "operational patterns, machine behaviors" and similar technical learnings in general models. If process know-how matters to you, narrow the definition of de-identified data in the contract.
Does a vendor have to delete models trained on our data when the contract ends?
Not under the published terms we read. Vention stops training new models on data that identifies you within 90 days of termination, but termination "will not require Vention to delete, destroy, retrain, modify, reverse engineer or otherwise alter any Model previously developed". Automation World notes that removing one site's data generally means retraining without it. Negotiate training limits before signing, not deletion after.
Sources and further reading
- Vention: Factory Data and AI Development Terms (updated 5 Oct 2026)
- Boston Dynamics: Spot Terms and Conditions of Sale (PDF)
- Automation World: Who Owns What Robots Learn? (7 Oct 2026)
- European Commission: Data Act explained
- TNW: Formic raises $50M for general-purpose factory robots (23 Oct 2026)
- Yahoo Finance (press release): Tutor Intelligence raises $75 million Series B (2 Nov 2026)
- Mercor: manufacturing and industrial company listing (data API, read 19 Nov 2026)
