ERETH ELD
Get Started →
LEGAL & PRIVACY

Privacy Policy

We keep the original policy language and published update date available here.

Get Started →Talk to Our Team
ERETH ELD
FLEET · HOS · COMPLIANCE

Last updated: August 1, 2026  |  Applies to: ERETH ELD (Device ID: ERS238)  |  Operated by ERETH ELD

This page covers data collected by the ERETH ELD device and associated software. For ERETH ELD's full corporate privacy policy, visit eretheld.com/privacy.html.

1. Who We Are

ERETH ELD (FMCSA ELD Registration ID: ERS238) is an electronic logging device operated by ERETH ELD, located in Ohio. ERETH ELD is registered with FMCSA. Contact us at info@eretheld.com.

2. Data We Collect

2.1 Vehicle and Device Data

  • Vehicle Identification Number (VIN)
  • Engine data: odometer, engine hours, RPM, ignition on/off events
  • GPS location, speed, and heading — recorded continuously while the vehicle is in motion
  • Device identifier (Device ID: ERS238 hardware serial)
  • Malfunction and diagnostic event codes

2.2 Driver Data

  • Driver ID (assigned by carrier)
  • Hours of Service (HOS) logs — driving, on-duty, off-duty, sleeper berth status
  • Co-driver information when applicable
  • Driver certification records for data edits and transfers
  • Name and email address (for portal account)

2.3 Trip and Compliance Data

  • Electronic Records of Duty Status (RODS) as required by 49 CFR Part 395
  • DVIR (Driver Vehicle Inspection Reports)
  • IFTA mileage records by jurisdiction
  • DOT roadside inspection data transfers

3. How We Use Data

We use collected data for the following purposes:

  • FMCSA Compliance: Generating and storing ELD records as required by 49 CFR Part 395
  • Fleet Management: Providing carriers and fleet managers with HOS, location, and compliance dashboards
  • Safety and Alerts: Sending HOS violation warnings, geofence alerts, and maintenance reminders
  • Support and Troubleshooting: Diagnosing device and connectivity issues
  • DOT Inspections: Transferring ELD data to authorized enforcement officials upon request

4. Legal Basis and Regulatory Requirements

The collection and retention of ELD data is mandated by the FMCSA Electronic Logging Device Rule (49 CFR Part 395). Carriers are required to maintain ELD records for a minimum of 6 months. ERETH ELD processes this data in compliance with applicable federal motor carrier safety regulations.

5. Who We Share Data With

  • Carriers and Fleet Operators: Your motor carrier has access to all ELD data for vehicles and drivers in their fleet
  • FMCSA and DOT Enforcement: ELD records may be transferred to authorized enforcement officials during roadside inspections or audits
  • Cloud Infrastructure Providers: We use secure hosting providers to store and process data
  • No advertising networks or data brokers receive your personal data

6. Third-Party API Access (Highway API Integration)

ERETH ELD exposes a REST API at https://eretheld.com/admin-panel/api/v1 that authorized third-party platforms may use to retrieve carrier ELD data. When a carrier enables API access for a third party:

  • The third-party platform receives access to vehicle location, HOS status, driver records, and engine hours for that carrier's fleet
  • All API requests are authenticated via Bearer token and logged with timestamp, IP address, and endpoint
  • Third-party integrations are bound by the carrier's data agreement and may not retain ELD data beyond the purpose for which it was requested
  • Carriers may revoke API access at any time through the Admin Dashboard under Highway API Settings
  • ERETH ELD does not share API access logs with third parties except as required by law

7. Data Retention

ELD records are retained for a minimum of 6 months on the ELD device as required by 49 CFR 395.8(k), and an additional 6 months in cloud storage (12 months total). GPS and telematics data is retained for up to 12 months. Engine hours and odometer records are retained for the carrier subscription period plus 2 years. Account data is retained for the duration of your carrier agreement and 2 years thereafter. API access logs are retained for 12 months.

8. Security

All data is transmitted over encrypted connections (TLS 1.2+). Portal access is protected by authenticated sessions. ELD device communications are secured per FMCSA technical specifications for certified ELD systems.

9. Driver Rights

Under 49 CFR Part 395, drivers have the right to review their ELD records, request corrections, and annotate records. Drivers may contact their carrier administrator or ERETH ELD support to exercise these rights.

10. Contact

For privacy-related questions, data access requests, or to report a concern:

11. Changes to This Policy

We may update this policy to reflect changes in our services or regulatory requirements. The "Last updated" date at the top of this page indicates when it was last revised. Continued use of ERETH ELD following any changes constitutes acceptance of the updated policy.