Security and data handling.
The questions an IT lead asks before granting access, answered from the policies that govern the service. Your TMS remains the system of record; Navion works around it.
Encryption and storage
- Is our data encrypted?
- Yes. Data is encrypted in transit and at rest. Stored data uses secure storage practices, including hashed passwords for any user credentials.
- How is the service tested for vulnerabilities?
- Navion performs vulnerability scanning and security reviews as part of regular security assessments. No method of transmission or storage is 100% secure, and Navion does not claim otherwise.
- Who else touches our data?
- Third-party service providers that operate the service on Navion's behalf: cloud infrastructure for hosting and storage, an authentication service, an email service, and a website analytics provider. Each is contractually obligated to protect the information and use it only for the purpose it was engaged for.
Access model
- Who at Navion can see our data?
- Access to your information is limited to authorized personnel only. Access controls are part of the security measures Navion maintains.
- How does Navion get access to our systems?
- Navion deploys a connector into your environment. Your team configures it to grant access to your TMS and your document management system (BOLs, scale tickets, delivery tickets, detention records, proof of delivery) for the workflows in scope. Navion exchanges data only with the systems you have authorized, such as your TMS, your document management system and the supplier portals you connect.
- Who controls what the automation is allowed to do?
- Your people. Extracted orders are held for dispatcher approval before enrichment, validation and order creation. Customer requirements and checks are yours to set; changes are tested and approved before use.
The TMS integration boundary
- Does Navion replace or modify our TMS?
- No. Navion is not a TMS and not a TMS replacement. Your TMS remains the system of record for execution. Navion reads from it and writes to it through the access your team grants, keeping the two in sync; how dispatch works inside the TMS does not change.
- What does Navion write to our TMS?
- Orders, order details and statuses. Navion creates orders in your TMS, adds details an order is missing such as accessorial charges, and updates statuses as work progresses. The sync is bidirectional: a change made in Navion is written to the TMS. What Navion may write is agreed for the workflows in scope.
Retention
- How long is our data kept?
- For as long as your account is active or as needed to provide the service, and as necessary to meet legal obligations, resolve disputes and enforce agreements. When data is no longer needed it is securely deleted or anonymized.
Support and incident commitments
- What availability does Navion commit to?
- A 99.9% monthly availability target for the service, excluding permitted downtime such as scheduled maintenance with notice. Availability is measured with Navion's internal monitoring.
- When is support available?
- Business hours support Monday to Friday, 9:00am to 5:00pm Central Time, excluding U.S. federal holidays, with after-hours coverage for Severity 1 incidents. Requests go to support@navionlogistics.ai.
- What counts as a security incident?
- The service level agreement defines an Integrity Incident as unauthorized access to customer data, cross-tenant data exposure, tampering with audit logs or receipts, or a confirmed breach of confidentiality or security affecting customer data. The full definitions, severity classification and service credits are in the Support Policy & SLA.
Questions your security review still has?
Bring them to the first conversation. Access, scope and terms are agreed with your team before setup.
Talk about our operation