Rights and contracts
Acquired business dataset release approvals: who signs during integration
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
During acquisition integration, the entity that holds the records approves a dataset release, acting through people its own governing documents authorize. Before closing that is the target's management, within the merger agreement's covenants and without buyer direction; after closing it is the record-holding entity under the acquirer's new delegation of authority, with the seller's cooperation for records still on its systems, and always within the original privacy promises.
Provenance trail
Acquired business dataset
Key takeaways
- Approval authority follows the entity that holds title to the records, not the team that runs the system.
- Before closing, the target decides its own releases; buyer approval of ordinary-course decisions can raise gun-jumping issues.
- After closing, officers of the record-holding entity sign under a delegation of authority, which should be in writing before they do.
- Under a transition services agreement the seller is usually custodian, not owner, and confirms exports rather than approving them.
- Privacy promises and customer terms from the collection period travel with the records through the deal.
Who should approve dataset releases during acquisition integration?
The legal entity that holds the records approves the release, acting through people its own governing documents authorize, and the approval is valid only if it respects the deal's constraints for that phase. Before closing, that is the target's management, within the merger agreement's interim covenants and without the buyer directing it. After closing, it is the record-holding entity under the acquirer's delegation of authority, with the seller's cooperation when records still sit on its systems under a transition services agreement.
Most integration plans name an owner for each system and each team. Few name who may sign off when someone asks to license or share a dataset built from the acquired company's records. This guide gives a phase-by-phase authority matrix, the evidence each approval should file, a worked example with an exception, and the signals that should stop a release until counsel looks at it. It is general information, not legal advice.
Why custody, ownership and approval authority split during integration
During integration, three things that usually sit with one person come apart: custody (who runs the system the records live in), ownership (which entity holds title to the records and the rights in them) and approval authority (who may commit that entity to a release). A release is approved properly only when the person signing has authority for the entity that owns the records and the custodian can actually deliver them.
Integration splits them in predictable ways. The acquirer's IT team may administer the acquired company's CRM before the entities merge, so custody moves while ownership stays. In a carve-out, the seller may keep running the systems under a transition services agreement, so the buyer owns records it cannot export without the seller. And the acquired company's former officers may have resigned while the new delegation of authority is still being drafted, leaving nobody clearly able to sign.
Two further layers sit on top of entity authority. Contracts with customers and vendors may restrict use or transfer of their data, and the privacy notices under which personal information was collected limit what any owner may do with it. Neither changes because ownership changed.
Between signing and closing, can the buyer approve the target's dataset releases?
No. Until closing, the target decides its own releases, and the buyer should not be approving its ordinary-course decisions. For transactions reportable under the Hart-Scott-Rodino Act, U.S. antitrust agencies treat transferring beneficial ownership before the waiting period ends as gun-jumping, and they look at who makes decisions in the normal course of business and who controls assets or contracts.
The FTC's guidance on pre-merger conduct notes that interim conduct of business provisions requiring the buyer's approval for decisions the target would make in the ordinary course can amount to gun-jumping, and it recommends clean teams and sharing only the information needed for diligence. The agencies' submission on gun-jumping advises that each company keep operating as a separate, independent entity during the waiting period.
In practice, the target's management approves or declines a proposed dataset license during this window, under its existing authority. If the merger agreement's interim covenants require buyer consent for actions outside the ordinary course, and entering a new data license may be one, the consent request goes through the channel the agreement sets out, with deal counsel involved, rather than through the integration team informally. Sharing samples of the dataset with the buyer before closing raises its own information-exchange questions and belongs with the clean team, if at all.
The transition authority matrix, phase by phase
Use the matrix to name, for each phase, who holds the records, who signs, who must consent or be consulted, and what goes in the file. Phases often overlap for different systems, so apply it system by system rather than for the whole company at once.
| Phase | Who may approve a release | Who must consent or be consulted | Evidence to file |
|---|---|---|---|
| Diligence, before signing | Target's management under its own authority | Target's counsel; no buyer direction | Target's approval record; any NDA limits on what was shown to the buyer |
| Signing to closing | Target's management, within interim covenants | Buyer only through the covenant consent process; deal counsel | Covenant analysis; consent letter if required |
| Closing to entity merger | Officers of the record-holding entity under the acquirer's new delegation of authority | Integration lead; privacy and contracts owners | Board or delegation resolution; title to the records under the purchase agreement |
| Transition services period | Buyer entity that owns the records | Seller as custodian under the TSA | TSA access and use terms; seller's confirmation of export |
| Steady state after integration | Owner named in the combined delegation of authority | Standard data release approvers | Standard release record plus the deal history of the records |
Does the purchase agreement give the records to the buyer, the target or the seller?
Authority follows title, and title follows the transaction structure, so start with the purchase agreement, not the org chart. In a stock or merger transaction where the target survives, the target entity usually keeps its records and its contracts, and its officers, appointed by the new board, approve releases. In an asset purchase, only the assets listed as transferred move, and records tied to excluded assets or excluded liabilities may stay with the seller.
Carve-outs are the hardest case. The divested business's records may be mixed with the seller's other operations in shared systems, and the purchase agreement may allocate some records to the buyer, keep some with the seller and give each party a license to shared material. A dataset built from shared records needs approval from whichever party holds each slice, and sometimes from both.
Records that came from customers carry their own constraints. A customer contract that limits use of its data to providing the service, or that cannot be assigned without consent, binds whoever now holds the records. Check those terms per customer segment before counting the records as available.
Employee records raise a parallel question. Payroll, timekeeping and HR files often move to the acquirer's systems early in integration for practical reasons, but the employing entity, and the notices given to staff, may not change until much later. Treat those records as belonging to the employing entity named in the employment records until counsel confirms otherwise, and keep them out of any dataset that has not been approved separately.
Do the acquired company's privacy promises still govern a release?
Yes. Promises made when data was collected generally travel with the data. In its 2014 letter on Facebook's acquisition of WhatsApp, FTC staff said WhatsApp must keep honoring its privacy promises after the acquisition, and that using data in a way materially inconsistent with those promises would require consumers' affirmative consent first.
California's privacy law reaches the same point by a different route. The CCPA's definition of sell excludes transfers of personal information as an asset in a merger, acquisition or similar transaction, but only if the information is used or shared consistently with the law, and an acquirer that materially changes its practices in a way inconsistent with the promises made at collection must give prior notice.
FTC staff have also warned that adopting more permissive data practices, such as using customer data for AI training, and disclosing the change only through a retroactive edit to the terms or privacy policy may be unfair or deceptive. Another staff post says companies must honor commitments made in terms of service and marketing, not only in privacy policies. For an integration-period release, that means the approver needs the acquired company's notices and customer terms as they stood when the records were collected, not the acquirer's current policy.
What an integration-period release approval should record
An approval made during integration should carry enough history that a reviewer a year later can see why the signer had authority. The fields below extend a normal release record with the deal facts that integration adds.
At a glance
What an integration-period release approval should record
- Records in scope: systems, date range, record types and the entity that held them at collection.
- Transaction structure: stock, merger or asset deal, the closing date, and the purchase agreement clause that allocates these records.
- Phase at approval: which row of the matrix applied, and whether any system was still under a transition services agreement.
- Signer authority: the board resolution or delegation of authority naming the signer, with its effective date.
- Consents: covenant consents before closing, custodian confirmation under a TSA, and any customer or vendor consents.
- Privacy basis: the notices and customer terms in force when the records were collected, and how the proposed use is consistent with them or what notice or consent was obtained.
- Exclusions: records removed because they belong to the seller, excluded assets or customers whose terms forbid the use.
- Open items: anything counsel flagged, with an owner and a date.
Worked example: an acquired field service firm's job records (illustrative)
Illustrative facts only. A regional HVAC services company is acquired in a stock purchase by a larger services group, and the target survives as a subsidiary. Three months after closing, the group's integration team wants to license four years of the subsidiary's job records, work orders, technician notes and equipment histories, for AI training.
Applying the matrix, the phase is closing to entity merger. The subsidiary owns the records, so its officers sign, under a delegation of authority the new board adopted at closing. The integration lead and the subsidiary's privacy owner are consulted. The file holds the board resolution, the share purchase agreement clause confirming no records were carved out, and the subsidiary's customer terms and privacy notice from the collection period.
The exception: one illustrative product line, commercial maintenance contracts for property managers, has customer agreements that restrict use of service data to performing the contract. Those records, roughly 15 percent of the jobs in this example, are excluded unless the customers consent. A second wrinkle would arise if the field service software had been licensed to the seller's parent rather than the subsidiary; the export would then depend on a transition arrangement with the former parent, and the custodian's confirmation would join the file.
Signals that should freeze a release until counsel reviews it
Stop and send the release to counsel when authority, title or permission is unclear rather than guessing. These signals are the common ones.
- The deal has signed but not closed, and the buyer's team is the one asking for the release.
- The purchase agreement does not clearly allocate the records, or they sit in systems shared with the seller.
- The records are on systems run by the seller under a transition services agreement that limits use to operating the business.
- The signer's authority depends on a delegation of authority that has not been adopted yet.
- Customer contracts restrict use of their data, or forbid assignment without consent, and the deal was an asset purchase.
- The acquired company's privacy notice did not contemplate sharing or AI use, and no notice or consent process has been run.
- The records include health, financial or other sensitive categories, or individuals outside the U.S.
Approving a SourceX license from an acquired business
When an acquired business decides to license selected records for AI, the approval questions above come before any data moves. Sourcing, rights review, contracting, preparation and delivery are the parts SourceX runs once such a business chooses to license its operational data directly to SourceX. The company approves the scope and terms and signs the agreement before any data is delivered, so the integration-period approval record becomes part of that rights review.
Eligibility starts with a short company assessment that needs no data upload, which makes it a reasonable step even while the deal history of the records is still being confirmed.
Frequently asked questions
Can the acquirer approve the target's data licenses before closing?
Generally no. The target should keep making its own ordinary-course decisions until closing, and for HSR-reportable deals buyer control of those decisions can be treated as gun-jumping. Any consent the merger agreement requires goes through its formal process with deal counsel.
Who owns the acquired company's records after a stock purchase?
Usually the acquired entity itself, which survives as a subsidiary, so its officers approve releases under the authority the new board grants. The purchase agreement should be checked for any records carved out or allocated elsewhere.
Does a transition services agreement let the seller license the buyer's records?
A TSA usually governs access and services, not ownership, so the seller as custodian should not license records the buyer owns. The buyer approves, and the seller confirms the export within the TSA's terms.
Do the acquired company's privacy promises still apply after the deal?
Generally yes. FTC staff have said acquired companies must keep honoring their privacy promises, and California's privacy law requires use consistent with the law and notice before materially inconsistent changes.
When does a dataset release need the board rather than an officer?
When the company's governing documents or delegation of authority reserve it, or when the release is outside the ordinary course. During integration the delegation may be new or incomplete, so confirm it in writing before signing.
Sources
- The U.S. submission on gun-jumping explains that acquiring beneficial ownership before the HSR waiting period ends is illegal, describes the factors the agencies weigh, and advises each company to keep operating as a separate, independent entity. Source
- FTC guidance says interim conduct provisions requiring buyer approval of ordinary-course decisions can constitute gun-jumping and recommends clean teams and limited information sharing. Source
- FTC staff told Facebook and WhatsApp that WhatsApp must keep honoring its privacy promises after the acquisition and that materially inconsistent use requires affirmative consent. Source
- California Civil Code section 1798.140 excludes merger and acquisition asset transfers from sell when the information is used consistently, and requires prior notice of materially inconsistent changes. Source
- FTC staff say adopting more permissive data practices such as AI training through a surreptitious, retroactive terms change may be unfair or deceptive. Source
- FTC staff say AI companies must honor commitments made in terms of service and promotional materials as well as privacy policies. Source
See if your company qualifies
A short company assessment. No data uploads are needed.