Logistics and distribution
Shipper confidentiality in broker-carrier agreements: what it restricts
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Broker carrier agreement confidentiality clauses usually bar the carrier from disclosing or using the broker's shipper identities, rates, lanes and contract terms except to haul the freight, and most sit beside a back-solicitation ban. They rarely mention data reuse, so the answer turns on the definition of confidential information, its exceptions, its survival period and the treatment of de-identified records.
Key takeaways
- The clause mainly binds the carrier, but many agreements make confidentiality mutual.
- Back-solicitation and confidentiality are separate promises with separate remedies and survival terms.
- Load records that name shippers, consignees or rates usually fall inside the definition of confidential information.
- Whether de-identified or aggregated records escape the clause depends on its exact wording.
What does shipper confidentiality cover in a broker-carrier agreement?#
Shipper confidentiality in a broker-carrier agreement covers the information a broker shares so a carrier can haul a load: the shipper's and consignee's names and locations, the rate, the commodity, the lane and often the terms of the agreement itself. The broker's concern is commercial, because its customer relationships and margins are its business.
Most clauses define confidential information broadly, then limit the carrier's use of it to performing the transportation services. Some agreements make the obligations mutual, so the broker also owes confidentiality over carrier information such as the carrier's rates, equipment, insurance and safety details.
These clauses are usually short, and that is part of the difficulty. A few sentences written to stop a carrier from going around the broker are now being read for a question their drafters never considered: whether load history can be reused for analytics or licensed to an AI developer.
Typical clauses and what each restricts#
Seven clauses in a typical broker-carrier agreement decide what a carrier may do with load records: the definition of confidential information, permitted use, back-solicitation, exceptions, survival, return or destruction, and remedies. Wording differs from broker to broker, and the precise language in each agreement decides what it covers.
| Clause | Typical wording pattern | What it restricts for load records |
|---|---|---|
| Definition of confidential information | Shipper and consignee names, rates, lanes, volumes, agreement terms | Records containing these details are covered wherever they are stored |
| Permitted use | Use only to perform services under the agreement | Uses beyond hauling, such as analytics shared with third parties, may fall outside |
| Back-solicitation | Carrier will not solicit freight directly from the broker's shippers | Commercial contact rather than data use, though shipper lists are the trigger |
| Exceptions | Public information, already known, independently developed, required by law | Records the carrier generated itself may arguably fall outside, depending on wording |
| Survival | Obligations continue for a period, or indefinitely, after termination | Old load records can stay covered long after the last load |
| Return or destroy | Return or destroy confidential information on request | A broker's request can reach archived rate confirmations and tenders |
| Remedies | Injunctive relief, damages, or a commission on back-solicited freight | Breach risk attaches to disclosure, not only to solicitation |
Back-solicitation is not the same as confidentiality#
A back-solicitation clause restricts commercial contact, while a confidentiality clause restricts information. A carrier can honor one and breach the other: never calling a broker's shipper, yet disclosing that shipper's lanes and rates in a dataset.
Back-solicitation clauses often run for a set period after the last load and may carry a specific remedy, such as a commission on diverted freight. Confidentiality may survive for a different period or indefinitely, and some agreements are silent on survival altogether. Read the survival language separately for each promise rather than assuming one period covers both.
What does the clause mean for a carrier reusing load records?#
For a carrier, the clause means that load records from brokered freight are not purely the carrier's own information. Rate confirmations, tender emails and dispatch records name the broker's shipper and consignee, the rate and the lane, and those details sit inside the usual definition of confidential information.
Records the carrier creates itself, such as driver assignments, transit times, detention events, delay reasons and equipment data, are less clearly covered, though they are stored alongside the broker's information in the same load file. Separating the two, and removing or tokenizing shipper, consignee, broker and rate fields, is the usual starting point for any reuse.
- Collect every broker-carrier agreement, including terms accepted on broker onboarding portals.
- Read the definition of confidential information and the permitted use language.
- Check exceptions, survival and return-or-destroy terms.
- Map which load record fields contain broker-supplied information.
- Decide with counsel whether de-identification resolves the restriction or consent is needed.
Which load record fields came from the broker?#
The load record fields that came from the broker are the ones the carrier could not have known without the tender: who the shipper and consignee are, what the broker pays, the reference numbers the shipper uses and any special instructions. Fields the carrier generates while hauling are a different category, even when they sit in the same row.
Sorting fields this way turns a vague contract question into a concrete preparation plan. Broker-supplied fields are removed, tokenized or generalized; carrier-generated fields are reviewed for anything that still points back to a shipper, such as an exact facility address recorded on a check call.
| Field | Usual source | Typical treatment for reuse |
|---|---|---|
| Shipper and consignee names and addresses | Broker tender and rate confirmation | Remove or tokenize; generalize locations to region |
| Rate paid to the carrier | Rate confirmation | Remove or band, depending on the clause |
| Shipper reference, PO and pickup numbers | Broker tender | Remove; replace with surrogate load IDs |
| Broker name and MC number | Agreement and tender | Tokenize, since it can reveal the shipper relationship |
| Appointment and actual times, detention, delays | Carrier dispatch and ELD | Usually carrier-generated; shift dates if they reveal a schedule |
| Driver notes and check-call comments | Carrier dispatch | Carrier-generated, but scan for shipper names and dock details |
What does a mutual clause mean for the broker's records?#
A mutual clause means a broker's load history can be restricted by its carrier agreements as well as by its shipper contracts. Under a mutual clause, what the carrier gives the broker, such as its rates, insurance certificates, safety and inspection details, equipment lists, factoring or payment details and driver contacts, is usually the carrier's confidential information.
Brokers also generate records about carriers: tender acceptance, on-time performance, claims, scorecards and the rates they paid. Those are the broker's own records, but they describe identifiable carriers, so read the mutual clause and the broker's carrier terms before reusing them. Carrier identities and rates paid are normally removed or tokenized in any outside package.
Check onboarding platforms too. Carrier packets collected through third-party onboarding or monitoring services may be governed partly by the platform's own terms, which can limit what either party does with that information.
Illustrative: a dry van carrier reviews its broker agreements#
Illustrative: a fictional dry van carrier hauls a mix of direct shipper freight and brokered loads. Leadership wants to know whether its transit-time and delay-reason history could support a data license, so the general counsel reviews the broker-carrier agreements first.
Many agreements were accepted on broker onboarding portals, and copies have to be downloaded one by one. Most define confidential information to include shipper identities and rates; a few are mutual; none mention aggregated data. One broker's clause covers all information relating to any load, without exceptions for carrier-generated records.
The carrier decides to exclude broker-supplied identities and rates entirely, keep its own events with lanes generalized to regions, and leave out every load from the broker with the broadest clause. The scope is narrower than first hoped, but each limit traces to a specific contract.
How SourceX handles broker-carrier restrictions#
SourceX maps broker-carrier agreements in the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Restricted fields are removed or generalized in Preparation, and loads under unusually broad clauses can be excluded entirely.
Each decision lands in the licensing rights and permitted use entries of the SourceX Evidence Packet, so the carrier and the licensee see the same record of what was included and why. The carrier approves the final scope.
Frequently asked questions
Do click-through broker onboarding agreements count?
They are usually treated as binding, so they belong in the review. Carriers often accept broker terms through onboarding platforms without keeping copies. Download the version you accepted where possible, note the date, and ask the broker for a copy if the portal only shows the current version.
Does removing shipper names solve the problem?
It often helps, but not always. If the clause protects information about the shipper's business, such as lanes, volumes and rates, removing names may not be enough when a lane or volume pattern still points to one shipper. Counsel reads the definition, and preparation checks for residual identification.
How long do the obligations last after we stop hauling for a broker?
The survival clause decides. Some agreements set a fixed period after termination, some say obligations survive indefinitely, and some are silent, which leaves the question to contract law in the governing state. Check each agreement rather than assuming old records are free of restrictions.
Can a broker demand that we delete our load records?
A return-or-destroy clause may let a broker request return or destruction of its confidential information, often with exceptions for records kept for legal or regulatory reasons. Carriers have their own retention duties for some records, so counsel should reconcile the two before anything is deleted.
Are direct shipper loads affected by broker agreements?
Not by the broker agreements, but by the carrier's own contracts with those shippers, which may carry their own confidentiality and data terms. Keep the two sets of loads clearly flagged in the archive, because the analysis and the scope often differ between them.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.