Last updated: November 13, 2026
Effective Date: November 13, 2026
Sirius Logistics LLC, a South Carolina limited liability company doing business as HD Fleet, United States (“Company”, “we”, “our”, or “us”), operates the HD Fleet fleet management platform at hamadev.net and the HD Fleet mobile application for iOS (together, the “Service”). This Privacy Policy explains what personal information we collect, why, who receives it, how long we keep it, and what choices you have.
Carriers and drivers. HD Fleet is a business-to-business service for motor carriers in the United States. A carrier (a trucking company or owner-operator) creates a company account and invites its dispatchers, office staff and drivers. For the data about a carrier’s drivers and operations (loads, locations, pay, documents), the carrier decides why and how the data is used (it is the “business” or “controller”) and we process that data on the carrier’s behalf and under its instructions (we are its “service provider” or “processor”). For account, security, billing and Service-improvement data about you as a user of our Service, we act on our own behalf.
If you are a driver, your carrier is your first point of contact for questions about what it collects about you and for access, correction or deletion of employment-related records. We will assist the carrier in responding to you. You may also contact us directly at admin@hamadev.net.
This Policy is part of a set of legal documents: Terms of Service, Driver Location Notice, Data Retention and Deletion, Subprocessors and AI, Data Processing Addendum, Partner Data-Sharing Terms, Broker Portal Terms, Cookie Notice and Security Summary.
By creating an account or using the Service you acknowledge this Privacy Policy. If you do not agree, do not use the Service.
2.1 Account and profile. Full name, e-mail address, password (stored only as a salted bcrypt hash), phone number (optional), profile photo (optional), role in the company (for example Owner, Dispatcher, Accountant, Driver), account status, preferred language, and notification settings. If you sign in with Google, we receive your Google e-mail, display name, profile image URL and a Google account identifier (never your Google password).
2.2 Operational and business data. Vehicles (plate, VIN, unit number, specifications), loads (pickup and delivery addresses, dates, routes, distances, weights, commodity, status steps and timestamps), brokers and their contacts (including broker contacts shared with a connected partner company, Section 6), rates, driver pay and settlements, expenses, fuel purchases and receipts, maintenance records, parts, mileage, messages in company chat (text, photos, voice messages and files), and notes.
2.3 Tax and driver records (sensitive). Where your carrier uses these features: Form W-9 data (name, address, tax classification, TIN: SSN or EIN, signature, signing date and IP address), driver license, passport or work-authorization numbers, date of birth, payment details, emergency contacts, and driver qualification documents such as license, DOT medical card and expiry dates. Government ID numbers, TINs and payment details are encrypted at rest; they are shown masked (last four characters) and the full value can be revealed only by the account owner or a platform administrator, and every reveal is logged.
2.4 Location. See Section 3.
2.5 Photos, scans and documents. Photos and files you take or upload through the camera, photo library or document scanner (bills of lading, proof of delivery, rate confirmations, receipts, registrations, license and ID images). See Section 8. If you use voice messages in chat, the App asks for microphone access and uploads only the recordings you send.
2.6 Device, usage and technical data. IP address, browser or device type and operating system, app version, time zone, push notification tokens, session records, and server logs of requests and errors. We write logs without message contents, tax numbers or document contents. We keep a first-party counter of how often each screen is opened (screen template, user role and platform only; never the user, IP or the real page address). We do not use advertising or third-party analytics SDKs (Section 15).
2.7 Communications. Messages you send to us at admin@hamadev.net, support requests, and records of notifications we sent you.
2.8 Brokers, partner companies and other people in the Service. Besides carrier staff, the Service holds data about: broker employees who use a carrier’s broker portal (name, work e-mail, optional phone, company name, MC and USDOT numbers, FMCSA registration data we look up for the broker company, the loads and messages they send; see Section 6 and the Broker Portal Terms); staff of partner carrier companies connected to a carrier (names, roles, chat messages, signed partner contracts with signature image, typed name and title, IP address and browser string); and load-board accounts that a carrier owner chooses to connect (the board credentials are encrypted and only the last four characters are shown). Anyone who opens a public tracking link (Section 3) is not asked to identify themselves; we count views per link and use the IP address only for rate limiting.
2.9 Sources. Directly from you; from your carrier and its authorized users (for example when a dispatcher creates your profile or a load); automatically from your device and our servers; from Google if you use Google sign-in; and from public data sources for map, weather, fuel-price and address lookups (Section 7).
2.10 Connected mailboxes. If you connect a Gmail, Microsoft 365/Outlook or SMTP mailbox to send e-mail from the Service, we store an encrypted access token or password and use it only to send the messages you create, from your mailbox; the recipient lists, message content and attachments you choose are passed to that mail provider. We do not read your inbox. HD Fleet’s use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. You can disconnect a mailbox at any time in Settings.
We use two AI providers through their APIs. Google Gemini (Google LLC) is the main provider. Anthropic Claude (Anthropic, PBC) is a backup: if the Google models do not answer or their quota is used up, the same request is sent to Anthropic so the feature keeps working. Which provider answered a request is not shown to you. Content is sent only to return a result to us. We do not use your content to train our own models, and we do not allow either provider to use it for advertising. Provider terms: as of the date above, Google states that content sent through the paid Gemini API is not used to improve its products, and Anthropic states that it does not train its models on API inputs and outputs by default. Providers may keep API content for a limited time for abuse monitoring and legal reasons under their own terms; we do not control that retention. See each provider’s current terms and our Subprocessors and AI page.
What is sent, by feature:
The privacy scrubbing described for the assistant does not apply to autofill, scanning and file sorting: the document or text you choose to submit is sent as is, so do not submit documents you do not want processed by these providers. You can always fill the same forms by hand. AI features are not used to make decisions that have legal or similarly significant effects on a person; people make those decisions.
We use sensitive personal information (precise location, government ID and tax numbers, payment details) only to provide the Service you or your carrier requested, to keep it secure, and to comply with law. We do not use it to infer characteristics about you.
We do not sell personal information, and we do not share it for cross-context behavioral advertising.
| Provider | Purpose | Data involved |
|---|---|---|
| Railway | Application and database hosting; PDF generation service (Gotenberg) runs there as well | All Service data |
| S3-compatible object storage (Cloudflare R2 or Amazon S3) | Private storage of uploaded photos, documents and generated PDFs | Files you upload |
| Google (Gemini API) | AI features, main provider (Section 4) | Questions, snippets, pasted text, scanned images and documents, weekly totals |
| Anthropic (Claude API) | AI features, backup provider used when Gemini does not answer (Section 4) | The same content as for Gemini |
| U.S. FMCSA (QCMobile) | Check of a carrier or broker by MC / USDOT number | MC or USDOT number |
| U.S. NHTSA (vPIC) | VIN decoding | VIN |
| Postmark (only if the owner turns on inbound e-mail) | Receives e-mails that brokers or partners send to a carrier’s inbound address and forwards them to us | The e-mail, its attachments and sender address |
| Load boards you connect (for example Sylectus, NTG, C.H. Robinson, DAT, Truckstop) | Only if the carrier owner connects a board in Settings: loads from the board appear on the Spot board | The carrier’s own board credentials (encrypted) and board requests |
| Google (Sign-In) | Optional sign-in with Google | E-mail, name, profile image, account identifier |
| Resend | Delivery of transactional e-mail from noreply@hamadev.net (we do not send marketing e-mail) | Recipient e-mail, message content |
| Apple Push Notification service (APNs) and Web Push | Push notifications | Device token, notification text |
| Sentry (Functional Software, Inc.) | Error and crash reports from the website and the App, so we can fix bugs | Technical error details, device and app version, page or screen, internal user ID; personal data such as names, e-mails, phone numbers, tax IDs and locations is removed before sending; no session recording |
| Telegram | Optional Telegram bot: load cards, status updates, receipt photos, notifications | Telegram ID, messages, photos and locations you send to the bot |
| Apple Maps (App), OpenStreetMap tiles, Esri (ArcGIS) tiles and data | Map display, truck-stop verification data | Your IP address and the map area viewed |
| BigDataCloud | Fallback reverse geocoding when the ZIP or city is missing | Coordinates |
| Microsoft (Office Online viewer) | Preview of Word, Excel and PowerPoint files you open | A temporary signed link to that file and the file’s contents |
| Mail providers you connect (Google Gmail API, Microsoft Graph, or your SMTP server) | Only if you connect a mailbox in Settings: sending the e-mail you create from your own mailbox (Section 2.10) | Recipients, message content and attachments you choose; your encrypted token or password |
| OpenStreetMap Nominatim, U.S. Census Geocoder, Zippopotam.us | Address and ZIP lookup, reverse geocoding of driver coordinates into city, state and ZIP | Addresses, ZIP codes, coordinates |
| OSRM and Overpass (OpenStreetMap data) | Route lines and truck parking along a route | Route coordinates (no personal identifiers) |
| U.S. National Weather Service; U.S. Energy Information Administration | Weather and diesel price information | Map coordinates or state only; no personal data |
The full list, with what each provider does, is on our Subprocessors and AI page. Each provider handles data under its own terms and privacy policy. The mobile App’s embedded route maps also load map scripts from public content delivery networks. Links to Google Maps, Apple Maps or phone dialers open the respective apps when you tap them.
| Category | How long |
|---|---|
| Account and profile | While the account is active; anonymized when the account is deleted |
| Precise location points | 90 days, then only daily summaries (miles by state, route summaries) for IFTA and load records. Exact location points are deleted immediately when the driver deletes the account; daily mileage summaries (miles by state and day) are kept with the carrier’s IFTA records. |
| Push tokens, sessions, in-app notifications | Until sign-out or account deletion |
| Loads, settlements, payouts, expenses, receipts, fuel and IFTA source data | As long as the carrier’s account exists and as long as required by tax, accounting and transportation rules (generally at least 4 years for IFTA and tax records; typically 3 to 7 years) |
| W-9 and signed forms (all versions) | As long as the carrier’s account exists and as long as required by law (generally at least 4 years after the last payment) |
| Driver qualification and employment records | While the carrier keeps the driver on record and as required by law (generally 3 years after employment ends) |
| Chat messages | As long as the carrier’s account exists |
| AI assistant questions and answers | Not stored by us (providers: Section 4) |
| Public tracking links | The link stops working after 7 days or when revoked; the link record (hash, view count) stays with the load |
| Partner contracts, signatures and audit trail | Kept as long as both companies’ accounts exist; never edited after signing (a change voids the signature and keeps the history) |
| Broker portal sessions and sign-in codes | Sessions 90 days; one-time codes 10 minutes |
| Backups | Removed from backups on their normal rotation within 30 days |
A fuller schedule is on the Data Retention and Deletion page.
Deleting your account. In the App: Settings → Delete account (Apple App Store requirement). You can also write to admin@hamadev.net from your account e-mail; we complete verified requests within 30 days. Details are on our account deletion page. Deletion takes effect immediately: you can no longer sign in and other signed-in devices are signed out within about a minute. We immediately delete exact location points and work status, push tokens, sessions, linked sign-in methods and notifications, and anonymize your name, e-mail, phone, photo, password, Telegram link and notification addresses.
What we must keep. Records that your carrier is legally required to keep are not deleted: loads, settlements and payouts, receipts and expenses, signed tax forms (W-9) and driver qualification and employment records, and chat messages inside the organization. Names already recorded in these records stay as part of them. They are kept only for the period described above, and they are used only for those legal and accounting purposes. The Service does not yet purge them automatically; the carrier or we remove them when the retention period ends or on request once the law no longer requires them. If a carrier closes its company account, it can export its data first.
No system is perfectly secure. If a breach affects your personal information, we will investigate and contain it, and notify affected users and carriers and, where required, authorities, without unreasonable delay and in any case as required by applicable state breach-notification laws. Our goal is to notify within 72 hours of confirming the breach.
This section applies to California residents and is our notice at collection. In the last 12 months we collected the categories below. We collect them from the sources in Section 2.9, for the purposes in Section 5, and disclose them to the recipients in Sections 6 and 7. Retention is in Section 9.
| Category | Examples | Disclosed to |
|---|---|---|
| Identifiers | Name, e-mail, phone, account ID, IP address, device token | Carrier, partner companies and brokers you work with (name, e-mail, role), hosting, e-mail, push |
| Contact and customer records | Address, emergency contact, broker contacts | Carrier, partner companies (shared broker contacts), hosting |
| Commercial and financial information | Pay, settlements, expenses, W-9/TIN (sensitive), payment details (sensitive) | Carrier, hosting, storage; the partner company on a signed partner contract (masked tax and license numbers only) |
| Precise geolocation (sensitive) | Driver GPS points while on duty | Carrier; partner companies and people holding a tracking link, only as the carrier chooses (Section 3); hosting; address lookup providers (including BigDataCloud) |
| Professional and employment-related information | Role, driver license number and expiry, DOT medical card, qualification documents | Carrier, hosting, storage |
| Audio, electronic and visual information | Photos, scans, voice messages | Carrier, storage, AI providers (scans), Microsoft (file viewer) |
| Internet or other electronic network activity | Logs, session data, app version | Hosting, error monitoring (Sentry) |
| Government identifiers (sensitive) | SSN/EIN, license, passport or work-authorization number | Carrier (masked; full only for the account owner), hosting. Never shared with partners or brokers except a masked value in a signed partner contract. |
| Account log-in credentials (sensitive) | Password hash; encrypted load-board and mailbox credentials | Hosting; the board or mail provider you connect |
| Health information (sensitive) | DOT medical card number and expiry date | Carrier, hosting, storage |
| Inferences | No profiles about personal preferences or characteristics are created | — |
No sale or sharing. Making data available to a partner company, a broker or a tracking-link viewer at the carrier’s direction is part of providing the Service, not a sale or sharing for advertising. We have not sold or shared personal information (as those terms are defined by the CCPA/CPRA) in the last 12 months, and we do not knowingly sell or share the personal information of anyone under 16. Sensitive personal information is used only for permitted purposes: providing the Service, security, and legal compliance. Because we do not use it for other purposes, the right to limit use of sensitive personal information does not apply.
Your rights: to know and access (including a portable copy), delete, correct, opt out of sale or sharing (not applicable, as we do neither), limit use of sensitive information (not applicable, see above), and not be discriminated against for exercising rights. To the extent we act as a service provider to your carrier, we will pass your request to the carrier or help the carrier respond.
Verification and agents. We verify requests by matching your e-mail and account details, and may ask you to sign in or confirm by e-mail. An authorized agent may submit a request with your written permission, and we may verify your identity directly. We respond within 45 days; we may extend once by up to 45 more days and will tell you why.
Residents of Virginia, Colorado, Connecticut, Utah, Texas, Oregon and other states with consumer privacy laws may have the rights to confirm and access, correct, delete, obtain a portable copy, and opt out of targeted advertising, sale and profiling. We do none of those three. Some of these laws exempt employee, job-applicant and business-to-business data, and may not apply to data processed on behalf of your carrier; the carrier then handles your request. We respond within 45 days, extendable once by 45 days where permitted.
Appeal. If we decline your request, you may appeal within a reasonable time by e-mailing admin@hamadev.net with the subject “Privacy Appeal” and your reference. We answer the appeal in writing within 60 days (45 days in some states) with the reasons. If the appeal is denied, you may contact your state attorney general.
We cannot delete data we are legally required to keep; we will tell you what was kept and why. We do not charge a fee for reasonable requests.
We send transactional and service messages (account, security, invitations, load, chat, maintenance and document reminders) by e-mail, push notification and, if you linked it, Telegram. We do not send text messages (SMS). You can turn push categories on or off in the App and in iOS Settings, and manage notification e-mails in your notification settings. We do not currently send marketing e-mail; if we ever do, each such message will include an unsubscribe link and our postal address as required by the CAN-SPAM Act. Notifications and e-mails use the language set on your account.
The Service is for business use by adults and is not intended for anyone under 18. We do not knowingly collect personal information from anyone under 13 (COPPA) or from minors under 18. If you believe a minor has provided information, contact admin@hamadev.net and we will delete it.
The Service is operated from the United States and is intended for U.S. carriers. Data is hosted on Railway and in S3-compatible object storage; hosting region: United States. Our AI and map providers may process data in the United States and other countries. If you use the Service from outside the United States, you understand that your information is transferred to and processed in the United States, which may have different data protection rules from your country. The Service is not offered for use under the EU/UK GDPR; if you are in those regions, contact us before using it.
We may update this Policy. When we make material changes we will change the “Last updated” date, give carriers at least 15 days’ notice before a material change takes effect (except changes required by law or for security), post a notice in the Service (a screen on the website and in the App that you must accept the next time you sign in) and, for significant changes, e-mail account holders. Continued use after the effective date means you accept the update.
Sirius Logistics LLC (HD Fleet)
Mailing address: [mailing address]
Email: admin@hamadev.net
Support: hamadev.net/support
Website: hamadev.net
We aim to answer privacy inquiries within 30 days and always within the periods required by law.