IN Brief:
- A California federal court approved a settlement in the Freightmate–Flexport dispute on 8 October.
- Freightmate and its founders acknowledged acquiring and using confidential shipping documents.
- The case raises practical questions about access controls and provenance of logistics software data.
Freight technology company Freightmate and logistics platform Flexport have settled a US trade-secrets dispute concerning confidential shipping documents, following a report dated 9 October 2026. A California federal court approved the settlement on 8 October. The development is relevant to supply chain software providers because customer records and internal freight documentation are increasingly used to support automated workflows and analytical tools. The settlement establishes specific acknowledgements; it should not be represented as a general court ruling that all freight data used in artificial intelligence systems is protected in the same way.
Under the stipulated judgment, Freightmate and co-founders Bryan Lacaillade and Yingwei Zhao acknowledged acquiring and using some of approximately 2,000 confidential Flexport shipping documents. Zhao separately acknowledged acquiring information Flexport classified as trade secrets. The distinction between documents being confidential and information meeting the legal definition of a trade secret matters. The terms of the stipulated settlement should not be expanded into claims about the contents of every document or the circumstances in which each individual record was handled.
The settlement followed a court ruling concerning failure to preserve electronic evidence. The court found that the defendants’ failure had prejudiced Flexport’s ability to pursue its claims. However, the judge did not find that Flexport had demonstrated deliberate destruction of evidence with the intention of preventing it from being used in the litigation. Those findings must be kept separate: deficient preservation and intentional destruction are different legal issues, and the case should not be described as establishing intentional spoliation.
Freight forwarding platforms hold documents generated across bookings, shipment execution, customs processes and commercial customer relationships. Such records can contain pricing, routing instructions, account details or other commercially sensitive information, depending on the document and the particular business. The details in this case do not establish which information appeared in every disputed file. Nevertheless, the matter illustrates why logistics companies need clear controls when information is copied between business systems or carried into a new software environment.
Artificial intelligence adds a further layer to those governance questions. Developers may use real-world examples to test extraction, classification, matching or search functions in freight software. But a data source being technically accessible does not in itself establish that its commercial use is authorised. Data collected during employment or through customer relationships can be governed by contracts, confidentiality obligations and company policies. Firms deploying AI-enabled tools need an identifiable chain of authority for the datasets they use, particularly where products are trained or evaluated against operational records.
For software buyers, the issue is not limited to whether a supplier offers useful automation. Procurement and legal teams may need to ask where demonstration datasets originated, whether customer permissions cover secondary uses, and what procedures exist for deleting or segregating data when a contract ends. The appropriate responses will vary with the services and data involved. The settlement does not establish new statutory requirements for all logistics operators, but it provides a concrete example of how weaknesses in governance can become material commercial and legal disputes.
Evidence retention is equally important. Freight businesses routinely process records in email accounts, collaborative platforms, customer portals and transaction systems. If a dispute emerges, relevant material may reside across those locations. Defined retention procedures and the ability to suspend routine deletion when required can help organisations account for their records. The court’s findings in this case make preservation an independently important part of the story, rather than a technical footnote to the trade-secrets allegations.
A careful reading of the legal record is particularly important for customers making procurement decisions. The reported acknowledgement concerns acquisition and use of documents, whereas separate procedural findings concern preservation of evidence. Neither point, without further evidence, establishes the performance, security or technical design of Freightmate’s product. Buyers should avoid converting the litigation into unsupported claims about a supplier’s entire platform or about the practices of unrelated freight technology firms.
The court-approved settlement resolves this particular dispute, while the use and retention of commercially sensitive shipping documents remains a continuing operational concern for software providers. Shipping technology companies must be able to develop and test new tools while respecting the provenance and agreed uses of sensitive records. Customers, in turn, need confidence that information entrusted to a logistics provider is not being reused in ways they did not authorise. The Freightmate–Flexport case underlines the value of examining data rights and auditability as carefully as the functionality promised by new software.
