Rights and contracts
Who owns telematics and connected equipment data?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Who owns telematics data is decided mainly by the contract with your telematics, equipment or leasing provider, not by who owns the trucks or machines. Agreements commonly leave the fleet in control of its own records while the provider keeps rights to aggregated data. Check three clauses: the data definition, the provider's usage rights and export on termination.
Key takeaways
- Owning a truck, trailer or forklift does not by itself make you the owner of the data its devices generate.
- The contract's definition of customer data decides whether GPS history, ELD logs, fault codes and video count as yours.
- Providers commonly reserve rights to use aggregated or de-identified data drawn from all their customers.
- Driver location and camera footage raise privacy and employment questions even when the fleet controls the records.
- A fleet can license only what it can export, so confirm export routes before any contract ends.
What decides who owns telematics data?#
Telematics data ownership is decided by contract: the master agreement, order form, terms of service and any data processing addendum you accepted from each provider. Property law says little about raw sensor readings, so in practice the party that holds contractual rights and practical access controls the data.
Most fleets have more than one of those contracts. A single tractor can carry an aftermarket device from a provider such as Samsara, Motive or Geotab, embedded telematics from the truck manufacturer, a trailer tracker, a reefer monitor and a dashcam. A warehouse adds connected forklifts and dock equipment, each reporting to an OEM or dealer portal. Every source needs its own answer.
| Data source | Contract that usually governs it | What to watch for |
|---|---|---|
| ELD and hours-of-service logs | Telematics provider terms, alongside federal recordkeeping duties | Driver access rights and how long logs stay exportable |
| GPS location and trip history | Telematics master agreement and order form | Provider rights to aggregated location data |
| Engine fault codes and diagnostics | OEM telematics terms or aftermarket device terms | Manufacturer limits on access and reuse |
| Road-facing and driver-facing video | Dashcam or safety platform terms | Biometric, consent and retention questions |
| Forklift, reefer and equipment hours | OEM portal, dealer or lessor agreement | Lessor or dealer claims to usage data |
| Fuel and toll transactions | Fuel card and toll account terms | Issuer restrictions on reusing transaction detail |
The three clauses to check in a provider contract#
The three clauses that answer most ownership questions are the data definition, the provider's usage license and the export and termination terms. Read them together, because a generous ownership clause means little if the export clause gives you no practical way to get the records out.
- Data definition and ownership: what counts as customer data, and whether it covers raw readings, video, derived outputs such as driver safety scores, and records the provider's software generates about your fleet.
- Provider usage license: what the provider may do with your data beyond running the service, including improving its products, training its own models and creating aggregated or de-identified datasets it owns or shares.
- Export, retention and termination: available formats and APIs, how long data stays accessible after the contract ends, and when it is deleted.
Can a fleet license its telematics data for AI or mapping?#
A fleet can often license telematics data that its contract defines as customer data and that it can export, but API terms and acceptable use policies may still restrict how exported data is used. Some prohibit using exports to build a competing product or to train models. The provider's own benchmarks and fleet-wide aggregates are not yours to license.
Telematics on its own is machine-generated and often reproducible from other fleets, which limits its value under the SourceX Enterprise Data Value Framework drivers of uniqueness and human-generated signal. The records AI developers find more useful link telematics to human decisions: the dispatcher's note on a late load, the reroute after a closure, the maintenance call after a fault code, the customer conversation about a missed window.
Mapping and routing uses raise one more question. Road speeds, dwell times at docks and stop sequences can reveal customer operations and shipper volumes even with names removed, so check shipper contracts for confidentiality language that covers shipment patterns, not only shipment documents.
What to do before a telematics contract renews or ends#
A renewal or termination is the moment a fleet has the most leverage over telematics data terms and the most to lose if it does nothing. Once an account closes, history that was never exported may be gone, and a provider has little reason to negotiate after the relationship ends.
- List every active device and portal account, including OEM, trailer, reefer, dashcam and forklift systems.
- Confirm who holds each account: the operating company, a parent, a lessor or a former owner.
- Request a full historical export in a documented format and test that it opens and joins to dispatch records.
- Ask the provider to narrow its usage license, for example by excluding model training on identifiable fleet data.
- Record the export date, format and contract version so the provenance can be shown later.
Where driver privacy limits what you can share#
Driver privacy limits telematics licensing because location tracks and camera footage reveal where people live, when they stop and what they look like. Several state privacy laws may treat precise geolocation and biometric information as sensitive, and some states have employee monitoring notice rules. Collective bargaining agreements sometimes restrict how telematics data may be used.
Coverage of driver data also differs by state, because drivers are usually employees or contractors rather than consumers. The Colorado Attorney General, for example, states that the Colorado Privacy Act does not cover people acting in an employment context or data kept for employment records, while California's law can reach employee data. Counsel should map where drivers are based before deciding what may be licensed.
Customer locations need care too. Delivery stops identify consignees, and shipper contracts may treat shipment details as confidential. The safer approach is to decide preparation by record type before anything is exported.
| Record | Privacy concern | Common preparation |
|---|---|---|
| Trip history | Reveals driver homes and personal stops | Trim trip ends, coarsen locations, remove driver IDs |
| ELD logs | Ties hours and duty status to named drivers | Replace driver identifiers with stable pseudonyms |
| Driver-facing video | Faces and in-cab behavior | Usually excluded from licensed scope |
| Stop and delivery data | Identifies customers and consignees | Generalize addresses, remove customer names |
| Safety events | Links incidents to individual drivers | Aggregate or pseudonymize, review against union terms |
Illustrative example: a distributor with trucks and connected forklifts#
Illustrative: a fictional industrial distributor runs a private delivery fleet with an aftermarket telematics platform, uses OEM portals for engine data and leases electric forklifts that report hours and fault codes to the dealer. Orders, routes and exceptions live in NetSuite and a separate routing tool. Before an AI developer conversation, the COO checks the three clauses for each provider.
The telematics contract defines GPS history, ELD logs and fault codes as customer data but treats safety scores as provider output. The forklift lease gives the dealer rights to usage data, so forklift records are left out. The distributor licenses delivery exceptions linked to route history and dispatcher notes, with driver identifiers replaced, trip ends trimmed and customer names removed. Video is excluded entirely.
How SourceX approaches telematics records#
SourceX treats each telematics and equipment source as its own line in the Supply step of the SourceX five-step transaction, then reads the governing provider terms in the Rights step before any export. Preparation removes driver and customer identifiers according to the record type.
The SourceX Evidence Packet records which contract governs each source, what was excluded and why, and the release authorization. Large telematics archives stay in the fleet's own storage or ship on encrypted drives; SourceX does not host multi-terabyte datasets.
Frequently asked questions
Do federal ELD rules decide who owns ELD records?
No. Federal hours-of-service rules focus on recording, retaining and producing driving records for safety enforcement. They do not decide whether a carrier or its provider may reuse those records commercially. That question is answered by the provider contract and by privacy and employment law, which counsel should assess.
Can our telematics provider sell or share our data?
A provider can use your data only as its contract allows. Many agreements permit aggregated or de-identified use across customers, and some allow product improvement or model training. Read the usage license, ask the provider to confirm its practices in writing and negotiate narrower terms at renewal if needed.
What about owner-operators leased onto our authority?
Owner-operator data needs separate attention. The lease agreement, who holds the device account and what the operator was told all matter. Many carriers carve owner-operator trucks out of a license or obtain written permission first, because the operator may have a stronger claim to records from equipment it owns.
Does leasing trucks or equipment change the answer?
It can. Full-service lease and rental agreements sometimes include telematics supplied by the lessor, with data terms the lessee never read closely. Check whether the lessor claims ownership or reuse rights before treating those records as yours, and ask for written confirmation if the agreement is silent on usage data.
Is raw GPS data valuable to AI developers on its own?
Usually less than fleets expect. Location pings are plentiful and similar across fleets, and buyers can often source comparable data elsewhere. Value rises when telematics connects to the decisions around it: dispatch changes, exception handling, maintenance outcomes and the customer communication that explains why a load ran late.
Sources
- The Colorado Privacy Act does not cover personal data of individuals acting in a commercial or employment context and does not apply to data maintained for employment records purposes. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.