Data integrity statement

1Our commitments

• No overwrites. Original, automatically recorded events are kept in the record for its whole retention period. Edits are added next to them, never on top.
• Driver confirmation. A carrier can only propose a change. It takes effect only after the driver accepts it in the app, and the driver can reject it.
• Driving time is protected. Driving recorded from the engine cannot be shortened, deleted or turned into another status by anyone.
• Full audit log. Every login, edit, proposal, acceptance, rejection, assignment and export is logged with who, when and what changed.
• Trucking42 cannot edit logs. Our support staff can see records only to help you, and have no tool to change them.
• Officials see the history. The roadside display and the FMCSA output file include edits, their authors and annotations.

2Original records are never changed

The T42 ELD records duty status changes, engine power-up and shut-down, login and logout, hourly driving records, malfunctions and data diagnostic events, each with date, time, location, engine hours, vehicle miles and driver, vehicle and carrier identification (49 CFR 395.26).

Under the Appendix to Subpart B, section 4.3.2.8, the ELD must not allow anyone to alter or erase the original information it collects. In T42 ELD:

• an edited event keeps its original values, author and time, and its status changes to inactive – changed;
• the new version is saved as a separate event with status active, the editor’s user ID and a required annotation of at least 4 characters explaining why;
• a carrier proposal is stored as inactive – change requested until the driver decides, and a rejected one as inactive – change rejected (Appendix section 4.4.4.2);
• the record can always be viewed in its original form and in its edited form, side by side.

Under 49 CFR 395.30(f), a motor carrier may not alter or erase original data collected by the ELD or alter source data streams that feed the ELD.

3Every edit needs the driver

1. Proposal. A safety manager suggests a change in the fleet portal and must write the reason.
2. Notice. The driver sees the request on the bell and in Settings → Request list, with the original and the proposed version.
3. Decision. The driver taps Accept or Reject. Nothing changes until the driver accepts (49 CFR 395.30(d)).
4. Re-certify. If a certified day changed, the driver certifies it again: “I hereby certify that my data entries and my record of duty status for this 24-hour period are true and correct.” (49 CFR 395.30(b)).

Drivers can edit their own non-driving time and add notes, which are kept with the original in the same way. Under 49 CFR 395.30(e), no one may coerce a driver to make false entries or to accept a change.

4Admin audit log

Besides the edit history inside each log, T42 ELD keeps a separate audit log of everything users do in the fleet portal and in the app:

Audit entries cannot be edited or deleted by any user, including carrier administrators. The carrier can view and export its audit log in the portal under Settings → Audit log. It is kept for at least as long as the records it describes.

5Tamper detection

• Engine synchronization. Miles, engine hours, motion and power status come from the engine control module. If the connection is lost, the ELD records an engine synchronization diagnostic or malfunction (Appendix section 4.6).
• Data check values. Each event line and each output file carries a check value calculated as required by Appendix section 4.4.5, so changes to a record are detectable.
• Time and position checks. The ELD checks its clock against UTC and records timing and positioning compliance malfunctions when limits are exceeded.
• Disconnects are recorded. Unplugging the gateway or turning off Bluetooth does not stop the record: it creates diagnostic events that the driver, the carrier and the officer can see.
• Backups. Records are stored on our servers with a backup on a separate system, kept at least 6 months (49 CFR 395.22(i), 395.8(k)).

6Unidentified driving

If the truck moves while no driver is logged in, the driving is saved under an unidentified driver profile. It cannot be deleted. At the next login the driver is asked to accept the time that belongs to them. The carrier must review the rest and either assign it to the right driver, who must accept it, or annotate why it cannot be assigned (49 CFR 395.32).

7What a safety official sees

At the roadside, the driver can show the records on screen or send the ELD output file to FMCSA by web service or email. Both include, for the inspection period, the active records, the edited and inactive records with their status, the person who made each change and the annotation, plus malfunctions and data diagnostic events (Appendix section 4.8). An officer can therefore see what was originally recorded and every change made to it.

8Report a problem

If you think a record was changed without your consent, or you were pressured to change it, call our 24/7 line or write to us. We will review the audit log and give the driver a copy of their records. Drivers may also file a complaint with the FMCSA within 90 days at nccdb.fmcsa.dot.gov (49 CFR 386.12(b)).