How to tell employees the company is licensing its records to AI developers
Tell employees once the scope and the de-identification and redaction rules are agreed, and before any data preparation starts. In plain words, say which systems and years are licensed, what is excluded, how names and personal details are handled, that the company keeps ownership, and who answers questions. A short note plus a staff FAQ keeps trust concerns from stalling the deal.
The short answer: announce after the rules are set, before preparation begins
Tell employees once the license scope and the de-identification and redaction rules are agreed, and before anyone starts preparing exports. The announcement should name the systems and years being licensed, list what is excluded, explain how names and personal details are handled, confirm that the company keeps ownership of its records, and give one person to ask. Sent at that moment, it describes careful decisions already taken instead of inviting speculation.
Timing is the whole game. Announce too early and you cannot answer the first question anyone asks. Announce after delivery and it reads as concealment. And if IT starts running large exports before anyone has said anything, the rumor will arrive before your note does.
What to settle before you announce
- Scope: the systems and date ranges in the license, for example the ticketing system and project drives from a given year onward
- Exclusions: what stays out, for example HR and payroll files, benefits or medical information, legally privileged material, board papers and direct messages, if those were excluded
- De-identification and redaction rules: agreed with SourceX before any work begins, covering employee names, customer details and free-text fields
- Policies in force: the acceptable use, electronic communications and handbook language employees acknowledged over the period the records cover
- Recorded calls: whether recordings or transcripts are in scope, and what notices callers heard at the time
- Confidentiality: what the agreement allows you to say about the buyer and the price
- Question owner: one named person, for example the head of HR or the CFO
If any box is empty, the note is not ready. The management time guide shows where this work sits in the overall process.
Seven steps to tell employees
- Brief the leadership team first. Everyone who will be asked must give the same answers, so walk them through scope, exclusions and redaction rules.
- Equip managers a day ahead. Give them one page of talking points and the staff FAQ, and tell them where to send questions they cannot answer.
- Send the CEO's note. Email it to all staff and pin it in the main Slack or Teams channel so it is easy to find later.
- Publish the staff FAQ. Put it on the intranet next to the note and update it as new questions come in.
- Hold an open session within a week. Thirty minutes, CEO plus the question owner, with anonymous questions allowed.
- Log every question and act on the useful ones. If a concern reveals sensitive material that should be excluded, raise it with SourceX before exports run.
- Close the loop. When delivery is complete, send a short update confirming what was delivered and that the agreed rules were followed.
The internal note
Adapt this to your company's voice. Keep every factual statement exact.
An operating partner can share this template with a portfolio CEO at the first sign of interest; a CEO who has seen the note early is less likely to treat staff reaction as a reason to stop.
Questions employees ask, and honest answers
| Question | Honest answer to adapt | What not to say |
|---|---|---|
| Will my name appear in the data? | Describe the agreed rule exactly, for example that names are removed or replaced before delivery | Fully anonymous, unless that is precisely what was agreed |
| Are my private messages included? | Say exactly which channels and message types are in scope and which are excluded | Only work stuff, which is too vague to trust |
| Is the company selling our emails? | No: the records are licensed for an agreed purpose and term, and the company keeps ownership | Anything that minimizes what is being licensed |
| Who is the buyer? | Say only what the agreement permits; if the identity is confidential, say so plainly | A guess or a hint |
| Will this be used to replace us? | The license is for AI developers training and evaluating their systems and does not change roles here; discuss any internal AI plans separately | Promises about the future you cannot keep |
| Can I opt out? | Explain what is possible, and invite concerns about specific sensitive content, which can be reviewed before export | A flat yes or no without checking |
| What about colleagues who have left? | The same de-identification rules apply to everyone who appears in the records | Silence |
Common mistakes
| Mistake | Why it hurts | Fix |
|---|---|---|
| Announcing before scope is set | You cannot answer basic questions, so trust drops | Wait until scope and redaction rules are agreed |
| Letting the news leak through IT | Export requests start rumors | Announce before exports begin |
| Vague language such as sharing data | It sounds like selling personal information | Name the systems, years and exclusions |
| Overpromising anonymity | A claim that turns out inexact damages credibility | Describe the actual rules |
| Naming the buyer or the price when the agreement restricts it | It can breach the agreement | Check confidentiality terms first |
| Treating questions as resistance | People stop asking and start assuming | Log and answer each one |
Ownership, privacy and recordings: what to check with counsel
Three legal questions sit underneath most employee concerns.
- Who owns the material. The Copyright Office's circular on works made for hire explains that for a work made for hire the employer, not the individual creator, is the author and owner, and that material an employee creates as part of their job falls into that category. Documents employees write in their jobs therefore generally belong to the company; material from contractors may not, unless it was assigned in writing.
- Personal information. Email and chat contain personal details of employees, customers and contacts. The redaction rules exist to handle this, and counsel should confirm what notices are needed in the states where your employees work, since requirements vary.
- Recorded calls. California Penal Code section 632 prohibits recording a confidential communication without the consent of all parties. If call recordings or transcripts are in scope, check what notices were given when and where the calls were recorded.
This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.
Illustrative example
Illustrative and fictional: a 180-person engineering services firm agrees a license covering its project management system and design-review threads back to 2016, excluding HR files and direct messages. The CEO sends the note on a Tuesday, two weeks before exports are scheduled. At the open session, staff ask three things: whether direct messages are included (no, excluded), whether client names will appear (replaced under the agreed rules), and whether one project lead can flag a folder with sensitive client correspondence (yes; it is reviewed and excluded before export). Exports run on schedule, and the closing update goes out the week after delivery.
Next step
If you are an operating partner, raise the communication plan in the same conversation as the license itself; the guide on explaining company data licensing to a founder helps with that first discussion. Platforms built by acquisition should also read whether records from before an add-on deal can be licensed, because staff who joined through add-ons will ask about their old company's files. For a portfolio-wide view of where licensing fits in a long hold, see the guide on extended PE hold periods and the operating partner referral page.
Partners never handle the records; they make the introduction. Partners earn 25% of the eligible platform fees SourceX collects from the referred company's licensing deals, capped at $100,000 per referred company, paid only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. Before raising any of this, run the company through the company fit checker. To introduce a portfolio company, register as a partner, or have the CEO apply at sourcex.si/apply.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Do we need employee consent to license company email and chat?
It depends on what employees were told, where they work and what is in scope, so ask counsel rather than assuming either way. Check whether your acceptable use and electronic communications policies say work systems and messages belong to the company, and make sure the redaction rules cover personal details. Clear communication matters even where formal consent is not required.
Should we tell employees which AI developer is licensing the data?
Say only what the signed agreement allows. If the buyer's identity is confidential, tell staff that plainly rather than hinting, and describe the purpose instead: training and evaluating AI systems under an agreed license. Keep the focus on what staff can check for themselves: what is included, how personal details are handled and whether anything changes for their roles.
Can an individual employee ask for their messages to be excluded?
They can ask, and the company should take the request seriously. Whether a specific exclusion is possible depends on the agreed scope and on what the content is. Requests that point to genuinely sensitive material, such as personal health matters or confidential client correspondence, are worth reviewing before export, and the outcome should be explained to the employee.
What about records involving former employees?
Archives include people who have left, and they cannot easily be reached individually. The agreed de-identification and redaction rules apply to everyone who appears in the records, current or former. Ask counsel whether any additional notice is appropriate, and make sure your FAQ answers the question, because current staff will ask on behalf of former colleagues.
When should employees hear about a license if the company is also being sold?
Coordinate with the deal team first, since a sale process has its own confidentiality rules and communication plan. The license announcement must not reveal the sale before the deal team is ready. If both will become public, consider whether one combined message is clearer than two, and keep the license note factual about scope, exclusions and redaction rules either way.
Related pages
- How much management time does a data license take from a portfolio company?
- How to explain company data licensing to a US founder
- Can an acquired company license its pre-acquisition records, and who signs?
- Longer hold periods in private equity: how to keep creating value when the exit slips
- Referral opportunities for private equity operating partners
- Check Company Fit for Data Licensing
Free resources
- Cash conversion cycle calculator — DIO, DSO, DPO and the cash conversion cycle.
- Operational data inventory builder — List systems, record types, years held and owners.
- AI readiness assessment — Ten questions, five dimensions, a score out of 100.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment