Orion TransportationOrionOS
Trust Center
Enterprise trust for freight teams running one connected system.
OrionOS brings TMS, LMS, documents, billing, support, integrations, and customer controls into one operating layer. This page describes currently implemented controls and calls out where external delivery, monitoring, or independent assurance is still pending.
Customer Protections
Controls enterprise buyers expect from a freight operating system.
Built for the realities of logistics software.
OrionOS includes the operational foundation enterprise teams look for: permission templates, connector setup, support operations, quality checks, recovery planning, incident communication, and customer-facing policies.
Access Control
Customer admins manage users inside their own organization. Authorized account administrators control subscription status, module gates, add-on entitlements, account setup, and support operations.
Vendor Integrations
When an authorized administrator supplies provider passwords, API tokens, client secrets, or signing secrets, OrionOS retains them as encrypted ciphertext in a tenant-bound server vault so the configured adapter can authenticate. Browser storage and normal API responses receive redacted metadata rather than usable credentials. Credentials can be replaced or revoked, and a connector is labeled connected only after a server-side provider validation receipt; unavailable providers remain clearly unconfigured.
Data Handling
Operational records, files, billing, LMS, messages, support tickets, and integration events are structured around the customer account instead of loose app-to-app copies.
Service Health
OrionOS stores review records and provider receipts where available. This Trust page is not a live availability monitor and does not infer provider health from configuration alone.
Compliance
FMCSA, OSHA, DQ files, driver training, document vault, AuditGuard, support records, and evidence packets stay close to the work they support.
AI Governance
Hey Orion is positioned as an assisted command layer with role-aware boundaries, human approval expectations, audit trail context, and access tied to purchased entitlements.
Due Diligence Documents
Review the boundaries before purchasing.
These documents state what OrionOS currently supports, what is configurable, and what still requires an executed agreement or provider-specific review.
Security overview
Implemented access, encryption, release, monitoring, recovery, and evidence controls—with limitations called out.
Data processing addendum
A reviewable DPA template. It becomes binding only when completed and executed by both parties.
Subprocessors
Provider categories, purposes, optionality, and the verification boundary for tenant-configured services.
Data residency
Current hosting and transfer boundaries, including the absence of a customer-selectable residency guarantee.
Last reviewed September 22, 2026. Review the versioned Privacy Notice and request process. Contract terms, security exhibits, privacy terms, and vendor DPAs must be confirmed through the active order form and customer agreement. Issued product records are available through the authenticated License Center. To responsibly report a suspected security issue, email operations@oriontransportation.us or review the published security contact.