Who owns telematics and ELD data: fleet, vendor or driver?

Who owns telematics and ELD data?#

Telematics and ELD data rarely has a single owner; rights are split among the fleet, the telematics vendor and, in practice, the drivers whose work and movements the data records. The vendor agreement usually decides the commercial rights, privacy law and employment terms shape what can be done with driver-related data, and federal motor carrier rules govern how ELD records are kept and produced.

For most fleets, asking who owns the data is less useful than asking who may use which data for what purpose. A fleet can hold clear rights to export its location history and still be limited in how it may use that history outside its own operations.

Ownership at a glance#

Ownership positions differ by data type. The table shows common starting positions; your vendor agreement, driver agreements and counsel's review decide the actual ones.

What to read in your telematics agreement#

The telematics agreement is where most answers sit, whether the platform is Samsara, Motive, Geotab or another provider. Pull the master subscription terms, your signed quote or order, and any separate data processing or AI terms, then read them as one document; note each version date, since online terms change.

Customer contracts are the other document to pull. Location trails reveal shipper facilities, delivery windows and lane volumes, and some shipper and broker agreements treat that information as confidential. A fleet may control its GPS history under the vendor terms and still owe a customer confidentiality over what the trail shows.

• 1The definition of customer data, and whether it covers derived data such as safety scores.
• 2The license the fleet grants the vendor, including aggregated, de-identified and AI development uses.
• 3Any limit on the fleet's own use, such as internal business purposes only.
• 4Export rights, formats and deadlines, including after termination.
• 5Retention settings for video and location history, and deletion at termination.
• 6Subprocessors and where data is stored.
• 7Restrictions on using the service's outputs to build or train competing products.

Why an internal business purposes clause matters#

An internal business purposes clause matters because it can limit what a fleet does with data even when the fleet controls it. Some platform terms permit customers to use the service and its outputs only for their own internal operations, and a license to a third party may fall outside that permission.

Depending on the wording, the clause may reach what the service produces, such as reports, scores and processed outputs, while raw data the fleet supplied is treated differently. Counsel should read the exact language, and some fleets ask the vendor for a written clarification or amendment before any licensing discussion.

Keep dated copies of each version of the terms you accepted, alongside any exports made under them. Counsel can then tell which terms governed the data when it was produced, which matters most for fleets that have changed plans or vendors.

Where drivers come in#

Drivers come into telematics ownership through privacy, not title. Location history, hours-of-service logs and in-cab video are tied to identifiable people, and company drivers, owner-operators and team drivers may each sit under different notices and agreements.

Company drivers usually received policies or notices about monitoring when they were hired, and the scope of those notices matters for any new use. Owner-operators may own their equipment and, under their lease agreements, sometimes their own ELD or telematics accounts. State privacy and biometric laws, such as the Illinois Biometric Information Privacy Act for facial analysis features, may apply depending on where drivers work and what the system captures; counsel assesses which laws apply deal by deal.

ELD records and regulators#

ELD records exist mainly for hours-of-service compliance, and federal motor carrier rules govern how they are kept, for how long and how they are produced to enforcement officers. Those rules set compliance duties, and federal rules also protect drivers against harassment, including harassment that uses ELD information. On their own, the rules do not grant the fleet a right to license the records; most other limits come from contracts and privacy law.

In practice, hours-of-service logs are among the most identity-bound records a fleet holds. A cautious licensing scope either excludes them or reduce them to de-identified duty-status patterns, and FMCSA requirements and any open audits are reviewed with counsel first.

Illustrative: a fleet's counsel reads two vendor contracts#

Illustrative: a fictional dry van fleet switched telematics vendors some years ago and still holds exported history from the old platform. Its general counsel reviews both agreements before the company decides whether any telematics-derived records belong in a licensed package.

The old vendor's terms let the fleet export raw location and engine data with no use limit after termination, but defined safety scores as vendor output. The new vendor's terms limit outputs to internal business purposes and reserve the vendor's right to use de-identified data for product development. Counsel advises keeping the old raw history in scope, with location coarsened and driver identities removed, excluding all video, and asking the new vendor for written clarification before anything from the current platform is considered.

How SourceX handles telematics records#

For telematics-derived records, most of the SourceX work happens at the Rights stage of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Vendor terms, driver notices, owner-operator leases and customer contracts are mapped before any preparation starts, and the resulting licensing rights and permitted use are recorded in the SourceX Evidence Packet alongside the privacy record.

The fleet approves the final scope, and SourceX does not assume a right the contracts do not show. Coarsened location, removed driver identities and excluded video are typical starting points for any telematics-derived package.