Change-of-control and assignment clauses: what they mean for acquired data

What the two clauses do#

An anti-assignment clause restricts a party from transferring the contract to someone else without consent, while a change-of-control clause attaches consequences to a change in who owns or controls a party. Both matter for acquired data because the right to use customer records usually comes from the contract under which they were collected.

The clauses come in many forms. Some prohibit assignment outright, some allow assignment to affiliates or to a successor to the business, and some treat a change of control as a deemed assignment. Others give the customer a termination right, a renegotiation right or simply a right to be notified when ownership changes.

The decision path for acquired data#

The decision path for acquired data runs through four questions in order, and each answer narrows what the acquirer can do with records from a given customer.

Only records that pass all four steps are candidates for new uses, and the fourth step is where most of them stop. Contracts written to deliver a service often permit data use only to provide that service, whatever happened to the contract in the deal.

• 1Deal structure: was this a stock purchase, an asset purchase or a merger? In a stock deal the contracting entity usually stays the same; in an asset deal contracts must be assigned to the buyer.
• 2Clause language: does the contract restrict assignment, assignment by operation of law or a change of control, and what consequence follows?
• 3Consent: if consent or notice was required, was it obtained in writing, and did it come with conditions?
• 4Data-use scope: with the contract in place, what does it actually permit for customer data, and does the intended use fall inside that scope?

How deal structure changes the analysis#

Deal structure changes which clause is in play. The table shows the usual pattern; state law and the exact wording can change the answer, so counsel should confirm it for each contract family.

Clause wording and what it means for data#

Clause wording decides the consequence, and a handful of patterns recur in the customer contracts that software and services acquirers inherit. Post-closing reorganizations deserve particular care: an add-on merged into a platform entity after closing may trigger the same clauses the original stock deal avoided.

Why consent does not widen data use#

Consent to an assignment or change of control does not widen data use, because consent moves or preserves the contract as written. If the original agreement allowed customer data to be used only to provide the service, the acquirer inherits exactly that limit.

Consent letters can also narrow use. Customers asked to approve a transfer sometimes add conditions, such as no use of their data beyond the service, no sharing with sister companies or deletion on request. Those letters belong in the contract file, next to the agreement they modify, or the condition is forgotten at the first integration.

Privacy notices follow the same logic. Records collected under a notice that described specific purposes generally stay tied to those purposes after the deal, whatever the corporate structure. Which privacy laws may apply is assessed deal by deal with counsel.

Building the contract map after closing#

A contract map after closing is a single table that ties every customer, or every contract template version, to the clauses and consents that govern its records. Without one, integration teams make data decisions from memory, and the conditions in consent letters are the first thing forgotten.

A workable map has one row per negotiated agreement or template version, with columns for the assignment clause, any change-of-control trigger, whether consent was required and obtained, conditions attached to the consent, the data-use clause and the privacy notice in force at collection. Start with the largest customers and the templates that cover the long tail, then add negotiated agreements as counsel reviews them.

Illustrative: an asset deal with conditional consents#

Illustrative: a fictional software acquirer buys an inspection scheduling product through an asset purchase. Most customers are on click-through terms that allow assignment to a successor of the business. A smaller group of enterprise customers signed negotiated agreements requiring consent to any assignment.

The deal team obtains those consents before closing, and several enterprise customers attach a condition that their data be used only to provide the service. After closing, the holdco considers licensing de-identified internal engineering and support records. Counsel maps every customer to its contract family and consent letter.

Records tied to conditional consents are excluded from scope. The company's own code, internal issues and release notes, which do not depend on customer contracts, go to a separate rights review, with a scan for pasted customer information before anything is considered further.

How SourceX reviews acquired-data rights#

SourceX reviews acquired-data rights in the Rights step of the SourceX five-step transaction, tracing each record family from the contracts under which it was collected, through the acquisition documents, to the entity that would sign today. Record families whose chain has a gap are left out of scope rather than argued in.

The SourceX Evidence Packet records that chain under provenance and licensing rights, so a buyer, and later an acquirer of the portfolio company, can see why each record family was included and which consents it relies on.