◉ Security & Compliance

Built for freight that
can't go missing.

Mid-sized shippers — pharma, electronics, regulated chemicals — ask the same four questions before they trust any new marketplace. Here are the answers, with the operational details behind each one.

◉ 01 — Pillar

Carrier identity

FMCSA SAFER cross-check on every onboard. Active broker / motor-carrier authority required before any offer.
In-house identity & liveness KYC requested from every carrier. Government ID + multi-frame selfie + Claude Vision pre-review. Not yet required before a carrier is offered or accepts a load.
BMC-84 surety bond active on the broker authority (CVS Logistics LLC, MC-123033).
No anonymous carriers. Public surfaces (e.g. /trucks landing) anonymise coordinates and never expose carrier names.

◉ 02 — Pillar

Payments

Stripe Connect platform model. Your card is authorised when a carrier accepts (or two days before a pickup booked further ahead) and captured after delivery — a card hold, not an escrow, and the money never sits on our balance sheet.
Captured when the shipper confirms delivery, or automatically 24 hours after delivery is marked. Standard ACH settlement is about two business days to the carrier.
Application-fee enforcement at the gateway level — flat 5 % is non-negotiable per load.
PCI-DSS handled by Stripe end-to-end. Card data never touches our infrastructure.

◉ 03 — Pillar

Data & infrastructure

TLS 1.2+ on every endpoint, HSTS preload eligible, modern security headers.
Auth via HttpOnly Set-Cookie with a short-lived access token and a rotating refresh token; JWTs are signed and verified on every request.
Per-microservice nginx routing with rate limits on auth endpoints (10/min on /login, lockout after 10 failures in 15 minutes).
Daily Postgres backups with 30-day retention. Stripe webhooks HMAC-verified, fail-closed when secret missing.

◉ 04 — Pillar

Privacy & marketplace controls

No public load board. Shippers see only their own loads; carriers see only matched offers routed to them.
Shipper rate posts are private — competitors cannot scrape pricing.
Cross-tab logout via BroadcastChannel. localStorage cleared on sign-out so a shared device doesn't leak the next user.
DEMO accounts are isolated at the matching layer — they can never offer to or appear in real shippers'/carriers' workflows.

Have a security question we missed?

Compliance, SOC2 status, vendor questionnaires — email security@gethauldirect.com. We answer within one business day with the controls you need to clear procurement.

Post your first load →