And there's a particular irony here: the contract you're about to paste almost certainly contains a clause forbidding you from doing exactly that. Scroll to the confidentiality section. It lists who is allowed to see this document. A chatbot vendor isn't on the list.
Worse, the confidential information in it usually belongs to the other side — which makes this someone else's secret to lose, and someone else's claim against you.
The confidentiality clause names permitted recipients. Standard drafting runs something like "…may disclose to its employees, officers and professional advisers who need to know." That's a closed list. An AI vendor is not your employee and not your adviser. There is no reading of that clause that quietly includes them.
It isn't your information. In most agreements the counterparty is the one being protected. So the injured party is a company you have a commercial relationship with, and the remedy sitting in that same document is often an injunction plus costs.
Unreleased numbers are a different order of problem. If the figures relate to a listed company — yours, your customer's, or an acquisition target's — you may be holding material non-public information. Disclosing MNPI to an unapproved third party isn't a policy breach. It's a securities regulator's business.
Pricing is competitive intelligence. Your discount ladder and your negotiation position are among the most commercially valuable things your company owns, and the easiest to hand over without noticing.
Nearly every question people paste a contract to answer can be asked in the abstract. You want to understand a mechanism, not have a document read aloud to you.
Summarise the risks in this MSA:
MASTER SERVICES AGREEMENT
between Acme Retail Ltd
and Northwind Systems Ltd
dated 14 April 2026
Fees: 1.2M annually
Signed: J. Blake, CFO
[…38 pages…]
In a SaaS master services
agreement, what should a
customer watch for in a
liability cap set at
1x annual fees with an
uncapped carve-out for
data breach?
What's typically negotiable?
If you genuinely need a specific clause reviewed, lift that clause alone and replace the parties, dates and amounts with placeholders. The legal mechanics are identical with [SUPPLIER] and [CUSTOMER] in them — that's rather the point of contract drafting.
An enterprise tool your legal team has approved for contract work. Contract review is one of the strongest genuine use cases for AI, and plenty of firms have adopted tools built for it — with confidentiality terms, retention controls and privilege considerations handled properly at the procurement stage.
So the useful move is to ask Legal what they've already approved before improvising. There's a reasonable chance the answer is "we bought one, it's in the intranet, nobody uses it."
One thing the exception doesn't cover: a counterparty's confidentiality clause binds your company regardless of how good your tooling is. If the clause says employees and advisers only, an approved vendor still isn't on the list without their consent.