What conflicts arise when a portfolio company's sister company could license its data?

The short answer: treat it as a related-party deal

If one sponsor controls both a company that holds valuable records and a company that builds AI, any license between them is a related-party transaction, even when the price looks fair. The fund's conflict obligations to its limited partners apply, and so do the licensing company's duties to its minority holders, lenders and customers.

The decision belongs to the licensing company's board, advised by its own counsel. The operating partner's job is to spot the conflict early, get it written down and keep the process clean, whether or not the affiliate ends up as the licensee.

The situation is becoming more common. McKinsey's Global Private Markets Report 2026 reports that sponsors are applying AI to operating levers and have more than doubled their operating groups since 2021, so a single portfolio can hold both a records-rich services business and an AI-native one.

Who sits on each side of the conflict

Which documents govern it

Three sets of documents usually decide how the transaction must be handled. Drafting varies, so read the actual text.

• Fund documents. Many limited partnership agreements require disclosure of affiliated transactions and, for deals between funds or with affiliates, review by the LP advisory committee. The GP's chief compliance officer or fund counsel can confirm what yours requires.
• Portfolio company governance. Charters, stockholders agreements and board policies often require related-party transactions to be approved by disinterested directors or consented to by minority holders.
• Credit agreements. Leveraged loans commonly include an affiliate-transactions covenant allowing dealings with affiliates only on terms no less favorable than an arm's-length deal, sometimes with a board certification above a set size.

The licensing company's customer contracts and privacy commitments sit beside these. FTC staff have stated that companies' promises not to use customer data for undisclosed purposes, such as training models, are enforceable, whether made in a privacy policy, terms of service or marketing. That is staff guidance rather than a rule, but it is a reason to check what the company promised before any records reach an AI developer, affiliated or not.

This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

The four-document conflict file

Before the board votes, the file should show four things. If any one is missing, pause the process.

• Disclosure memo: who controls each company, which funds own them, who sits on both boards and who could gain.
• Independent price evidence: a price discovered through review by unaffiliated AI labs and data buyers, or an outside valuation, rather than a number set between affiliates.
• Disinterested approval: board minutes showing that directors without a stake in the AI company approved the terms, with conflicted directors recused.
• Required consents: LP advisory committee, minority holder and lender consents wherever the documents call for them.

Competitive review strengthens the second item. Through SourceX, the licensing company agrees price and terms first, then AI labs and data buyers review the opportunity; once a company is deal-ready, buyers typically respond within about two weeks. A price tested that way is easier to defend than one negotiated inside the portfolio.

Exclusivity cuts both ways

Deals are typically exclusive for AI training for an agreed term. If the licensing company grants exclusivity to an outside buyer, the sister AI company cannot train on the same records during that term. If the sister company takes exclusivity, outside buyers are shut out and the price has to stand on its own. Either way, the board should record why the chosen licensee and term serve the licensing company rather than the portfolio as a whole.

The same logic applies when the common owner is a lender group rather than a fund; see who approves a data license at a lender-owned company. If either company is public or sits under a public parent, disclosure obligations widen; see whether a public company or its subsidiary can license data.

What to say to the deal team

What it means for an operating partner who refers

You can introduce the licensing company and still keep the conflict managed. Check your firm's policy on fees connected to portfolio companies before you register, and disclose the referral relationship to the board. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, payable only after the buyer pays and SourceX receives its fee; the rewards page has the details. The reward is a share of SourceX's fee and never reduces what the company receives, but a director voting on the license should still recuse if they stand to gain from it.

When to stop

• The AI company already has informal access to the licensing company's records through shared services.
• Customer contracts or privacy commitments rule out using the data for AI training.
• The fund documents require LP advisory committee consent and the GP will not seek it.
• The board cannot find directors without a stake on both sides.

Next step

Screen the licensing company with the company fit checker and the who qualifies baseline, then read the operating partner referral guide for raising licensing across a portfolio. Once the conflict file is in order, register as a partner and make the introduction.