Privacy Policy

Last updated: November 13, 2026

Effective Date: November 13, 2026

1. Introduction and Who Is Responsible

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. Information We Collect

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.

3. Location Data

  • Driver tracking (App). With the driver’s permission, the App reports precise location, including in the background. iOS asks for location access “While Using the App” and then “Always”; “Always” is needed so location keeps reporting when the screen is off or the App is closed. Reporting happens only while our server confirms one of these: the driver’s work status is “Working”; the driver has an active load (also when the status is “Vacation” or “Home time” — the carrier is warned about this); or no work status is set and a truck is assigned to the driver. Otherwise collection and sending stop. The App shows the driver whether tracking is on and why.
  • What is collected: coordinates, accuracy, speed, heading, the time of the fix, the truck assigned at that time, the state, city and ZIP derived from the coordinates, the device’s location-permission status (for example “Always” or “While Using”) and precise-location setting, Low Power Mode, the phone’s battery level and whether it is charging, and the app version, so dispatch can tell why a driver is not reporting. When the phone goes silent on a load, we record the gap and the likely reason (for example location off or phone off).
  • Why: dispatch coordination and ETA, showing the truck on the map, per-state mileage for IFTA fuel-tax reports, route summaries of loads, and proof of delivery. We do not use location for advertising, and we do not sell it.
  • Who sees it: the driver and the carrier’s authorized staff. Other companies see location only in the five cases below, each started by the carrier and each ended by the carrier at any time:
    • Public tracking link. An office user (owner, dispatcher or tracker) of the carrier can create a link for one open load and send it to a customer or broker. Anyone who has the link can open it without signing in. It shows: the company name and logo, the driver’s first name and last initial, the truck number, the truck’s current position on a map (exact GPS point, with city, state and ZIP), heading and speed, the route driven since pickup (up to 72 hours), city and state of pickup and delivery, the delivery stop’s map point (no street address in text), the next stop with miles, ETA and appointment window, and after delivery only “Delivered” with the place and time. It never shows money, phone numbers, e-mails, broker, load or PO numbers, street addresses, notes or documents. Only the SHA-256 hash of the link’s secret is stored. A link works for 7 days after it was created, then stops; it also stops at once when it is revoked, when a new link is made for the same load, or if the person who created it loses an office role. Creating a link is the carrier’s decision; the carrier is responsible for who receives it (see the Terms).
    • Partner fleet map. If a carrier owner switches on “Share my fleet map” for a connected partner company, the partner’s owner and dispatchers see that carrier’s drivers on their fleet map: live point, work status, battery level, today’s path and history, current and next load (including the next stop’s company and address). The setting is off by default, can be changed only by the carrier’s owner, applies the carrier’s own tracking rules (for example “do not track”), never includes money, and ends immediately when the owner switches it off or the connection ends.
    • Loads handed over by a partner. When a carrier takes a load that a connected partner handed over, the partner’s owner and dispatchers can see, on their own copy of that load, the exact position on a map (with city, state, ZIP and time), name and phone number of the driver the carrier assigned to it. This starts when the load is taken and ends 2 hours after delivery, or at once if the connection ends or is blocked. A separate chat for that load can include the assigned driver. The partner also sees “picked up”, “delivered” and the proof of delivery. Other drivers of the carrier are never visible to the partner this way.
    • Partner fleet view. If a carrier owner switches on “Sees my fleet” for a connected partner, the partner’s owner and dispatchers see the last known position of each shared truck (map point, city, state, ZIP and time), whether it is free or on a load, and the assigned driver’s name and phone. The setting is off by default, only the owner can change it, and it ends at once when switched off or when the connection ends.
    • Brokers. A broker who works through a carrier’s broker portal sees only the status and messages of loads that broker sent to that carrier, as the carrier chooses to show them.
  • Driver control: in My GPS the driver sees the tracking status and can start or end a shift, and can revoke location permission at any time in iOS Settings (some features, such as automatic reporting, will then not work).
  • Retention: exact points are kept for 90 days; after that only daily summaries are kept (miles by state, truck and day, and load route summaries), which are needed for IFTA and tax records. See Section 9 and the Driver Location Notice.
  • One-time lookups and mileage tracker. Using your current position to find a ZIP code or nearby services is not stored. For company owners, the optional mileage tracker keeps the full route on the phone and sends only the trip’s start and end points, their addresses, the time and the miles to the Service, where they are kept as a tax mileage record.
  • Telegram. If a driver manually shares a location through the Telegram bot, it is handled under the same rules.
  • Carrier responsibility. The carrier is responsible for informing its drivers about tracking and for obtaining any consent or giving any notice that the law requires of an employer.

4. AI Features

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:

  • AI assistant (optional). The assistant is switched on per company by the platform administrator. When you ask a question, the question and a limited set of data snippets that the assistant looked up for you (for example your loads, maintenance due dates or expiring documents) are sent to the AI provider to write the answer. The assistant is read-only; it only sees what your role may see (a driver gets only the driver’s own loads and pay). Before sending, we automatically try to remove or mask Social Security and tax numbers, bank and account numbers, phone numbers and e-mail addresses, and we exclude fields such as dates of birth, addresses, file links and tokens; this filtering is not perfect, so do not type such numbers into your questions. We do not store your questions or the answers on our servers (we keep only counters for daily limits and technical metadata without content). Daily question limits apply per user and per company. AI answers can be wrong; see our Terms.
  • Weekly owner summary. For companies with the assistant switched on, an owner may receive a weekly e-mail or push. Company totals for the week (for example gross, net, miles, unpaid amounts, expiring documents) are sent to the AI provider, which writes a few sentences of commentary. No driver names, tax or ID numbers are included; the commentary is dropped if it contains a number that was not in the data we sent.
  • Load auto-fill. Text you paste, or an image/PDF of a rate confirmation you provide, is sent to the provider to extract fields (dates, addresses, company names, rates, weights) into the load form. The same extraction reads rate confirmations and e-mails that a broker sends through a carrier’s broker portal or inbound e-mail address, and posts pasted or forwarded into the Spot board.
  • Receipt, registration and document scanning (OCR). A photo of a fuel or expense receipt, a vehicle registration, or a driver or vehicle document (for example a license, medical card, insurance or registration, to read the expiry date) is sent to the provider to read amounts, dates, vendor, vehicle details and expiry dates. The same receipt scanning is used when a receipt photo is sent through the Telegram bot. The document scanner can also send small page pictures to the provider to suggest page rotation and order.
  • File sorting. If your company has AI features on, a file in the inbox, or a picture or PDF sent in a load chat, may be sent to the provider to suggest whether it is a BOL, POD or other document and which load it belongs to.
  • Spreadsheet import. When you import a spreadsheet and ask the AI to map columns, the column headers and at most five sample rows are sent.
  • Parts research. “Find parts for this truck” sends the truck’s year, make, model and engine (decoded from the VIN with the U.S. NHTSA vPIC service) to the provider to list maintenance parts. The VIN itself is not sent to the AI provider, only to NHTSA.
  • Sign-up screening. When a new carrier company registers, its company name, USDOT and MC numbers and the e-mail domain (not the person’s name, mailbox or phone) are sent to the provider to help flag fake sign-ups. A person reviews flagged sign-ups; the AI does not approve or reject anyone by itself.
  • Name translation. Names of maintenance and expense items may be sent to the provider for translation into standard English terms.

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.

5. How We Use Information

  • Provide and operate the Service: loads, dispatch, tracking, chat, documents, settlements, expenses, maintenance, reports and exports.
  • Authenticate users, enforce role-based access and company data separation, and secure accounts.
  • Send service messages: account approval, invitations, password resets, load and chat notifications, document-expiry and maintenance reminders.
  • Provide AI features (Section 4), maps, weather and fuel-price information.
  • Support carriers with tax and regulatory records (for example W-9, IFTA mileage, driver document expiry).
  • Detect abuse and fraud, debug, and keep the Service reliable.
  • Improve the Service using aggregate usage information, and comply with law.

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.

6. Who We Share Information With

We do not sell personal information, and we do not share it for cross-context behavioral advertising.

  • Your carrier and its users, according to roles. Drivers see their assigned loads, own pay and own documents. Dispatch and office staff see operational data. Money data is limited to finance roles. The accountant role is read-only and cannot see GPS, chat or full tax numbers. Companies are separated from each other, except for the connections a carrier chooses to switch on, described in the next three bullets.
  • Connected partner companies. Two carrier companies can connect as partners (both sides accept). Only then, and only for what the carrier turns on: the partner sees the carrier’s shared trucks (“Sees my fleet”) and, if “Share my fleet map” is on, its drivers’ locations (Section 3); brokers the carrier shares (contacts only; each side sees only its own money); loads handed over (with the assigned driver’s position, name and phone while the load runs) and their documents; loads offered on the shared chat or the Spot board; the partner chat (text, files); and the signed partner contract with its audit trail. The partner’s users receive this data under the Partner Data-Sharing Terms. Disconnecting, blocking or switching a setting off stops access at once; what the partner already saved in its own records (for example a load it took) stays with the partner.
  • Brokers. Brokers who use a carrier’s broker portal are users of that carrier’s portal. The carrier sees the broker’s name, e-mail, company and the offers and messages; a broker sees what the carrier shows in the portal (company name, public carrier packet documents the carrier chose to share, load status). See the Broker Portal Terms.
  • People with a tracking link. See Section 3.
  • Service providers listed in Section 7, only as needed to run the Service, under their terms and our instructions.
  • Platform support. A small number of our platform administrators can access account data where needed to operate, support and secure the Service, including per-company operational and revenue views. Signing in to a company’s account as one of its users requires a written reason and is logged.
  • Legal and safety. If required by law, subpoena or other legal process, to protect rights, safety or property, or to enforce our Terms.
  • Business transfers. In a merger, acquisition or sale of assets, with notice to affected users where required.
  • Aggregated or de-identified information that cannot reasonably identify you (for example an anonymous broker payment rating shown only when at least three companies contribute data, without company names).

7. Service Providers We Use

ProviderPurposeData involved
RailwayApplication and database hosting; PDF generation service (Gotenberg) runs there as wellAll Service data
S3-compatible object storage (Cloudflare R2 or Amazon S3)Private storage of uploaded photos, documents and generated PDFsFiles 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 numberMC or USDOT number
U.S. NHTSA (vPIC)VIN decodingVIN
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 usThe 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 boardThe carrier’s own board credentials (encrypted) and board requests
Google (Sign-In)Optional sign-in with GoogleE-mail, name, profile image, account identifier
ResendDelivery 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 PushPush notificationsDevice token, notification text
Sentry (Functional Software, Inc.)Error and crash reports from the website and the App, so we can fix bugsTechnical 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
TelegramOptional Telegram bot: load cards, status updates, receipt photos, notificationsTelegram ID, messages, photos and locations you send to the bot
Apple Maps (App), OpenStreetMap tiles, Esri (ArcGIS) tiles and dataMap display, truck-stop verification dataYour IP address and the map area viewed
BigDataCloudFallback reverse geocoding when the ZIP or city is missingCoordinates
Microsoft (Office Online viewer)Preview of Word, Excel and PowerPoint files you openA 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.usAddress and ZIP lookup, reverse geocoding of driver coordinates into city, state and ZIPAddresses, ZIP codes, coordinates
OSRM and Overpass (OpenStreetMap data)Route lines and truck parking along a routeRoute coordinates (no personal identifiers)
U.S. National Weather Service; U.S. Energy Information AdministrationWeather and diesel price informationMap 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.

8. Files, Photos and Documents

  • Files are stored in private storage. They are opened only through short-lived signed links issued after the server checks your role and your company. Profile photos and company logos are the only public files. Exception: to preview Word, Excel and PowerPoint files we pass the signed link to Microsoft’s Office Online viewer, which fetches the file to show it (Section 7); you can download the file instead.
  • Smaller thumbnails are generated from photos for faster loading; the original photo is kept and you can download it.
  • Tax numbers and ID numbers are encrypted at rest and masked on screen (Section 2.3). Generated W-9 PDFs are stored masked.
  • Access to sensitive documents and reveals of full numbers are logged.

9. Retention and Deletion

CategoryHow long
Account and profileWhile the account is active; anonymized when the account is deleted
Precise location points90 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 notificationsUntil sign-out or account deletion
Loads, settlements, payouts, expenses, receipts, fuel and IFTA source dataAs 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 recordsWhile the carrier keeps the driver on record and as required by law (generally 3 years after employment ends)
Chat messagesAs long as the carrier’s account exists
AI assistant questions and answersNot stored by us (providers: Section 4)
Public tracking linksThe link stops working after 7 days or when revoked; the link record (hash, view count) stays with the load
Partner contracts, signatures and audit trailKept 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 codesSessions 90 days; one-time codes 10 minutes
BackupsRemoved 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.

10. Security and Breach Notification

  • HTTPS/TLS for data in transit; bcrypt-hashed passwords; secure httpOnly session cookies; rate limiting on sign-in.
  • Server-side role checks on every request and strict separation of companies.
  • AES-256-GCM encryption at rest for tax and ID numbers and payment details; masked display; logged reveals.
  • Private file storage with short-lived signed links; no tokens, tax numbers or contents in logs.

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.

11. California Privacy Notice (CCPA/CPRA)

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.

CategoryExamplesDisclosed to
IdentifiersName, e-mail, phone, account ID, IP address, device tokenCarrier, partner companies and brokers you work with (name, e-mail, role), hosting, e-mail, push
Contact and customer recordsAddress, emergency contact, broker contactsCarrier, partner companies (shared broker contacts), hosting
Commercial and financial informationPay, 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 dutyCarrier; 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 informationRole, driver license number and expiry, DOT medical card, qualification documentsCarrier, hosting, storage
Audio, electronic and visual informationPhotos, scans, voice messagesCarrier, storage, AI providers (scans), Microsoft (file viewer)
Internet or other electronic network activityLogs, session data, app versionHosting, error monitoring (Sentry)
Government identifiers (sensitive)SSN/EIN, license, passport or work-authorization numberCarrier (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 credentialsHosting; the board or mail provider you connect
Health information (sensitive)DOT medical card number and expiry dateCarrier, hosting, storage
InferencesNo 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.

12. Other U.S. State Privacy Laws

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.

13. How to Submit a Request

  • E-mail admin@hamadev.net from the e-mail address of your account and tell us what you want (access, correction, deletion, copy of data).
  • Use “Download my data” (website and App) for a portable copy of your personal data; it does not include location history or chat, which we provide on e-mail request.
  • Delete your account yourself in the App under Settings → Delete account (Section 9).
  • Drivers: ask your carrier first for records the carrier controls; we will assist the carrier.
  • You can correct your profile in Settings, and export your carrier’s operational data in CSV/Excel inside the Service where your role allows it.

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.

14. E-mail, Push and Telegram Messages

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.

15. Cookies, Local Storage and Tracking

  • The website uses only essential cookies (sign-in session and CSRF protection) and browser local storage for interface preferences (such as language and theme) and unsent drafts. Details are in our Cookie Notice.
  • We do not use advertising, retargeting or third-party analytics trackers or SDKs in the website or the App, and we do not “track” you across other companies’ apps and websites (App Tracking Transparency does not apply).
  • Do Not Track / Global Privacy Control. Because we do not sell or share personal information or run cross-site tracking, there is nothing to opt out of; browser DNT and GPC signals therefore do not change how the Service works.

16. Children

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.

17. Data Location and International Users

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.

18. Changes to This Policy

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.

19. Contact

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.

HD Fleet — Loads & Expenses for Carriers & Owner-Operators