ELD rule privacy protections: what carriers can and can't do with ELD data

What privacy protections does the ELD rule include?#

The ELD rule includes a small set of driver protections built into how records are made and used. They focus on the hours-of-service record itself and on how a carrier treats the driver, rather than on data ownership or commercial use.

Read the current regulation text with counsel for exact wording and any later amendments. This summary describes the structure of the protections, not their precise thresholds.

The coarse location design has a practical consequence. The certified hours-of-service record is a poor source of precise movement data, so requests for detailed routes almost always draw on the telematics stream, which these protections were not written for.

• 1Coarse location: the location stored with duty status changes is approximate, and less precise still when a driver uses the truck for personal conveyance.
• 2A harassment prohibition: carriers may not use ELD information to pressure a driver into violating hours-of-service or fatigue rules.
• 3A complaint route: drivers can report suspected harassment to FMCSA.
• 4Edit integrity: original entries are kept when records are edited, and carrier-proposed edits require the driver's confirmation.
• 5Driver access: drivers can review their own records of duty status.

What counts as harassment under the rule?#

Harassment under the ELD rule means a carrier using information available through the ELD, or technology tied to it, in a way the carrier knew or should have known would push a driver to violate hours-of-service limits or drive while too ill or fatigued to operate safely. The test turns on the effect on compliance and safety, not on whether monitoring happened.

Ordinary fleet management is not the target. Planning loads around remaining hours, coaching after a violation and reviewing logs during an audit all use ELD data. The line is crossed when the data becomes a lever, for example repeated messages during a sleeper berth period urging the driver back on the road.

A separate coercion rule reaches further, covering carriers, shippers, receivers and intermediaries who coerce drivers into violating safety rules. Carriers reviewing their practices usually look at both together.

A written dispatch policy helps show where the line sits. It should say when dispatchers may contact drivers in the sleeper berth or off duty, how available hours feed load planning and how drivers raise concerns, and message logs should be kept so the policy can be shown in practice.

What the ELD rule does not decide#

The ELD rule does not decide most commercial uses of the data. It is a safety and recordkeeping rule, so questions about sharing with insurers, customers or AI developers are settled by contracts, driver notices and other laws.

A fleet that treats the ELD rule as its whole privacy answer will miss the laws and contracts that actually govern these uses. The gap shows up most often when a sales team agrees to a customer tracking feed or an insurer program without legal review.

ELD records versus the rest of the telematics stream#

ELD records are a narrow slice of what a modern device collects. The hours-of-service record holds duty status, approximate location, engine hours, vehicle miles and edits, while the same hardware often captures precise GPS breadcrumbs, engine fault codes, driving events and camera video.

That distinction matters for every privacy question. Protections written for the hours-of-service record do not automatically extend to precise location trails or driver-facing video, and other laws may attach to those streams instead. Map which records come from the ELD function and which come from the broader telematics service before deciding any use.

The vendor contract usually covers both under one agreement, which hides the difference. Ask the vendor which export contains the certified hours-of-service record and which contains everything else, and keep the two apart in any review.

Which other laws and terms may apply#

Several other rules may apply to ELD and telematics data, and they are assessed deal by deal with counsel. The list below is where carrier counsel typically looks first.

Retention duties continue regardless of use. FMCSA's ELD guidance says carriers must keep ELD records of duty status and back-up data for six months, with the back-up on a device separate from the original (49 CFR 395.22(i)), and must store those records in a manner that protects driver privacy. Supporting documents, such as bills of lading, itineraries and expense receipts used to verify a driver's log, carry the same six-month duty under 49 CFR 395.8(k)(1). Six months is a minimum, and no sharing or licensing arrangement should touch those originals.

• 1State privacy laws that may cover employee and contractor data, including California's CCPA.
• 2State biometric privacy laws, such as Illinois BIPA, for driver-facing cameras that analyze faces.
• 3State electronic monitoring notice laws, and wiretap laws for in-cab audio.
• 4The Justice Department's bulk sensitive data rule, which may matter for precise geolocation data and certain foreign recipients.
• 5Telematics vendor agreements, owner-operator leases and any collective bargaining agreement.

Illustrative: carrier counsel reviews a request to reuse ELD data#

Illustrative: a fictional less-than-truckload carrier is asked whether its ELD and dispatch history could support AI development. Its general counsel starts by separating the hours-of-service records from the telematics vendor's GPS, fault code and camera data.

Counsel concludes that the hours-of-service records add little and carry driver identity throughout, so they stay out. The vendor agreement permits exports of dispatch-linked trip data, driver notices mention operational analytics, and drivers based in Illinois are flagged because the fleet uses driver-facing cameras. The proposed scope becomes dispatch decisions and exception notes, with location coarsened to the city level and no video.

The carrier also confirms that originals stay in its ELD system for the required retention period, untouched by the review.

How SourceX handles ELD and telematics records#

SourceX handles ELD and telematics records through the Rights and Preparation steps of the SourceX five-step transaction. The fit check collects metadata only, and any later scope usually centers on dispatch and exception records rather than the hours-of-service log.

The SourceX Evidence Packet documents the privacy record for each package, including how driver identifiers and location were treated and which jurisdictions counsel flagged, alongside the release authorization from the carrier.

Counsel stays involved at each step, and the carrier can stop a release at the Approval step if a jurisdictional question remains open.