Logistics and distribution

Shipper-broker agreements: can brokers reuse load data?

By SourceX Editorial · Reviewed by Noah Loul · October 9, 2026

Short answer

Whether a broker can reuse load data under a shipper-broker agreement depends on which of three positions the contract takes: an explicit data clause, confidentiality only, or silence. An explicit clause controls. Confidentiality-only terms usually need de-identification and careful review before any third-party use. Silence is not permission, because routing guides, portal terms and incorporated documents still apply.

Key takeaways

An explicit data use clause controls over general confidentiality language.
Silence on data is not blanket permission, because incorporated documents, portal terms and trade secret law can still apply.
Routing guides, RFP award terms and shipper portal terms can add restrictions the signed agreement lacks.
Some shipper agreements now bar using their data to train AI models.
Sort the shipper base contract by contract before scoping any reuse.

Who controls load data in a shipper-broker relationship?#

Load data in a shipper-broker relationship is controlled by contract rather than by any default rule of ownership. The broker creates and stores most of the records, such as quotes, tenders, carrier selections, tracking events and invoices, but much of the content describes the shipper's business: its facilities, lanes, volumes, products and prices.

That split is why the useful question is about permitted use, not ownership. A brokerage may hold every load file in its TMS and still owe the shipper limits on what it does with them. The signed agreement, and every document it pulls in, sets those limits.

Three contract positions, three different answers#

The three contract positions are an explicit data clause, a confidentiality clause with no data clause, and silence on both. Each leads to a different next step, and a brokerage with many shippers will usually find all three in its files.

Three contract positions, three different answers
Contract position	What it usually means	Next step
Explicit clause permitting data use	Broker may use data as the clause allows, often only de-identified or aggregated	Confirm the permitted purposes reach licensing to a third party
Explicit clause restricting data use	Use limited to providing services, or AI training barred outright	Exclude that shipper's records or seek written consent
Confidentiality only	Shipper information protected and limited to performing services; analytics not addressed	Counsel reads definitions and exceptions; de-identified use is assessed case by case
Silent on data and confidentiality	No express limit in the signed agreement	Check routing guides, RFP terms and portal terms before relying on silence

The decision tree, step by step#

The decision tree runs shipper by shipper, because a brokerage's agreements rarely match. Large shippers tend to send their own paper; smaller shippers often sign the broker's form, or nothing beyond a credit application and emailed quotes.

Step 1: gather the signed agreement and every document it incorporates, such as shipper terms, routing guides, rate agreements and RFP award letters.
Step 2: search for an explicit data, analytics, aggregated data or AI clause. If one exists, it controls this question; read its permitted purposes closely.
Step 3: if there is no data clause, read the confidentiality clause: what counts as confidential, permitted use, exceptions and survival.
Step 4: if confidentiality covers shipper information, decide with counsel whether de-identified and aggregated records fall outside it.
Step 5: if the agreement is silent on both, check incorporated terms and any portal agreements before treating the records as unrestricted.
Step 6: record the outcome per shipper as permitted, permitted after de-identification, consent needed or excluded.

Why silence is not permission#

Silence on data use is not permission because other terms and rules still shape what a broker can do. Documents incorporated by reference can restrict reuse even when the signed agreement says nothing about data, and trade secret law may protect some shipper information, such as pricing and volumes, without any contract clause at all.

Routing guides and supplier codes of conduct are common sources of data terms. Shippers often update them without a new signature and post them on a portal, so the version in force when a load moved may differ from the current one. Keep dated copies.

How the information arrived matters too. Data a broker pulled from a shipper's own TMS or tendering portal may be governed by that portal's terms of use, which can be stricter than the brokerage agreement itself.

When the shipper agreement addresses AI directly#

Some shipper agreements now address AI directly, for example by barring the broker from using shipper data to train or improve AI models, or by requiring notice before any AI tool processes shipper information. Where such a clause exists, it decides the question for that shipper's records.

Read these clauses closely. Some bar training by the broker's software vendors but say nothing about the broker's own de-identified analytics; others reach any machine learning use at all. Some cover only information the shipper provides, leaving broker-generated records such as carrier performance and exception handling outside their scope.

Mistakes brokerages make when reading shipper contracts#

The most common mistake brokerages make is reading only the signed master agreement. Data terms often sit in documents nobody in sales or operations thinks of as contracts: the routing guide, the RFP award letter, the shipper's supplier portal terms or the purchase order conditions attached to each tender.

Other mistakes are quieter but just as costly to fix later. Each one turns a manageable rights question into a scope that has to be rebuilt after preparation has started.

Treating former shippers as unrestricted because the relationship ended, when confidentiality often survives termination.
Assuming a confidentiality clause only covers documents marked confidential, when many definitions reach all non-public business information.
Reading an AI clause as covering only the broker's software vendors, without checking whether it reaches the broker itself.
Relying on the current routing guide instead of the version in force when the loads moved.
Sorting by customer name instead of by legal entity, so a shipper's subsidiaries end up under the wrong agreement.

Illustrative: a brokerage sorts its shipper base#

Illustrative: a fictional brokerage focused on temperature-controlled freight wants to know whether its load, exception and carrier performance history could be licensed. Its general counsel sorts every active and former shipper by contract position.

The largest shippers signed their own paper, and one of those agreements bars any AI training on shipper data, so its loads are excluded. Mid-size shippers mostly have confidentiality-only terms, so their records move forward with shipper identities tokenized and lanes generalized. Smaller shippers signed nothing beyond credit applications, but loads tendered through one shipper's portal fall under portal terms that restrict use to the transaction, so those loads are excluded too.

What remains is still substantial: carrier performance and exception histories across many lanes, with every exclusion traceable to a specific document.

How SourceX handles shipper-broker restrictions#

Shipper contracts are worked through during the Rights stage of the SourceX five-step transaction, which runs Supply, Rights, Preparation, Approval and Delivery. The per-shipper outcomes from the decision tree set what Preparation removes, generalizes or excludes.

The resulting licensing rights and permitted use are written into the SourceX Evidence Packet, and the brokerage approves the scope before anything is delivered. Under the SourceX Enterprise Data Value Framework, rights is one of the drivers of value, so a well-documented rights position helps the package as well as protecting the broker.

Frequently asked questions

Is the broker's own pricing covered by shipper confidentiality?

Partly. The broker's carrier costs and margin decisions are its own business information, but the shipper's rate, lanes and volumes are usually the shipper's confidential information. Records that combine both need sorting field by field, and the shipper rate is normally removed or generalized before any outside use.

Do we need consent from every shipper?

No, not automatically. Consent is needed where a contract restricts the intended use and de-identification does not resolve it. Many brokerages start with shippers whose terms are clearly compatible, exclude restrictive ones, and seek consent only where a shipper's records are central to the package.

What about carrier information in the same load files?

Carrier names, MC numbers, rates paid and contact details may be covered by broker-carrier agreements, especially mutual confidentiality clauses. Treat them as a separate layer of restriction, and remove or tokenize carrier identities alongside shipper identities before any outside use.

Can a shipper change the terms for records we already hold?

A shipper can propose an amendment or publish a new routing guide, which often changes terms for future loads. Whether a change reaches records created under earlier terms depends on the wording. Keep dated copies of the terms in force for each period and note which governed each load.

Do quotes that never became loads count?

Often, yes. Quotes and spot bids contain shipper lanes, volumes and target rates, so confidentiality can cover them even without a load. They are also useful for pricing analysis, which makes them worth including in the rights review instead of assuming they fall outside the agreement.

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your brokerage qualifies Talk to SourceX