Skip to content
Blog

How Do You Keep Freight AI From Leaking One Customer's Rates to Another?

By Connor Miller, Founder and CEO, FreightScout. Last updated 11 November 2026.

Short answer: you don't take the vendor's word for it. You ask four things before an agent ever sees a rate. Where does my data live, and who else can reach it? Does my data train or feed anything another brokerage gets? What can the agent say out loud to a carrier or a shipper? And can I see every message it sent? If a vendor can't answer all four in plain words, it doesn't get your book.

Why is this the question that matters most?

Because your rates are the business. I spent 12 years on a floor. The lanes you've built, what each shipper pays, what you pay to cover it, and the spread in between, that's what a brokerage actually owns. The trucks aren't yours. The freight isn't yours. The book is.

We already guarded it the old way. You didn't leave a rate sheet on the printer. You didn't tell a carrier who the shipper was before the load was booked. A new rep who forwarded the wrong customer's quote to the wrong customer heard about it that afternoon.

An AI agent sits in the middle of all of that. It reads the email, sees the lane history, talks to carriers and drafts to shippers. So the same rules apply, and you need to know how they're enforced before day one, not after the first bad email.

Where can a rate actually leak?

Think about it the way you'd think about a new hire. The leaks come from a handful of places.

Where it leaksWhat it looks like on the floorWhat to ask the vendor
Another brokerageYour lanes and margins sit in a database or model that other customers use tooIs my data kept to my brokerage only, and how?
A shared model or rate productYour rates help train a model, an index or a benchmark another brokerage benefits fromIs my data used to train anything shared, or pooled with anyone else's?
A carrier callThe agent gives up your max pay, or names your shipper to a carrierWhat won't it say on a call?
An outbound messageA quote, update or email goes to the wrong contact with the wrong number in itWho sees a message before it goes, and is every send logged?
A third-party AI modelEmail or load content gets sent to a model provider that keeps itCan the model provider train on my content?

Most of these aren't new risks. Software just moves faster than a rep, so a bad habit goes out wider before anyone catches it.

How should your data be kept apart from other brokerages?

Your data should be scoped to your brokerage, enforced in the database, not just promised in a sales deck.

Here's how we do it at FreightScout. Each brokerage's operational data is scoped to that brokerage. Row-level security is enforced so each organization sees only its own data. A connected mailbox copy is stored against your brokerage's organization under the same row-level security, and no other customer can reach it.

If you connect Google or Microsoft, the OAuth tokens are encrypted at rest with AES-256-GCM. The keys are held separate from the database, and raw tokens aren't written to logs or shown in the product. Security and audit logs of sign-ins, privilege changes and administrative actions are append-only.

That's the bar I'd hold any vendor to. Ask them to say, in writing, how one brokerage is kept out of another brokerage's loads. "We take security seriously" isn't an answer.

Does your data train something another broker gets?

This is the one people forget to ask. A vendor can keep your loads private and still use your rates to build something everybody else buys: a shared model, a lane benchmark, a rate tool.

At FreightScout, your load, lane, rate, carrier, margin and contact data isn't used to train generalized AI or machine-learning models. It isn't shown, sold, licensed or made available to any other customer. It isn't pooled with any other customer's data to build a shared model, index, benchmark or rate product. What the product learns from your data stays scoped to your brokerage.

Some features send email content to an AI model, for things like reading a rate request into a quote or judging whether a reply is interested. That content goes to the model provider only to produce that result for you, under terms that don't allow the provider to train on it. The provider is named on our privacy and messaging policy.

If a vendor's answer to "does my data train anything shared" is long and full of qualifiers, the answer is probably yes.

What will the agent say to a carrier?

On the phone is where a careless agent does the most damage. Two things should never come out of its mouth: your ceiling and your customer.

FreightScout's carrier sales agent says it's an AI assistant at the start of the call without being asked. It doesn't give up your ceiling and doesn't name your customer. It negotiates up to your max pay and never above it, and above the ceiling the offer waits for a person. Before a load word is spoken, the caller's number is checked against the MC, and if it doesn't match he gets a call back on the number of record. More on how that call runs is on the AI carrier sales page.

That's the same thing you'd teach a rookie in week one. Don't say who the shipper is. Don't open with your top number. Don't talk load details to a number you haven't checked.

How do you keep the wrong number off an outbound message?

You put a person in front of it until you trust it, and you keep a record of everything that went out.

At FreightScout, booking the carrier and shipper outreach run supervised by default. A person sees the action before it leaves. You can switch either one to autopilot per team and per action when you're ready, and you can move it back the same day. Every action is logged and reversible.

To be straight about it: nobody can unsend an email, person or software. That's exactly why the sends that leave the building start on approve. The log tells you who got what and when, so if something does go to the wrong contact, you know in minutes and you make the call yourself.

Inside your own brokerage, the agent works the same book your reps already see in your TMS. It cites the load, the lane and the margin behind what it tells you, so you can check where a number came from before it goes anywhere.

What should you do before you connect an AI agent to your book?

Treat it like onboarding a rep who'll see every lane on day one.

  1. Get the data answer in writing. Where it's hosted, how one brokerage is kept out of another's data, and whether anything is pooled or trained. Ours is on the security page.
  2. Read the policy, not just the page. Retention, who processes what, and the OAuth scopes belong in a real policy. Ours is the privacy and messaging policy.
  3. Ask what it says on a call. Max pay, the customer's name and caller checks. Get it specific.
  4. Start every outbound send on approve. Booking and shipper outreach should wait for a person until your floor has watched enough of them.
  5. Know how it connects to your TMS. With FreightScout it's by API where the TMS offers one, and by reading it in place where it doesn't, set up during implementation. The details are on integrations, and the questions to ask before anything writes back are in what to ask before AI writes to your TMS.
  6. Check the log in week one. Pull a handful of sent messages and booked loads and read them like you'd read a new rep's work.

Questions brokers ask

Can another brokerage on the same software see my rates?

It shouldn't be possible, and you should ask how it's enforced. At FreightScout, row-level security is enforced so each organization sees only its own data, and your load, lane, rate, carrier, margin and contact data isn't shown or made available to any other customer.

Is my rate data used to train a shared AI model?

Not at FreightScout. Your data isn't used to train generalized models and isn't pooled with another customer's data to build a shared model, index, benchmark or rate product.

Will the AI tell a carrier who my shipper is?

It shouldn't, and FreightScout's agent doesn't name your customer on a carrier call. It also doesn't give up your ceiling.

Will the AI ever go over my max pay to cover a load?

No. FreightScout negotiates up to your max pay and never above it. Anything over waits for a person.

Does the AI model provider keep my email content?

Ask the vendor who the provider is and what the terms say. At FreightScout, content sent to the model provider is used only to produce the result for you, under terms that don't allow the provider to train on it. The provider is named in the privacy policy.

How do I stop a wrong quote or update from going out?

Keep sends on approve until you trust them. FreightScout runs booking and shipper outreach supervised by default, and every action is logged and reversible. Nobody can unsend a message, so the approve step is the real protection.

Where's my data hosted?

At FreightScout, Vercel hosts the application and Supabase hosts the database and authentication. Product data is held in Supabase and passes through Vercel in transit. The full detail is on the security page.

Related

All posts: the blog index.