EZ Logs Terms of Service

Effective date: October 9, 2026
Provider: EZ Logs ("EZ Logs", "we"). Contact us at the email addresses below.

1. Agreement

These Terms govern access to the EZ Logs service:

• the EZ Logs Android driver app
• the supported ELD vehicle device (currently the Pacific Track PT30)
• the carrier web portal
• the related APIs (together, the "Service")

They bind:

• the motor carrier that subscribes ("Carrier" or "you")
• each person who uses the Service under the Carrier's account: drivers, owners, administrators and support personnel ("Users")

By creating an account or using the Service, you agree to these Terms and to the Privacy Policy.

2. The Service and its regulatory status

2.1 ELD status. EZ Logs is built to the FMCSA ELD technical specification (49 CFR Part 395, Subpart B, Appendix A); FMCSA registration in progress. Until EZ Logs appears on FMCSA's list of registered ELDs, it is not a registered ELD, and 49 CFR 395.22(a) requires carriers to use only ELDs on that list to meet the ELD mandate. We will notify the Carrier when registration is complete.

2.2 Removal from the FMCSA list. After registration, if FMCSA removes EZ Logs from its list of registered ELDs (Appendix A §5.4), we will tell you promptly and work toward a fix or replacement. FMCSA guidance gives carriers a limited time to replace a revoked device. If we cannot restore the device to the list, the Carrier may terminate and receive a refund of any prepaid fees for the affected period.

2.3 Supported transfer method. The Service supports roadside data transfer by telematics: web services and email (App. A §4.9.1(b)(1)). Both need a working data connection and our servers.

2.4 Hardware. The Service supports the Pacific Track PT30 ELD device, which the Carrier obtains as agreed in its order. The Service needs a compatible Android phone or tablet. A portable ELD must be mounted in a fixed position during vehicle operation and be visible to the driver from the normal seated driving position (49 CFR 395.22(g)).

3. Carrier responsibilities

The Carrier remains responsible for its own compliance with the Federal Motor Carrier Safety Regulations, including:

a. Account management. Creating, updating and deactivating User accounts. Giving each User a unique ELD username. Making sure each driver account uses the driver's valid license number and accurate information. Making sure Users log in with their own credentials (49 CFR 395.22(b), (c), (e)). Sharing credentials is prohibited.

b. In-vehicle packet. Making sure every driver carries (49 CFR 395.22(h)):

• the Driver Instruction Sheet for data transfer
• the Malfunction Instruction Sheet
• blank graph-grid logs for at least 8 days

We provide templates of all three.

c. Malfunctions. Acting on driver malfunction notices and correcting malfunctions within 8 days, or asking FMCSA for an extension (49 CFR 395.34(d)). We will provide reasonable support, as described in section 6.

d. Record retention and production. Keeping ELD records for 6 months with a back-up copy on a separate device, and producing them to authorized safety officials when asked (49 CFR 395.8(k), 395.22(i)–(j)). The Service keeps data and back-ups as described in the Privacy Policy. The Carrier remains responsible for meeting these obligations, including after this agreement ends: see section 9.

e. Edits and harassment. Using edits and unidentified-driving assignments only as 49 CFR 395.30 and 395.32 allow. Not using the Service to harass or coerce drivers (49 CFR 390.36; 395.8(e)).

f. Lawful basis and notices. Giving drivers any notice required by law about the collection of their location and duty data. Getting any consent required by law.

g. Calibration and installation. Installing, calibrating and maintaining devices according to our specifications (49 CFR 395.22(f)).

4. User obligations and acceptable use

Users must not:

• tamper with the ELD. This includes disabling, jamming, reprogramming, spoofing or otherwise degrading recording or signals (49 CFR 395.8(e)(2)–(3)).
• make false entries, or access another User's account
• reverse engineer the Service, except as the law allows
• probe or overload the Service, or get around its rate limits or security controls
• use the Service for anything unlawful

We may suspend accounts that violate this section. Where we can, we will keep ELD records intact and keep the roadside display and transfer working for drivers.

5. Data

5.1 Ownership. As between the parties, the Carrier owns the ELD records and other data it or its Users submit ("Carrier Data"). Drivers keep their right to get copies of their own records (App. A §4.7.2).

5.2 Our use. We process Carrier Data only to provide, secure, support and improve the Service, and as required by law. We act as the Carrier's service provider under the CCPA (Cal. Civ. Code §1798.140(ag)). We will not:

• sell or share Carrier Data
• keep, use or disclose it for any purpose outside the business purposes in this agreement
• combine it with other data, except as the CCPA regulations allow

We may use aggregated, de-identified data that cannot reasonably identify any Carrier or person to operate and improve the Service.

5.3 Regulatory disclosures. The Carrier authorizes us to:

• transmit ELD output files to FMCSA when a driver starts a roadside transfer
• comply with lawful requests from FMCSA, State enforcement and courts

Where the law allows, we will tell the Carrier about a request it did not start.

5.4 Subprocessors. We use the subprocessors listed in the Privacy Policy: Amazon Web Services (hosting), Google Firebase Cloud Messaging (push notifications to the driver app) and OpenFreeMap (map tiles in the portal). We will give 30 days' notice of new subprocessors. The app contains place-name data from GeoNames (CC BY 4.0). That lookup runs on the device, and no data is sent to GeoNames.

5.5 Integrity of records. ELD records are append-only. They can be changed only through the regulated edit workflow, which keeps the originals (App. A §4.3.2.8, §4.4.4). We will not alter or delete records on request where that would break these requirements or a retention obligation.

5.6 Security. We maintain administrative, technical and physical safeguards as described in the Privacy Policy. We will notify the Carrier of a security breach affecting Carrier Data without undue delay, and within any period the law requires.

6. Support and availability

6.1 We will make commercially reasonable efforts to keep the Service available. We do not offer a numeric service level. The app records duty status offline, so logging, the on-device display and the output file do not depend on our servers. Roadside transfer and sync do need connectivity and our servers.

6.2 Support is provided by email at hello@ezlogs.co. We will help with malfunction diagnosis and replacement.

6.3 We may change the Service, including to keep it compliant with amended FMCSA rules. If a change materially reduces core ELD functionality, we will give reasonable notice.

7. Fees

Fees are charged per licensed vehicle seat, as shown in the order or in the portal's subscription page. Fees are billed monthly and are due within 30 days of the invoice. Seat changes are prorated as shown in the portal. If payment is late, we may restrict the Carrier's portal to read-only access after giving notice. We will not block drivers from recording, displaying or transferring records for an inspection. Taxes are the Carrier's responsibility, except taxes on our income.

8. Term and termination

Either party may terminate for convenience, effective at the end of the current billing month, by giving notice before that month ends. Either party may terminate for material breach that is not cured within 30 days of written notice. We may suspend the Service for misuse or security threats.

9. Effect of termination

For 60 days after termination we will give the Carrier an export of its ELD records in the FMCSA output-file format (App. A §4.8.2), together with the audit log. After that we will delete Carrier Data, except where the law requires us to keep it. The Carrier remains responsible for keeping ELD records for the full 6-month period required by 49 CFR 395.8(k), and DVIRs for 3 months (49 CFR 396.11(a)(4)).

10. Warranties and disclaimers

10.1 We warrant that the Service will materially conform to the technical specifications in Appendix A to Subpart B of Part 395. The Carrier's exclusive remedy for a breach of this warranty is repair, replacement or a refund of the fees paid for the affected period.

10.2 The Service does not replace the driver's and Carrier's own duty to comply with the hours-of-service rules. Hours-of-service clocks and violation alerts are aids only. They are based on the data recorded and on the rule settings the Carrier selects (for example the cycle, short-haul and adverse-conditions settings).

10.3 EXCEPT AS STATED IN THIS SECTION, THE SERVICE IS PROVIDED "AS IS". WE DISCLAIM ALL IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, TO THE EXTENT THE LAW ALLOWS.

11. Limitation of liability

11.1 Neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits or revenue, even if advised of their possibility.

11.2 Each party's total liability arising out of or relating to these Terms is limited to the fees paid by the Carrier for the Service in the 12 months before the event giving rise to the claim.

11.3 Civil penalties for hours-of-service violations remain the responsibility of the Carrier and its drivers, except to the extent caused by a defect in the Service.

12. Indemnities

12.1 We will defend the Carrier against third-party claims that the Service, as provided by us, infringes their intellectual property rights, and pay resulting damages finally awarded.

12.2 The Carrier will defend us against third-party claims arising from its or its Users' misuse of the Service, harassment or coercion of drivers, or violation of the Federal Motor Carrier Safety Regulations, and pay resulting damages finally awarded.

13. Third-party components and attributions

The Service includes open-source software, listed in the app under More > Settings > Licences and in the portal. It also includes data from GeoNames (www.geonames.org), licensed under CC BY 4.0: "Contains data from GeoNames (www.geonames.org), licensed under CC BY 4.0", modified as described in the notice. These components are subject to their own licenses.

14. General

• Governing law and venue. These Terms are governed by the laws of the State of Delaware, USA, without regard to its conflict-of-laws rules. The state and federal courts located in Delaware have exclusive jurisdiction over any dispute arising out of these Terms.
• Changes. We will give 30 days' notice of material changes to these Terms by email or in the portal. Continued use after that is acceptance.
• Assignment. Neither party may assign these Terms without the other's consent, except to a successor in a merger, acquisition or sale of substantially all of its assets.
• Notices. Notices to us must be sent to legal@ezlogs.co. Notices to the Carrier are sent to the account owner's email address.
• Force majeure. Neither party is liable for delays caused by events beyond its reasonable control.
• Entire agreement and severability. These Terms, any order and the Privacy Policy are the entire agreement on their subject. If any provision is unenforceable, the rest remain in effect.
• Export control. Each party will comply with applicable export laws.
• Contact. Contact us at the email addresses below: legal matters at legal@ezlogs.co, privacy at privacy@ezlogs.co, and support at hello@ezlogs.co.

Regulatory references (eCFR, current as of 2026-10-01): 49 CFR 390.36; 395.8(e), (k); 395.22; 395.30; 395.32; 395.34; Appendix A to Subpart B of Part 395, §§4.3.2.8, 4.4.4, 4.7.2, 4.8.2, 4.9.1, 5. Cal. Civ. Code §1798.140; 11 CCR §7051.