How past data licenses show up in M&A diligence and disclosure schedules

Where do data licenses appear in a disclosure schedule?#

Data licenses appear in a disclosure schedule wherever the purchase agreement's definitions catch them, which is usually in more than one place. Seller's counsel lists them so the representations are accurate; buyer's counsel uses the lists to decide what to read first.

The definitions differ from deal to deal, so treat the table as a map of where to look rather than a rule. Thresholds, such as a value above which a contract counts as material, are set in each agreement.

What will the acquirer's counsel read in each license?#

The acquirer's counsel reads each data license for terms that survive the sale and terms that restrict the combined business. A license that looked routine to the company can raise new questions when the acquirer has its own AI plans for the same records.

• 1Parties: which entity is the supplier, and whether it is the entity being sold.
• 2Licensed records: the record families, systems and date ranges covered.
• 3Permitted use and model scope, including any rights over future model versions.
• 4Exclusivity and follow-on rights, with their scope and expiry.
• 5Term, termination rights and what survives termination.
• 6Assignment and change-of-control provisions.
• 7Deletion duties and whether certificates were received.
• 8Payment terms, including any amounts still due after closing.
• 9Representations, indemnities and liability caps given by the company.
• 10Audit rights either party still holds.

Which seller representations reach data licenses?#

Seller representations reach data licenses through intellectual property, privacy and contract compliance language. An IP representation may say the company has not granted exclusive rights in its IP except as scheduled; a privacy representation may say the company complied with its own notices and applicable law when sharing personal data; a contract representation may say the company is not in breach of customer agreements.

Each one can be made accurate by a precise schedule entry. Problems arise when a license is missing from the schedules, or when the schedule describes scope more broadly or narrowly than the agreement actually grants. Accurate scheduling protects the seller after closing, because indemnity claims often turn on what was disclosed.

Which license terms raise questions at exit?#

License terms raise questions at exit when they restrict the acquirer or leave obligations open. Most can be avoided at signing with a little foresight, and some can be fixed with an amendment before a sale process starts.

What does a clean license file look like?#

A clean license file lets someone who was not in the negotiation answer every diligence question from the documents alone. It should sit in one folder per license, ready to move into a data room without editing.

The core documents are the signed agreement and amendments, a short scope memo, approvals such as board minutes and any lender or investor consents, the privacy record showing what was removed before delivery, delivery records showing what was sent and when, payment records, and deletion certificates for any ended license. Where records came from customer-facing systems, add the rights review that confirmed customer contracts allowed the use.

Illustrative: a distributor's license meets a buyer's AI plans#

Illustrative: a fictional industrial distributor owned by a lower-middle-market fund licensed order exception records from its Epicor system to a model developer during the hold period. At exit, a strategic acquirer's counsel flags the license because the acquirer plans its own AI project on similar records.

The operating partner hands over the license file. It shows that exclusivity covers only one field of use and one record family, that change of control needs notice but not consent, and that the privacy record documents removal of customer contact details. The seller's schedule already describes the license accurately, so the acquirer's counsel notes it as a known restriction and moves on.

The one gap is a missing deletion certificate for an earlier pilot. The company requests it from the developer before signing, and the schedule notes it as received.

How operating partners can prepare during the hold period#

Operating partners can prepare during the hold period by treating data licenses like any other contract category that will be diligenced. The work is simple when done as licenses are signed and tedious when reconstructed under exit time pressure.

• 1Keep one register of data licenses across the portfolio, with scope, term, exclusivity and renewal dates.
• 2Use a standard term sheet so follow-on rights and change-of-control terms stay consistent.
• 3Avoid open-ended exclusivity and rights over all future data.
• 4Document board, lender and investor consents at signing.
• 5Agree revenue treatment with the CFO and auditors when the first license is signed.
• 6Collect deletion certificates as licenses end.

How SourceX supports exit readiness#

SourceX documents every package with a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. Those entries answer several of the first questions an acquirer's counsel asks about a data license: what was licensed, on what rights, for which uses, with what privacy treatment and on whose approval.

Because each license runs through the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, the supplier's approvals and the delivery record are captured as the deal happens rather than rebuilt at exit.