Security Summary

Last updated: November 13, 2026

Effective Date: November 13, 2026

A plain-language summary of how we protect data. It supports Section 10 of our Privacy Policy. No system is perfectly secure; we describe what we do, not a guarantee.

1. Accounts and access

  • Passwords are stored only as salted bcrypt hashes. Sign-in is rate limited. Sessions use secure, httpOnly cookies and last up to 7 days.
  • Every request is checked on the server for your role and your company. Companies are separated from each other; the accountant role is read-only; drivers see only their own loads, pay and documents.
  • Broker portal sign-in uses an e-mail one-time code (stored as a hash, valid 10 minutes, 5 attempts) and an optional password.
  • 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.

2. Protecting data

  • HTTPS/TLS in transit.
  • Tax numbers (SSN, EIN), driver license, passport and work-authorization numbers, payment details and load-board credentials are encrypted at rest with AES-256-GCM, shown masked, and revealed in full only by the account owner or a platform administrator, with every reveal logged. W-9 PDFs are stored masked.
  • Files are stored privately in S3-compatible storage with server-side encryption, and opened only through short-lived signed links after a role and company check. Only avatars and company logos are public.
  • Public tracking links and partner access are built from a fixed list of fields; they cannot return money, phone numbers, street addresses or documents. Link secrets are stored only as hashes and links expire after 7 days.
  • Logs carry codes and counts, not tokens, tax numbers, message text or document contents. Error reports go through a scrubber before they leave our servers.

3. Operations

  • Hosting on Railway; secrets are kept in environment variables, not in code.
  • Database backups rotate out within 30 days.
  • If a breach affects personal information we investigate and contain it, and notify affected users and carriers and, where required, authorities, as state breach-notification laws require. Our goal is to notify within 72 hours of confirming a breach.
  • We have not been independently certified (for example SOC 2 or ISO 27001), and we do not claim to be.

4. Reporting a vulnerability

Write to admin@hamadev.net with the subject “Security”. Please include what you found, the steps to reproduce it and how to reach you. We aim to acknowledge within 3 business days.

If you act in good faith, we will not take legal action against you for research that: stays within your own accounts and data; does not access, change or keep other people’s data; does not degrade the Service (no denial-of-service, spam or social engineering); and gives us reasonable time to fix the issue before you tell anyone. This is not permission to test other companies’ accounts.

Contact

HD Fleet

Email: admin@hamadev.net

Support: hamadev.net/support