Field-level encryption, what is collected and why, and who can see it — written for the person running a security review rather than for a brochure.
| Data type | Purpose | Shared with 3rd parties? | Encrypted in transit? |
|---|---|---|---|
| Personal info (name, email, phone) | Account management, compliance tracking | No | Yes |
| Sensitive info (SSN, DOB, address) | FMCSA regulatory compliance (49 CFR 391) | Only with authorized compliance partners (MVR / Clearinghouse), if configured | Yes |
| ID documents (CDL, medical card) | Qualification verification | No | Yes |
| Device & app activity | App stability & crash reporting | No | Yes |
Permissions requested on-device: Camera (document scanning), Biometrics (secure administrative login) and Storage (saving generated PDFs locally). Data is owned by the organization that creates it — DPS does not sell or share it for marketing purposes. Full detail is in the Privacy Policy and SMS Consent pages.
Happy to walk your safety or IT team through the encryption model and data flow directly.
Talk to Us