Last Updated
May 19, 2026. Trust documentation is reviewed as platform controls, operations, and customer support processes mature.
Security Baseline
Freight Back Office OS uses authenticated access, environment separation, secure configuration practices, and operational safeguards appropriate for freight back-office workflows.
Access Controls
Staff and driver experiences are separated, account access is scoped by role and organization, and operational access is limited to support or account administration needs.
Operational Monitoring
Platform health, application behavior, and support signals are monitored so the team can investigate issues and prioritize practical remediation.
Data Retention
Retention practices are designed around operational records, document workflows, support needs, and customer account administration. See the retention page for additional detail.
Incident Response
Material incidents affecting customer data or availability are reviewed, prioritized, and communicated through designated support channels with clear next steps.
Transparency on certifications
Freight Back Office OS does not represent SOC 2, ISO, HIPAA, PCI, or similar certifications on this page unless and until formally achieved and documented.
Customer responsibility
Customers remain responsible for inviting appropriate users, removing access when team members leave, reviewing uploaded documents, and following their own accounting, factoring, and compliance requirements.
Questions about security or platform operations?
Contact our support team for trust-related questions, operational concerns, or platform availability follow-up.
support@adwafreight.com