Private equity and portfolios
Can a sponsor use portfolio company data for its own AI tools?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
A sponsor can usually use portfolio company data for its own AI tools only within the purpose its information rights allow, which is typically monitoring the investment. Reusing operating records such as support tickets, CRM notes or job histories to build or train sponsor tools generally needs a separate agreement with the company, and customer contracts may still limit it.
Key takeaways
- Information rights in investment documents usually cover reporting for monitoring purposes, not reuse of operating records.
- Majority ownership gives control of the board, not ownership of the company's records.
- Sponsor AI tools built on operating records generally need a written data use agreement with each company.
- Customer contracts, privacy notices and employee policies bind the company even when it agrees to share.
- Related-party and minority holder approvals may apply when a sponsor draws value from a company's records.
What information rights usually cover#
Information rights usually entitle a sponsor to financial statements, budgets, operating metrics, board materials and access to management, so it can monitor its investment. They appear in shareholder agreements, management rights letters and investor rights agreements.
These clauses typically come with confidentiality terms that limit how the information may be used, often to evaluating, monitoring or managing the investment. The exact words matter, so read the clause itself before assuming that any use beyond reporting is covered.
Lenders receive similar information under the reporting covenants of credit agreements, and those agreements usually limit how lenders may use it. Neither set of rights was drafted with AI tools in mind, which is why reuse of records for model building tends to fall into a gap that only a new agreement closes.
The rule: reporting is not reuse#
The working rule is that reporting is not reuse. A monthly KPI pack sent to the sponsor for monitoring is reporting; pulling a company's support tickets, CRM notes or job records into a sponsor-built AI assistant or model is reuse, and it usually falls outside what information rights were written to cover.
Operating records also carry obligations that summary reports do not. A single support ticket can contain a customer's confidential information and an employee's personal details, so its use is governed by the customer agreement, the privacy notice and employee policies as well as by the investment documents.
Which sponsor uses need a separate agreement?#
Most sponsor AI uses of operating records need a separate written agreement with the portfolio company, and some need more than that. The table sorts common uses by where they usually fall, as a starting point for counsel rather than a conclusion.
| Sponsor use | Where it usually falls | What to put in place |
|---|---|---|
| Dashboards built from monthly reporting packs | Within information rights | Confirm the confidentiality clause covers the tool's hosting |
| Benchmarking KPIs across portfolio companies | Often within rights if aggregated, depending on the confidentiality clause | Aggregation rules, and company consent where unclear |
| AI assistant that answers questions from board materials | Usually within rights | Access controls and a check of the tool provider's data terms |
| AI tool trained or grounded on support tickets or CRM notes | Outside information rights | Data use agreement, customer contract review and privacy review |
| Sharing one company's records with another portfolio company | Outside information rights | Agreements with both companies and a competition law check |
| Licensing records to an outside AI developer | A company decision, not a sponsor use | The company licenses directly, with any sponsor consents |
Cross-portfolio benchmarking: where the line usually sits#
Cross-portfolio benchmarking usually stays on the safe side of the line when it uses reported metrics that companies already send the sponsor, aggregated so no single company or customer can be identified. Comparing gross margin, first-time fix rates or ticket backlog trends across companies is a familiar monitoring activity.
The line moves when benchmarking draws on underlying records instead of reported metrics. Feeding each company's job records or support transcripts into a shared model to compare performance is reuse, and it raises a further issue when two portfolio companies compete, because the model may carry one company's information into answers about the other.
Why customer contracts and privacy laws still apply#
Customer contracts and privacy laws still apply because the portfolio company remains bound by them even when it agrees to share records with its owner. Many B2B customer agreements limit use of customer data to providing the service, and confidentiality clauses may treat the sponsor as a third party.
Privacy laws such as the CCPA may apply where records include personal information about California residents, and they can raise questions about whether the sponsor receives that information as a service provider or as a third party. Employee records add another layer. Counsel assesses these issues deal by deal and record family by record family.
What a sponsor data use agreement should cover#
A sponsor data use agreement sets the terms on which a portfolio company lets its owner use operating records, and it protects both sides if the company is later sold or the sponsor exits.
Keep one agreement per company rather than a single group-wide document. Each company has its own customers, notices and minority holders, and a separate agreement lets one company decline or narrow its scope without holding up the others.
- Purpose: the specific tool or analysis, stated narrowly.
- Records: the record families, systems and date ranges, with excluded customers listed.
- Preparation: how personal and confidential details are removed before transfer.
- Controls: who at the sponsor may access the records, where they are hosted and which AI providers may process them.
- Outputs: who owns models, prompts and results, and whether the company may use them.
- Onward use: no sharing with other portfolio companies or third parties without new consent.
- Exit: deletion or return of records when the company is sold or the agreement ends.
- Approvals: board approval, plus minority holder or independent director sign-off where related-party rules apply.
Illustrative: a holdco general counsel reviews an operations assistant#
Illustrative: a fictional permanent-capital holding company owns six operating companies, including a fleet maintenance software vendor and a packaging distributor. Its operations team wants an AI assistant that answers questions across the group using monthly reporting packs and each company's support ticket history.
The general counsel splits the request. Reporting packs fall within the information rights in each shareholder agreement. Support tickets do not, so each company would need a data use agreement. Two companies' customer agreements limit use of customer communications to service delivery, so their tickets are excluded, and one company with a founder holding a minority stake requires approval from its independent director.
The holdco launches the assistant on reporting packs first and adds ticket history company by company as agreements are signed.
How SourceX keeps sponsor and company roles separate#
SourceX treats the operating company as the supplier in any external license, and a sponsor's internal use of records remains a separate matter between the sponsor and the company. When a company licenses records through the SourceX five-step transaction, the SourceX Evidence Packet records permitted use and release authorization, which helps show that sponsor tools and outside licenses rest on clearly separated rights. SourceX's own rights in a deidentified dataset are set out in the signed supplier agreement.
Where a company both licenses records externally and shares them with its sponsor, the two arrangements should describe the same record families consistently. Mismatched descriptions are the kind of gap an acquirer's counsel tends to find during diligence.
Frequently asked questions
Does majority ownership give the sponsor rights to the records?
Not directly. Shareholders own shares, and the company owns its assets, including its records. Control lets a sponsor shape decisions through the board, but the company still makes them, subject to directors' duties and any protections for minority holders or management equity.
Can the sponsor reuse materials it received during diligence?
Diligence materials are usually received under a confidentiality agreement that limits use to evaluating the transaction. After closing, check whether that agreement still governs, whether information rights replaced it, and whether building tools on those materials needs fresh consent from the company.
Is de-identified data free to use?
De-identification lowers privacy risk, but it does not remove contract or confidentiality limits. A customer agreement that restricts use of customer data may still apply after names are removed, and the standard for what counts as de-identified differs between laws.
Do limited partners have a say in sponsor AI tools?
Sometimes. Limited partnership agreements and side letters can include confidentiality, data protection or responsible investment commitments that reach how the sponsor handles portfolio information. Fund counsel should check them before a tool processes portfolio company records.
Should the sponsor pay the company for using its records?
Where the sponsor gains value from a company's records and minority holders or management also hold equity, an arm's-length arrangement can reduce related-party concerns. Whether a fee is appropriate, and how it is set, is a question for the company's board and counsel.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.