Data & Privacy
Driver Data FAQ
Plain-language answers to how TruckerCloud handles driver data — what we collect, why we collect it, and how it's protected.
What driver data does TruckerCloud collect?
TruckerCloud pulls driver data from the fleet's telematics service provider (TSP) through their API. The fields available in our system include:
Typically populated
First Name, Last Name, ELD Driver ID, Status (active/deactivated)
Rarely populated
Middle Name, License Number, License State/Class/Expiry, Phone Number, Email, Address
In practice, the vast majority of driver records contain only the driver's name, their ELD driver ID, and their active/deactivated status. The remaining fields are part of the TSP's data schema but are rarely populated by the fleet or the provider.
How is driver data used?
Driver data serves three specific purposes within the TruckerCloud platform:
Driver-to-mileage association
The ELD driver ID is the link between a driver and their miles driven. Without this data, it is not possible to attribute mileage to individual drivers.
Safety event and collision reporting
Safety events (hard braking, speeding, etc.) and collision reports reference the driver involved. The driver endpoint provides the identity context needed for claims investigation and loss control analysis.
Vehicle assignments
Drivers are associated with specific vehicles through the TSP platform, enabling insurers to understand who is operating which assets and when.
How is driver data protected?
SOC 2 Compliance
TruckerCloud maintains SOC 2 compliance. Full details on our security posture, certifications, and policies can be made available at request.
Insurer isolation
Driver data is never shared across insurers. Each insurer only has access to data for fleets within their own program.
No external distribution
Driver data is not shared with any third parties outside of the insurer relationship.
De-identification requirement
If data is ever used outside of the direct insurer-fleet relationship (e.g., for aggregate analytics or research), it undergoes full de-identification and anonymization.
Consent-based sharing
Fleets explicitly authorize data sharing with their insurer during the TruckerCloud onboarding process. No data flows without fleet consent.
Can driver data collection be disabled?
Yes. TruckerCloud maintains per-insurer and per-fleet configuration controls. If a fleet or insurer requires that driver data not be collected, we can disable driver data calls for that fleet in our system. This is a simple configuration change on our end.
Questions? Reach out to support@truckercloud.com.