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.

Explore OrionOS View Status

Customer Protections

Controls enterprise buyers expect from a freight operating system.

AccountMapped APIs apply tenant, role, and relationship checks; customer administrators should still use least-privilege access.

VaultIntegration credentials use a redacted credential-vault model with administrator-visible connection status.

SupportSupport records receive identifiers and in-app status history. External delivery and a verified response-time SLA are not yet represented here.

EvidenceStored reviews and events are operating records, not independent certifications or proof of external delivery.

Security And Operations

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

Setup wizards currently retain redacted connection metadata, not usable provider secrets. 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.

Last reviewed July 20, 2026. Contract terms, security exhibits, privacy terms, and vendor DPAs must be confirmed through the active order form and customer agreement.