Who owns equipment data: the OEM, the dealer or the fleet operator?

Contracts, not one US statute, mainly decide who owns equipment data. OEM telematics terms often govern data that connected machines send to the manufacturer, while dealers, rental companies and fleet operators generally hold their own work orders, technician notes, parts and maintenance records, subject to dealer agreements, customer terms and privacy promises.

The short answer: contracts decide, one layer at a time

No single US statute that we rely on settles who owns equipment data, and state law varies. It depends on the agreements around each machine: the OEM's telematics or connected-services terms, the dealer agreement between the OEM and its dealers, rental and lease contracts, and service contracts with customers. Privacy law adds limits wherever the data can identify a person, such as an operator's location history.

The working pattern for an operating partner: data an OEM's connected platform collects is often governed by the OEM's terms, while dealers, rental companies and fleet operators generally hold their own work orders, technician notes, parts history and maintenance logs as ordinary business records. Those records can be licensable, subject to confidentiality commitments and to any restrictions in dealer or customer agreements.

What the rules actually say

Three sources of rules shape the answer.

  • Contract. Whatever the purchase, rental, telematics and dealer agreements say about data ownership, permitted use and confidentiality usually controls. Read them first.
  • Promises to customers. FTC staff have stated that a company's promises not to use customer data for undisclosed purposes, such as training or updating models, are enforceable whether they appear in privacy policies, terms of service, promotional material or marketplaces. That post is staff guidance rather than a rule, but a dealer portal's privacy page belongs in the review.
  • Privacy statutes. Where telematics ties location or behavior to an identifiable operator, state privacy law can apply. California's CCPA statute text requires notice at collection of the categories of personal information and the purposes, and requires a written agreement limiting use when a business sells or shares personal information or discloses it to a service provider or contractor.

Right-to-repair laws and agreements deal with who can get the diagnostic tools, parts and information needed to fix equipment. They are not designed to settle who may license records for AI training, they vary by state, and they are changing, so check the current position with counsel.

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

Five layers of equipment data

Splitting the data into layers makes the ownership question manageable.

LayerExamplesWho often controls itWhat to check
Machine-generated telematicsEngine hours, fault codes, GPS, fuel burn, idle timeOEM or telematics provider, under platform termsData access and use clauses; whether the customer can export raw data
Dealer service recordsWork orders, technician notes, diagnostics performed, parts usedDealer, as its own business recordsDealer agreement confidentiality; customer service terms
Warranty claimsClaims submitted to the OEM, approvals, rejections, chargebacksShared: the dealer prepares them, the OEM decides under its programWarranty program manual and dealer agreement
Operator recordsMaintenance logs, inspections, utilization, downtimeFleet operator or rental companyCustomer contracts and notices to operators or employees
OEM technical contentService manuals, diagnostic software, parts catalogsOEM, under copyright and software licensesExclude from scope

Dealer work orders often follow a complaint, cause and correction structure, which is exactly the problem-diagnosis-fix sequence AI developers want to see. That is why the dealer and operator layers, not raw telematics, are usually where a license starts.

How the rules apply in common partner situations

SituationWhat to checkTypical outcome to confirm with counsel
Dealer group wants to license years of service historyDealer agreements for data and confidentiality clauses; customer service termsWork orders and technician notes may be licensable once customer details are removed
Rental company with telematics across its fleetTelematics subscription terms; rental agreements; operator noticesIts own utilization and maintenance records may qualify; OEM platform data may not
Contractor that uses an OEM portal for its own machinesPortal terms on export and useIts own maintenance logs and job records are its own; portal-only data depends on the terms
Independent service company repairing customers' equipmentService contracts with customersService notes are usually the company's records, subject to customer confidentiality
Dealer holding years of warranty claim filesOEM warranty program rulesWhether the OEM restricts outside use of claim submissions

Warranty records get their own treatment in warranty claims records as AI training data. The operator side is covered in fleet maintenance records, and dealer fit signals in equipment dealer data.

Disclosure and consent good practice

Before a portfolio company scopes a license, its team should:

  • Read customer-facing privacy pages and portal terms as they stood when the records were created, not only the current version.
  • Avoid relying on a quiet terms update to cover past records.
  • Give the OEM notice if the dealer agreement requires it for any outside use of data.
  • Remove customer names, operator identities and precise locations unless counsel confirms they can stay.
  • Keep OEM manuals, diagnostic software output and parts catalogs out of scope.

The data inventory builder helps the company list each system and its history as metadata, so counsel can review the contracts behind each one.

Questions to ask your counsel

  1. Which of our agreements address data ownership, use or confidentiality, and which are silent?
  2. Does our dealer agreement require OEM consent or notice before we license service records?
  3. Do our telematics or maintenance records identify operators or drivers, and which privacy laws apply to them?
  4. What did our customer terms and privacy notices promise about data use during each period?
  5. Can we license our own records while excluding everything that came from an OEM platform?

Where this leaves an operating partner

Equipment dealers, rental platforms, field service businesses and fleet-heavy contractors in a portfolio often hold the dealer and operator layers in depth. The operating partner page has wider portfolio screens. Franchise systems pose the same contract-first question for franchisors and franchisees, covered in franchise data ownership.

Next step

When a portfolio dealer, rental or service company meets who qualifies and counsel is comfortable with the contract picture, register as a partner and introduce the CEO. SourceX handles qualification, the inventory, terms and buyer review, and the partner never handles the records.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Does buying a machine mean the buyer owns its telematics data?

Not automatically. Owning the machine and controlling the data its connected systems send to an OEM platform are separate questions, answered by the telematics or connected-services terms the buyer accepted. Some terms give owners access and export rights, others limit them. The buyer's own maintenance logs, inspections and job records are a different matter and are generally its own.

Can a dealer license warranty claims it submitted to the OEM?

Possibly, but check the warranty program manual and dealer agreement first. The dealer prepares each claim from its own work order, so the underlying service record is usually the dealer's, while the OEM's approval decisions and program rules may be treated as OEM confidential information. Counsel should confirm which parts can be licensed and whether the OEM must be notified.

Are fault codes and sensor readings personal information?

On their own they describe a machine, not a person. They can become personal information when linked to an identifiable operator or driver, for example through login records, shift assignments or location history. That link is what brings privacy law into play, so the safer approach is to remove or generalize operator identities and precise locations during de-identification.

What if the OEM changed its terms after the data was collected?

A later change does not necessarily reach records collected under earlier terms, and regulators have cautioned against quiet, retroactive changes that expand data use. Keep copies of the terms in force during each period. Where terms changed partway through the history, counsel can advise whether records from different periods need different treatment or should be left out of scope.

Does right to repair give a dealer or operator the right to license OEM data?

Generally not. Right-to-repair rules and agreements focus on access to the diagnostic tools, parts and information needed to fix equipment, not on licensing OEM data or technical content to third parties for AI training. The rules vary by state and are changing, so confirm the current position with counsel before relying on any repair-access right.

Free resources

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