Privacy
Privacy policy
What TruDOT collects, why we collect it, who helps us process it, and what you can ask us to do with it.
Effective September 11, 2026 · Last updated October 18, 2026
1.Who we are and what this covers
Umapachi LLC (TruDOT) provides DOT/FMCSA compliance recordkeeping software to motor carriers. This policy covers trudot.app, the TruDOT application, and the text messages we send and receive. It does not cover your carrier’s own privacy practices or any third-party site we link to.
2.Customers and drivers
Our customer is the motor carrier. The carrier decides which drivers, vehicles and documents go into TruDOT, and it is responsible for the information it enters — including obtaining a driver’s consent before entering a mobile number for text alerts. For that information, we act on the carrier’s instructions.
If you are a driverand want to see, correct or remove information in your file, start with your carrier’s office — they control the record. You can also reach us at privacy@trudot.app and we will route the request to them.
3.What we collect
- Account information. Name, work email address, role, and either a hashed password or the verified email from your Google sign-in.
- Carrier profile. Legal and DBA name, USDOT and MC numbers, addresses, and filing and insurance dates.
- Driver and vehicle records. Driver name, mobile number, SMS consent status, CDL number, state, class and endorsements, medical certificate and query dates, employment status; vehicle unit number, VIN, plate, and inspection and maintenance dates.
- Documents you send us.Files uploaded, emailed or texted in — medical examiner’s certificates, CDLs, MVRs, inspection reports, drug and alcohol program records and similar. These commonly contain sensitive personal information, which is why we treat every document as confidential to the carrier that owns it.
- Messages. The content and attachments of texts sent to our number, the sending number, and delivery status of texts we send.
- Technical information. Server and security logs, and a single httpOnly session cookie that keeps you signed in for seven days. We do not use advertising or cross-site tracking cookies.
4.How we use it
- Run the service: file documents into the right CFR slot, calculate deadlines, score completeness, and build audit packets.
- Send alerts: email to the carrier's office and, with consent, text reminders to drivers.
- Classify and extract dates from documents you send in, so they file themselves.
- Support, troubleshooting, security monitoring and abuse prevention.
- Billing and account administration.
- Meeting our legal obligations and enforcing our terms.
We do not sell personal information, and we do not use your documents or driver data to advertise to you or anyone else.
5.Text messages and mobile opt-in
Mobile numbers are used to send the compliance reminders described in our SMS terms & consent page and to match documents texted in to the right driver.
Mobile opt-in is never shared
No mobile information will be sold or shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are excluded from all of the information-sharing categories described below; this information is not shared with any third parties.
6.AI processing of documents
When AI intake is enabled for a carrier, the document image or text is sent to Anthropic’s API to be classified and to have its dates and names extracted. Anthropic processes that content to return the result and, under its commercial terms, does not use it to train its models. A person at your carrier reviews anything the system is not confident about. When AI intake is not enabled, classification runs locally and no document leaves our infrastructure.
8.How long we keep it
Compliance records exist to be produced in an audit, so we keep them for as long as the carrier’s account is active, and afterwards for the retention periods the carrier tells us to apply or the FMCSA requires (for example, three years for driver qualification records). A carrier can export its full file at any time and can ask us to delete its data after termination; we honor that within 60 days, except where we must keep something to comply with the law. Backups age out on their own schedule.
9.Security
Traffic is encrypted in transit. Passwords are stored as salted scrypt hashes, never in plain text. Sessions are signed, httpOnly cookies. Documents live in a private store and are streamed only to signed-in users of the carrier that owns them; every carrier’s data is scoped to that carrier. No system is perfectly secure, so tell us right away at privacy@trudot.app if you think an account has been compromised.
10.Your choices and rights
- Text messages. Reply STOP to any message, or ask your office to switch SMS off on your record.
- Email alerts. Account owners can change alert settings in the app.
- Access, correction, deletion and a copy of your data. Depending on where you live, you may have these rights under state privacy laws (including in California) or other applicable law. Email privacy@trudot.app. If the information belongs to a carrier’s account, we forward the request to that carrier and help them answer it.
- No discrimination. We will not treat you differently for exercising a privacy right, and we never sell personal information.
11.Children
TruDOT is a workplace tool for commercial motor carriers and is not directed to anyone under 18. We do not knowingly collect information from children.
12.Changes and contact
We will update this policy as the service changes; the effective date above moves when we do, and we announce material changes in the app before they take effect. Contact: Umapachi LLC, 11335 NE 122nd Way, Suite 105, Kirkland, WA 98034, United States — privacy@trudot.app.