Privacy Policy

1Who we are and scope

T42 ELD is an electronic logging device (ELD) developed and operated by Trucking42, Inc. (“Trucking42”, “we”, “us”), 256 Atlantic Isle, Sunny Isles Beach, FL 33160, USA. The T42 ELD system includes the in-cab vehicle connection hardware, the T42 ELD driver app for Android and iOS, the fleet web portal and our cloud servers (together, the “Service”).

This policy applies to:

• Drivers who log in to T42 ELD to record hours of service;
• Motor carriers and their administrators, safety managers and dispatchers who manage drivers, vehicles and records in the fleet portal;
• Visitors to eldt42.trucking42.com and people who contact us or request early access.

Hours-of-service records are required by federal law. The Federal Motor Carrier Safety Administration (FMCSA) defines which data an ELD must record, who may see it and how long it must be kept. Where this policy describes what we must collect or keep, it follows those rules. Nothing in this policy limits a driver’s or a carrier’s obligations under 49 CFR Parts 390–399.

2Key points

• We record what the ELD rule requires. Date, time, location, engine hours, vehicle miles and driver, vehicle and carrier identification at every duty status change and every 60 minutes while driving (49 CFR 395.26).
• Location is deliberately imprecise. About a 1-mile radius for normal records and about a 10-mile radius during authorized personal conveyance.
• Original records are never altered. Edits are kept beside the original with a required note, and the driver must approve or reject any edit proposed by the carrier.
• Drivers see their own data. Each driver can view and obtain a copy of their own records at any time, without asking the carrier.
• We do not sell personal information and do not use ELD data for advertising.
• We share ELD records only with the driver’s motor carrier, with authorized safety officials, with service providers that run the Service for us, or when the law requires.
• Records are kept at least 6 months as required by 49 CFR 395.8(k) and 395.22(i).

3Information we collect

3.1 ELD records required by the FMCSA

For each driver, the T42 ELD records the following data elements automatically at each change of duty status, at each intermediate interval of 60 minutes while the vehicle is in motion, at engine power-up and shut-down, and at login and logout (49 CFR 395.26 and the Appendix to Subpart B, section 4.5):

The ELD also records: duty status (off duty, sleeper berth, driving, on-duty not driving) and special driving categories (authorized personal use and yard moves); the driver’s daily certification of records; malfunction and data diagnostic events; login and logout events; engine power-up and shut-down events; edits, edit requests and annotations; and data check values that confirm the records have not been altered.

3.2 Driver account information

To create a driver account, the motor carrier or its administrator enters the driver’s first and last name, ELD username, driver’s license number and issuing state, home terminal, time zone and contact details such as phone number and email. The license number and state are required by the ELD rule (Appendix, section 4.1.2) so that safety officials can identify the driver. They are stored securely and are shown only on the roadside display and in the ELD output file. Under 49 CFR 395.22(c)–(d), a driver’s license number or Social Security number may not be used as the username, and we do not collect Social Security numbers. A driver may have only one active account per carrier (Appendix, section 4.1.2(c)).

3.3 Carrier and fleet information

Company name, USDOT and MC numbers, home terminal addresses, administrator and support user accounts, vehicles (unit numbers, VINs, license plates), trailers and shipping document numbers, and billing contact details.

3.4 Vehicle and engine data

Through the vehicle’s diagnostic port the device reads engine synchronization data required by the ELD rule (engine power status, vehicle motion status, miles, engine hours and VIN). To support diagnostics and fleet features, the device may also read fuel level, odometer, speed and diagnostic trouble codes. Unassigned driving time, meaning driving recorded while no driver is logged in, is kept in an “unidentified driver” profile until the driver or the carrier assigns or annotates it.

3.5 App and device information

Phone or tablet model, operating system version, app version, ELD hardware serial number and firmware, Bluetooth pairing status, crash reports and service logs. We use these to keep the Service working, to detect malfunctions and to provide support.

3.6 Support, inspection and document data

Calls, emails, chat and WhatsApp messages with our 24/7 support line; roadside inspection reports and outcomes that a driver or carrier chooses to upload; and photos or documents (for example, bills of lading) uploaded in the app.

3.7 Billing information

Subscription plan, invoices and payment history. Card payments are handled by our payment processor; we do not store full card numbers.

3.8 Website and early-access requests

When you fill in the early-access form we collect your name, phone number, email (if given), fleet size and your message. Our web servers and analytics tools also collect standard technical data such as IP address, browser type, pages visited and referral source (see section 15).

4How we use information

• To record, store, display, certify and transfer records of duty status as required by 49 CFR Part 395.
• To calculate hours-of-service availability, violations and alerts for drivers and carriers.
• To transfer ELD records to authorized safety officials at the roadside or during audits and investigations.
• To detect, record and resolve ELD malfunctions and data diagnostic events (Appendix, section 4.6).
• To provide fleet features the carrier turns on, such as vehicle location, IFTA mileage by jurisdiction, DVIR and document storage.
• To provide 24/7 customer support, onboarding and training.
• To secure the Service, prevent fraud and investigate misuse, including attempts to alter records.
• To bill for the Service and keep business and tax records.
• To improve the Service using aggregated or de-identified data that does not identify a driver.
• To send service notices and, if you agree, product news. You can opt out of marketing at any time.
• To comply with law, court orders and FMCSA or state enforcement requests.

We do not use ELD records to build advertising profiles, and we do not sell ELD records or any other personal information.

5Location data

The ELD rule limits how precise recorded location can be, to protect drivers’ privacy:

• On-duty records and driving. Position is recorded to two decimal places of latitude and longitude, which is about a 1-mile radius (Appendix, section 4.3.1.6). The ELD records a valid position at least every 5 miles of driving.
• Authorized personal conveyance. While a driver is in personal-use status, location is recorded to one decimal place, which is about a 10-mile radius, and engine miles and engine hours are left blank in the records (49 CFR 395.26(d)(2); Appendix, sections 4.3.1.6(f) and 4.7.3).
• Roadside and output file. Safety officials see the same reduced-precision location and the nearest city and state.

If a motor carrier subscribes to optional real-time fleet tracking, the carrier can see more precise, live vehicle location for dispatching and safety. This feature is separate from the hours-of-service record, is shown only to the carrier’s authorized users and is not included in the ELD output file or sent to safety officials.

6Integrity of records and edits

• No alteration or erasure. T42 ELD does not allow anyone, including Trucking42 and the carrier, to change or delete original, automatically recorded data (Appendix, section 4.3.2.8; 49 CFR 395.30(f)).
• Edits keep the original. When a driver or carrier edits a record, the original stays in the system with the status “inactive-changed”, and the change is saved as a new record with the author, date and time (Appendix, section 4.4.4.2). Every edit requires an annotation explaining the reason.
• Driving time cannot be shortened. Automatically recorded driving time cannot be changed to non-driving time. Unassigned driving may be assigned to the correct driver or annotated.
• Driver approval. Edits proposed by the carrier are applied only after the driver confirms them, and the driver may reject them (49 CFR 395.30(d)). After an approved change the driver re-certifies the affected days.
• Daily certification. Drivers certify each 24-hour record as true and correct (49 CFR 395.30(b)).
• Data check values are calculated for each record and each output file so tampering can be detected (Appendix, section 4.4.5).

7Who we share information with

We share personal information only as follows:

• The driver’s motor carrier. ELD records belong to the carrier’s hours-of-service file. The carrier’s authorized users can see and manage the records of drivers who work for that carrier, according to the user roles the carrier sets (49 CFR 395.22(b)). A driver’s records are not shown to any other carrier. If a driver works for more than one carrier, each carrier sees only the records created under its own account.
• Authorized safety officials. FMCSA and state enforcement personnel, at the roadside and during compliance reviews, audits and investigations, as required by 49 CFR 395.8, 395.22(j) and 395.24 (see section 8).
• Service providers. Companies that host our servers, provide cloud storage and backups, send SMS and email notifications, process payments, provide customer support tools and run crash reporting. They act on our instructions, under written contracts that require them to protect the data and use it only to provide services to us.
• Integrations the carrier turns on. If the carrier connects T42 ELD to another system, such as a TMS, dispatch, payroll, fuel card or insurance program, we send the data the carrier selects to that system on the carrier’s instruction.
• Legal requirements. When required by law, subpoena, court order or other legal process, or when necessary to protect someone’s safety, prevent fraud or defend legal claims. Where the law allows, we tell the affected carrier or driver first.
• Business transfer. If Trucking42 is involved in a merger, acquisition or sale of assets, information may transfer to the new owner, which will remain bound by this policy and by the FMCSA retention rules.

We do not sell personal information, and we do not share it for cross-context behavioral advertising.

8Roadside inspections and data transfer

At a roadside inspection the driver can show the records on the app screen and send them to the official. T42 ELD supports the telematics transfer methods defined in the Appendix, section 4.9.1:

• Wireless web services: the output file is sent to FMCSA’s ELD web service over an authenticated, encrypted connection using our provider certificate.
• Email: the output file is sent to the FMCSA address as an encrypted and digitally signed (S/MIME) attachment, using FMCSA’s public key and our provider key.

The output file contains the information required by the Appendix, section 4.8.2, including the driver’s name, ELD username, license number and issuing state, the carrier, the vehicle, the ELD identifier and the records for the inspection period. We send it only to the destination specified by the FMCSA, using the routing code the official provides. Every transfer is logged.

The in-vehicle information packet (user manual, data transfer instruction sheet, malfunction instruction sheet and blank paper logs for 8 days) is described in our T42 ELD User Manual (49 CFR 395.22(h)).

9How long we keep information

When a carrier closes its account, we give the carrier the opportunity to export its records. We continue to keep the records that must be kept for the 6-month retention period and then delete or de-identify them. Records under a legal hold, investigation or litigation are kept until that matter ends. Under 49 CFR 395.22(i)(2), records are kept in a manner that protects the driver’s privacy.

10How we protect information

• Encryption in transit (TLS) between the device, the app, the portal and our servers; encryption of stored data and backups.
• Separate driver accounts with login authentication: a driver can access only their own records, and team drivers log in separately on the same device (Appendix, sections 4.1.3 and 4.1.4).
• Role-based access in the fleet portal, set by the carrier’s administrator.
• Restricted access for Trucking42 staff on a need-to-know basis, with access logging and confidentiality obligations.
• Backups kept on separate storage so records can be produced even if one system fails (49 CFR 395.22(i)(1)).
• Storage and transfer monitoring, with malfunction and data diagnostic events recorded and reported to the driver (Appendix, section 4.6).
• Our provider private key for FMCSA data transfer is protected and never shared.

No system is perfectly secure. If a security incident affects your personal information, we will notify affected carriers and drivers and authorities as required by applicable law. Please report suspected security issues to [email protected].

11Driver protection from harassment and coercion

Federal rules protect drivers from misuse of ELD data:

• Harassment is prohibited. A motor carrier may not use ELD information or other technology to harass a driver (49 CFR 390.36). Harassment means an action by the carrier, involving the ELD, that the carrier knew or should have known would result in the driver violating hours-of-service or driving while ill or fatigued (49 CFR 390.5 and 392.3).
• Coercion is prohibited. Carriers, shippers, receivers and transportation intermediaries may not coerce a driver to violate safety rules (49 CFR 390.6), and a carrier may not pressure a driver to falsify or change records (49 CFR 395.30(e)).
• Mute in sleeper berth. The T42 ELD app mutes or turns down audio while the driver is in sleeper berth status and does not send interrupting messages to the driver while in that status.
• Communication while driving. The app limits interactions on screen while the vehicle is in motion.

How to file a complaint. A driver who believes they were harassed or coerced may file a written, signed complaint with the FMCSA within 90 days of the event, through the National Consumer Complaint Database at nccdb.fmcsa.dot.gov or with the FMCSA Division Administrator for the state where the driver is employed (49 CFR 386.12(b)). The complaint should include the driver’s name, address and phone number, the carrier’s name and address, and a statement of the facts. On request, we will give a driver a copy of their own records to support a complaint.

Trucking42 does not retaliate against drivers who exercise these rights and will cooperate with FMCSA investigations.

12Roles of the carrier and the provider

The motor carrier is responsible under 49 CFR 395.8 for requiring drivers to use a registered ELD, for keeping records of duty status and supporting documents, and for producing them to safety officials. For ELD records and fleet data, Trucking42 processes information on behalf of the carrier and under the carrier’s instructions, as a service provider. Trucking42 is responsible for the ELD meeting the technical specifications, for keeping the systems secure and for this policy as it applies to our website, support and billing.

T42 ELD is in the FMCSA self-certification and registration process. Once registered, our ELD registration ID and identifier will be shown in the app, on our website and in the ELD output file, and our registration can be checked on the FMCSA list of registered ELDs. If the device is ever revoked by the FMCSA, we will notify carriers right away so they can replace it within the time allowed by the rule.

13Your rights and choices

Drivers

• See your records. You can view your records of duty status in the app at any time.
• Get a copy. You can obtain a copy of your own ELD records on demand, directly from the app or by asking us, without going through the carrier (Appendix, section 4.7.2).
• Correct mistakes. You can edit your records with an annotation, and you can approve or reject edits suggested by the carrier.
• Ask about your data. Ask us what information we hold about you and who we disclosed it to.

Carriers

• Export records and supporting data from the portal at any time.
• Manage users, roles and integrations, and choose a longer retention period.
• Close the account and request deletion after the required retention period.

Rights under US state privacy laws

Depending on where you live (for example, California, Colorado, Connecticut, Florida, Texas, Virginia and other states with consumer privacy laws), you may have the right to know and access the personal information we hold about you, to correct it, to delete it, to receive a portable copy, and to opt out of sale, sharing for targeted advertising and profiling. We do not sell or share personal information for targeted advertising, and we do not use it for profiling that has legal or similarly significant effects. Driver’s license numbers are treated as sensitive information and used only to meet the ELD rule.

Some requests are limited by law. For example, we cannot delete or change ELD records that must be kept under 49 CFR 395.8(k), and when we hold records on behalf of a carrier, we may direct your request to that carrier and help it respond.

How to make a request. Email [email protected] with the subject “Privacy request” or call +1 (305) 399-8553. We will verify your identity using information we already hold, and we answer within 45 days. You may use an authorized agent. If we decline your request, you may appeal by replying to our answer, and we will respond to the appeal within the time required by your state’s law. We will not discriminate against you for using these rights.

14Mobile app permissions

You can change permissions in your device settings. Turning off location or Bluetooth stops the ELD from recording correctly and will create a malfunction or data diagnostic event, so you may need to use paper logs as the ELD rule requires.

15Website, cookies and messages

This website uses cookies and similar technologies that are needed for it to work and, with your consent where required, to measure traffic. You can block or delete cookies in your browser settings. Our website does not respond to “Do Not Track” signals, but we honor Global Privacy Control signals as an opt-out where state law requires. See also the Trucking42 Privacy Cookie page.

If you give us your phone number, we may call or text you about your request and about the Service. Marketing texts are sent only with your consent; reply STOP to opt out. Message and data rates may apply. Service and safety messages related to your account cannot be turned off while you use the ELD.

Our website may link to other Trucking42 services and to third-party sites, such as FMCSA. Their own privacy policies apply there.

16Children

The Service is for commercial drivers and businesses. It is not directed to children under 16, and we do not knowingly collect personal information from them.

17Changes to this policy

We may update this policy when our Service or the law changes. We will post the new version on this page with a new “Last updated” date. If the changes are significant, we will notify carriers by email and drivers in the app before they take effect. Earlier versions are available on request.

18Contact us