Reefer downloads and trailer telematics: who owns the temperature data?

Short answer: who owns reefer temperature data?#

Reefer temperature data is controlled record by record, not as one dataset. A refrigerated carrier usually controls the downloads from its reefer units and the history in its telematics account. A shipper controls the temperature instructions on its bills of lading and any portable loggers it places with the product. A telematics vendor holds copies under terms the carrier accepted.

Contracts rarely use the word ownership. What matters is who may access, retain, share and reuse each record, and those rights sit in carrier-shipper agreements, broker-carrier agreements, rate confirmations and telematics subscriptions.

Which temperature records exist on a refrigerated load#

Temperature records on a refrigerated load come from several devices and documents, and claims specialists treat them as a set. A complete file usually includes the records below.

Each record has a different origin. That is why one claim can involve three parties producing files that disagree, and why reuse rights have to be sorted one record type at a time.

• 1Reefer unit microprocessor download: setpoint, return air and discharge air temperatures, defrost cycles, alarms, run mode and fuel events.
• 2Trailer telematics stream: remote temperature readings, door open and close events, location and unit status.
• 3Shipper or receiver loggers: portable devices placed in the load and read by the shipper or receiver.
• 4Loading and receiving checks: pre-cool confirmation, pulp temperatures and seal numbers.
• 5Bill of lading and rate confirmation: the temperature instruction, run mode and any continuous-run requirement.
• 6Driver messages and logs: notes about stops, delays and unit problems, often tied to the driver's identity.

Who holds each record, and which terms govern reuse#

Each temperature record has a holder and a governing document. The table reflects common practice; the agreements on a given lane control.

What telematics vendor terms usually decide#

Telematics vendor terms usually decide three things that matter in practice: how long history is retained, whether the carrier can export it in a usable form, and what rights the vendor takes in aggregated or de-identified data. Read the customer data, aggregate data and termination sections of the subscription.

Retention settings deserve attention because deletion can be permanent. Samsara's help center, for example, describes customizable retention settings for DVIR, camera, Hours of Service and safety data, and says data outside the chosen retention period is purged nightly and cannot be recovered by the customer or Samsara. Check how your own vendor handles temperature and sensor history before changing any setting.

Before switching vendors or replacing units, export the temperature history you may need for claims, audits or later analysis, and confirm in writing what the old vendor keeps.

Shipper and broker contracts#

Shipper and broker contracts often give the other side a right to temperature records about its loads. Many broker-carrier agreements require the carrier to provide reefer downloads on request or when a claim is filed, and some shippers ask for continuous visibility through a feed from the carrier's telematics account.

A right to receive data about a load is not the same as owning the carrier's history. Still, confidentiality terms may restrict how the carrier uses shipper-identifying details such as product, consignee and lane, and those details should come out before temperature history is used outside the business.

Food shippers, loaders, carriers and receivers covered by the FDA sanitary transportation rule under FSMA may have their own temperature and record-keeping responsibilities. Which ones apply depends on each party's role and written agreements, so check with counsel and the shipper's food safety team.

Driver privacy and location data#

Driver privacy matters because temperature history rarely travels alone. Telematics records pair readings with GPS position, timestamps and often a driver login, which together show where a named driver was at a given time.

Federal guidance already ties some of these records to privacy. FMCSA's ELD guidance says carriers must retain ELD records of duty status and back-up data for six months and store them in a manner that protects driver privacy. State employee monitoring laws may also apply. The table shows typical treatment before outside use.

Illustrative: a refrigerated carrier sorts its temperature records#

Illustrative: a fictional regional refrigerated carrier hauls produce and dairy for shippers and brokers. Its reefer units report through a trailer telematics platform, its tractors run a separate ELD and video system, and its claims team stores unit downloads and receiver logger reports in a shared drive by load number.

Planning a switch of trailer telematics vendors, the safety director learns that the old platform would delete stored temperature history after cancellation. The team exports the full history first, then reviews its broker agreements and finds that most require downloads only on request or with a claim.

Later the carrier considers licensing temperature and door-event history to AI developers working on cold chain monitoring. Shipper names, products, consignees and driver identities are removed, locations are generalized to regions, and claim files containing receiver logger data are left out.

Can a fleet license its temperature history?#

A fleet can often license temperature and equipment history it controls, once shipper details and driver identities are removed and vendor terms permit export. Unit downloads, alarm sequences, defrost behavior and door events, linked to claim outcomes, show how cold chain problems develop and get resolved.

SourceX runs that review through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery, with the carrier approving each step. Large telemetry archives stay in the carrier's own storage or ship on encrypted drives, because SourceX never hosts multi-TB datasets, and a SourceX Evidence Packet records which shipper and driver fields were removed and who authorized release.