Software companies
Fleet and telematics software vendors: what records you can license
By SourceX Editorial · Updated
Short answer
Telematics software vendors can usually license their own records, such as device and firmware engineering history, hardware failure analyses, support cases, integration issues and product decisions. Fleet-owned telemetry and driver personal data, including logs, location traces and camera footage, stay out without the fleet's agreement and careful preparation. Sort every record by owner before scoping.
Key takeaways
- Every telematics platform holds three classes of record: fleet-owned telemetry, driver personal data and vendor-owned records.
- Driver logs, location traces and dash cam footage are the most sensitive records and are generally excluded.
- FMCSA guidance expects carriers to store ELD records in a way that protects driver privacy, and fleets expect the same of their vendors.
- Retention settings decide how much fleet history exists, so the vendor's own systems are the dependable archive.
- Hardware failure analyses, firmware decisions and integration issues are the vendor records with the clearest rights.
Three owners inside one telematics platform#
A telematics platform holds records with three different owners: the fleet that operates the vehicles, the drivers whose activity the system records, and the vendor that builds and supports the product. Licensing questions get much easier once every record family is assigned to one of those three.
The sort below reflects common contract terms. Your own subscription agreement may differ, so treat it as a starting point for review rather than a conclusion.
| Record | Who controls it | Licensing outlook |
|---|---|---|
| GPS breadcrumbs and trip history | Fleet customer; reveals driver movements | Excluded without fleet agreement |
| Engine diagnostics and fault codes | Fleet customer | Excluded, or aggregate only with clear contract terms |
| Hours of service and ELD records | Carrier; personal data about drivers | Excluded |
| Dash cam video and safety events | Carrier; drivers' faces and voices | Excluded |
| Vehicle inspection reports | Carrier | Excluded unless the fleet agrees |
| Driver coaching notes and scorecards | Carrier; personal data about drivers | Excluded |
| Hardware failure analyses and returns | Vendor | Strong candidate |
| Firmware releases and rollback decisions | Vendor | Strong candidate |
| Installation and support tickets | Vendor, with fleet details inside | Candidate after preparation |
| Integration issues with TMS, fuel card and payroll systems | Vendor | Candidate |
Why driver data needs the most care#
Driver data needs the most care because it describes identifiable workers in detail: where they went, when they rested, how they braked and what the cab camera saw. Even when a fleet owns the account, the people in the records have their own interests and, in some states, their own legal rights.
Federal trucking rules shape expectations as well. FMCSA's ELD guidance says carriers must keep ELD records of duty status and back-up data for six months, hold the back-up on a separate device, and store the records in a way that protects driver privacy. Driver qualification files must be kept for as long as the carrier employs the driver and for three years after, so platforms hosting them hold some of a carrier's most sensitive records.
Camera products add another layer. Footage of faces, and any feature that analyzes driver attention or identity, can raise biometric privacy questions under state laws such as Illinois BIPA. Treat video and in-cab analytics as excluded unless counsel has reviewed a specific, narrow use.
Retention settings shape what history exists#
Retention settings decide how much fleet history exists at all, which is one more reason the vendor's own systems are the dependable archive. Regulatory periods are minimums, not limits: FMCSA requires carriers to keep records of duty status and supporting documents for six months, and fleets often choose their own windows inside the platform.
Once a fleet shortens retention, history can disappear for good. Samsara's help center, for example, says data outside a customer's chosen retention period is purged nightly and cannot be recovered by the customer or by Samsara. For a vendor, licensable history lives in engineering trackers, support systems and hardware databases it controls, not in tenant data it holds for fleets.
The vendor-owned records worth inventorying#
The vendor-owned records worth inventorying are those that show how experts diagnosed and fixed problems in devices, firmware and integrations. They connect a symptom to a decision and an outcome, which is what AI developers building maintenance and support agents look for.
Most of these records still mention fleets, vehicles or drivers. Preparation replaces fleet names, unit numbers, VINs and driver names with placeholders and removes location coordinates, while keeping the technical reasoning intact.
- Hardware failure analyses, return authorizations and root cause reports.
- Firmware release notes, staged rollout plans and rollback decisions.
- Installation and activation tickets, including wiring and harness troubleshooting.
- Integration issue histories with transportation management, fuel card, maintenance and payroll systems.
- Engineering work on regulatory logic, such as ELD rule updates, with test plans and code reviews.
- Platform incident postmortems and on-call notes.
- Product decisions on alerts, geofences and safety scoring features.
Contract language to check before scoping#
The contract language to check first is your subscription agreement's data clauses, followed by the agreements that bring other parties' rights into your platform. Telematics businesses often sit inside a web of hardware, vehicle maker and partner contracts, and each can restrict reuse.
Older agreements matter as much as current ones. If you changed hardware suppliers or acquired a competitor's customer base, records created under earlier contracts may carry different terms, so note the governing agreement for each era of your archive before deciding what is in scope.
| Agreement | What to look for |
|---|---|
| Fleet subscription agreement | Customer data definition, usage data clause, aggregated vehicle data rights and AI training language |
| Hardware supplier and contract manufacturer agreements | Ownership of failure data, test results and firmware components |
| OEM-embedded telematics agreements | Whether vehicle data from factory devices is licensed to you only to run the service |
| Insurance and partner data-sharing programs | Which fleet data flows to partners and under whose consent |
| Reseller and dealer agreements | Who holds the customer relationship and the related records |
Illustrative example: a telematics vendor for regional carriers#
Illustrative: a fictional vendor sells telematics devices, ELD software and dispatch tools to regional less-than-truckload carriers. Its records live in Jira, GitHub, a Zendesk support desk, a hardware returns database and a firmware release tracker.
The CEO starts with the three-owner sort. Trip history, ELD logs, inspection reports and all camera footage are excluded. The hardware returns database, firmware decisions, integration issues and Jira engineering history are classed as company records. Support tickets go into a preparation queue because many quote unit numbers and driver names.
The resulting candidate package centers on device failures and their fixes, which no public source documents in comparable detail. The company also adds a plain statement to its customer FAQ that fleet telemetry and driver data are never licensed, answering a question its sales team hears often.
How SourceX scopes telematics records#
SourceX scopes telematics records by owner in the Supply and Rights steps of the SourceX five-step transaction. Fleet telemetry and driver personal data are generally excluded, and the assessment focuses on the vendor's device, firmware, integration and support history, starting from a metadata-only fit check.
Packages that proceed go through Preparation to remove fleet, vehicle and driver identifiers, then vendor Approval and Delivery. Each package's SourceX Evidence Packet then shows where the records came from, the licensing rights relied on, the uses permitted, how privacy was handled and who authorized the release.
Frequently asked questions
Can we license anonymized GPS traces?
Usually not without the fleet's agreement, and often not even then. Location traces are hard to de-identify because start and end points reveal homes, depots and customer sites, and repeated routes identify drivers. Most vendors exclude raw traces and treat even aggregated movement data as a contract and counsel question.
Do fleets ask whether vendors train AI on their data?
Many do, especially larger carriers with procurement and legal teams. A clear written answer in your subscription terms, trust page or security questionnaire avoids confusion: say what customer data is used for, whether any of it trains your own features, and that fleet telemetry and driver data are not licensed to third parties.
Is dash cam video ever in scope?
Rarely. Video shows identifiable drivers and members of the public, may capture audio and can raise biometric questions. A narrow use, such as footage with faces and plates removed under explicit fleet agreement, would need careful legal review. Most vendors exclude video and work from their engineering and support records instead.
Do hardware suppliers have rights in our failure data?
Sometimes. Supply and manufacturing agreements can give the supplier rights in test results, defect reports or component firmware. Check those agreements before treating failure analyses as entirely yours, and remove supplier confidential information, such as proprietary schematics, from any records you scope.
What about data from OEM-embedded telematics devices?
Data from factory-installed devices usually reaches you under an agreement with the vehicle maker or a data aggregator, and those agreements often limit use to delivering your service to the fleet. Read them before assuming any vehicle data is yours, and expect most of it to stay out of any licensing scope.
Sources
- FMCSA's ELD FAQ states that motor carriers must retain ELD records of duty status and back-up data for six months, that the back-up copy must be maintained on a device separate from the one storing the original data (49 CFR 395.22(i)), and that carriers must store these records in a manner that protects driver privacy. Source
- 49 CFR 391.51(c) requires each driver qualification file to be retained for as long as the carrier employs the driver and for three years thereafter, while 391.51(d) allows certain items (such as annual MVR inquiries, annual review notes and medical examiner's certificates) to be removed three years after execution. Source
- Under 49 CFR 395.8(k)(1), a motor carrier must retain drivers' records of duty status and supporting documents at its principal place of business for six months from the date of receipt. Source
- Samsara says data outside the chosen retention period is purged every night at 12am UTC and, once deleted, is permanently removed from Samsara systems and cannot be recovered by the customer or Samsara. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.