Skip to content

Security

Security is part of the operating record

FreightPilot is designed around workspace membership, tenant-scoped data access, auditable actions, and explicit operational evidence. This page states the controls and the remaining limits plainly.

Controls in place

  • Authenticated access with role checks and active workspace membership on business endpoints.
  • Organization-scoped reads and writes; cross-tenant record access returns 404 rather than revealing existence.
  • HTTP-only, same-site authentication cookies; the console SPA also uses a short-lived bearer token held in tab-scoped session storage, with cache clearing on account switches.
  • Encrypted provider credentials at rest; keys are masked in the interface and can be revoked.
  • Audit events for sensitive workspace, route, payment, and provider actions.
  • Hash-pinned backend dependencies and dependency-audit gates in CI.

Current limits

  • This is not a claim of SOC 2, ISO 27001, PCI-DSS, or another third-party certification.
  • FreightPilot does not take custody of funds, provide escrow, or guarantee a carrier payment.
  • Public docs and status pages are informational; a signed enterprise agreement controls support and incident commitments.
  • External AI providers are optional and governed by the workspace owner's provider relationship.
  • Independent security review and customer-specific threat modeling should precede high-risk deployment.

Report a vulnerability

Do not include production secrets, customer data, or personal information in a public issue. Contact the team through the contact page with a concise description, affected surface, reproduction steps, and the minimum evidence needed to validate the report. We will acknowledge the report and coordinate disclosure according to the risk and the affected workspace.