Last updated: November 13, 2026
Effective Date: November 13, 2026
This Addendum is part of the Terms of Service between Sirius Logistics LLC, a South Carolina limited liability company doing business as HD Fleet (“we”) and the carrier company that holds an account (“Carrier”). It applies automatically when the Carrier agrees to the Terms; no separate signature is needed. If it conflicts with the Terms about personal data, this Addendum prevails. “Personal Data”, “process”, “business”, “service provider” and “sale” have the meanings in applicable U.S. state privacy laws, including the California Consumer Privacy Act as amended (CCPA).
For Personal Data that the Carrier or its users put into the Service about drivers, staff, brokers, partners and others (“Carrier Data”), the Carrier is the business (controller) and we are its service provider (processor). For account, security and Service-improvement data about users as users of our Service, we act on our own behalf, as described in the Privacy Policy.
| Item | Description |
|---|---|
| Purpose | Providing the Service: loads, dispatch, tracking, chat, documents, settlements, expenses, maintenance, reports, partner and broker features, and AI features the Carrier uses |
| Duration | While the Carrier’s account exists, plus the retention in the Data Retention and Deletion page |
| People | Carrier staff and drivers, owner-operators, broker employees, partner company staff, customers and contacts named in loads |
| Data types | Identifiers and contact data; driver qualification data; W-9 and tax identifiers; payment details; precise location of drivers; photos, scans, documents, voice messages; messages; operational and financial records |
| Sensitive data | Precise location, SSN/EIN and other government ID numbers, payment details, date of birth. Health data is limited to a DOT medical card expiry date and certificate number |
The Carrier authorizes the providers on the Subprocessors and AI page, including the AI providers. We bind them to data-protection terms no less protective than this Addendum where their standard terms allow, and remain responsible for them. AI providers keep content under their own terms (see the Privacy Policy), and the Carrier accepts this when it enables AI features. We update the page before a new provider receives personal data, and handle objections as described on that page.
We give the Carrier tools to answer requests from drivers and others (the “Download my data” export, role-based views, deletion) and, on request, reasonable help with access, correction, deletion and portability requests, with data-protection assessments, and with regulators. If someone asks us directly about Carrier Data, we tell them to ask the Carrier, and we pass the request on to the Carrier.
We tell the Carrier without undue delay after confirming a breach of Carrier Data, with our goal being within 72 hours of confirmation, and give what we know: what happened, the data affected, what we did and what the Carrier should do, and we will provide updates as we learn more. Notice of an incident is not an admission of fault. The Carrier is responsible for notices to its drivers and authorities where the law makes the Carrier the notifying party, and we will help.
Before closing, the Carrier can export its data. After the account ends we delete or anonymize Carrier Data as described in Data Retention and Deletion; records the law requires us or the Carrier to keep are retained for the required period and used only for that. Backups age out within 30 days.
On reasonable request we provide written information to show that we comply with this Addendum. A more detailed audit may be requested once a year, with notice, at the Carrier’s cost, during business hours, under confidentiality and without access to other customers’ data.
The Service is operated from the United States for U.S. carriers and is not offered for use under the EU or UK GDPR. If a Carrier is subject to such laws, it must contact us before using the Service.
The limits in Section 15 of the Terms apply to this Addendum. Questions or requests under it: admin@hamadev.net (mailing address: [mailing address]).