Can a Company License Employee Emails and Slack for AI Training?

Usually yes: a US company generally owns the email and chat its staff produce at work and may access them on its own systems, so ownership is rarely the obstacle. The obstacles are the people and promises inside the messages. California staff have had full privacy rights over their work data since the state's employee exemption became inoperative on 1 January 2023; customers, job candidates and vendors in the threads never agreed to anything; privileged legal advice and other companies' confidential information sit in the same mailboxes; and the software vendors' terms decide how the data may leave their systems. Buyers want these records badly: one buyer's revenue chief said that if a company will not sell its Slack, CRM or email records, "the rest of the corpus is less valuable". The workable answer is to license a de-identified copy, exported with each system's own admin tool, after the material that cannot be licensed has been taken out.

This guide is for the founder, CEO, general counsel or head of people at a US company deciding whether to license its internal communications (email, Slack, Microsoft Teams, meeting recordings) to an AI buyer. It covers who owns business communications, the federal wiretap and stored communications laws, monitoring notices and the state laws that require them, California's treatment of employee data, the third parties inside the messages, the privileged and confidential material that must come out, the vendors' terms on exports and AI training, and de-identification. It ends with a worked example and the questions people ask most.

This guide is research from public sources, not legal advice.

Contents

1. Who owns business communications
2. Federal law: the Wiretap Act and the Stored Communications Act
3. Monitoring notices and the state laws that require them
4. California: employee data under the CCPA
5. The third parties inside the messages
6. Privileged and confidential material that must come out
7. Your software vendors' terms
8. De-identification
9. Worked example: an accounting firm's email and Teams
10. Questions people ask
11. What this means for you

1. Who owns business communications

Start with ownership, because holders often assume it is the hard part, and it usually is not. Under US copyright law, a work " prepared by an employee within the scope of his or her employment" is a work made for hire, and in that case the employer " is considered the author" and owns all the rights in the copyright unless a signed agreement says otherwise. The emails, documents, wiki pages and code your staff produce as part of their jobs are, as a matter of copyright, the company's. Contractors are different: their work belongs to them unless a written agreement assigns it, so a holder should check that every contractor and agency signed an assignment and list and exclude the gaps.

The software vendors confirm the same thing from their side. Microsoft's data protection terms say that " as between the parties, Customer retains all right, title and interest in and to Customer Data"; Zoom's terms say you retain all ownership rights in your Customer Content; GitHub's say " You own Your Content". The customer in each case is the company that holds the subscription, not the individual employee. So a company that pays for Slack, Microsoft 365 or Google Workspace is, as between itself and the vendor, the owner of what its workspace holds.

Ownership settles less than it seems, for two reasons. First, owning the copyright in a message does not give the company rights over the personal information in it (a colleague's health, a customer's address) or over other companies' confidential information that was shared under an NDA. Those are governed by privacy law and contract, and they are what the rest of this guide is about. Second, ownership only reaches records the company actually holds in its own systems. Messages staff sent from personal accounts, copies a former employee kept, or an archive someone offers you from outside are not yours to license. Buyers have learned this the hard way: one AI vendor's head of environments described being offered a large company's codebase for millions of dollars by a group that "did not have the rights to sell this data". Show title by exporting from your own systems, with your own administrators, and keep the record of how you did it.

2. Federal law: the Wiretap Act and the Stored Communications Act

The federal Electronic Communications Privacy Act has two parts that matter here. The Wiretap Act governs communications captured in transit. It makes it an offense to intentionally intercept an email or chat message, and separately to disclose or use the contents of a communication knowing or having reason to know that it was obtained through an unlawful interception. The Stored Communications Act governs messages at rest on a service. It is an offense to access stored communications without authorization, or by exceeding an authorization. Licensing an archive that already sits in your mail or chat system is a stored-communications question, not an interception one.

The Stored Communications Act carries the exception that makes a company's own export lawful. Its access offense does not apply to conduct authorized " by the person or entity providing a wire or electronic communications service", or by a user for messages to or from that user. A company that provides email or chat to its own staff can authorize access to what is stored on that system; where the system is hosted by Microsoft, Google or Slack, the company exports under its contract with the vendor, through the vendor's own admin tools. The Act's ban on divulging stored contents applies only to a provider of service " to the public". A company's internal system is generally not a public service, so that ban does not itself stop the company from licensing its records; it does bind the hosting vendor, which may disclose contents only within the Act's exceptions, such as the lawful consent of the originator or an addressee, and is one reason vendors release data only to the customer's administrators.

Two exceptions are often misread as broader than they are. The Wiretap Act's provider exception lets a service provider's staff intercept, disclose or use communications in the normal course of employment when the activity is a necessary incident to providing the service or protecting the provider's rights or property. Licensing staff messages for revenue is neither, so a company should not rest an AI licence on it. The one-party consent rule says interception is lawful where one of the parties to the communication has given prior consent, unless the purpose is criminal or tortious. An employee's consent speaks only for that employee: the customer, candidate or vendor on the other end of the thread has not consented, and some states require every party's consent (section 3).

The practical upshot is a clear method. Export each system with its own built-in admin export, run by your own administrator, from systems your company controls. Never collect from staff's personal accounts or devices, never let a buyer install a connector that reads live traffic, and keep a written record of who exported what, when, and how. That method answers the federal statutes and also, as section 7 shows, the vendors' terms.

3. Monitoring notices and the state laws that require them

Most companies already tell staff, in an acceptable-use policy or handbook, that work systems belong to the company and may be monitored. Those notices matter for an AI licence in two ways. They are evidence that staff had no reasonable expectation of privacy in work messages, and of the company's authority over its systems. But they were almost always written for security, compliance and investigations, not for licensing the content to a third party. A notice that says "we may review your email to protect our systems" does not tell anyone their messages may be sold. Read yours for what it actually says, and treat it as one input, not as consent to an AI licence.

At least four states go further and require employers to give notice before monitoring employees' electronic communications. Pulling every mailbox into an export and reviewing it to build a training set is at least close to monitoring, so a holder in these states should confirm that the required notices exist and were given. These laws govern notice, not licensing: they do not make a licence lawful or unlawful on their own. But a company that never gave a required notice has a weaker answer to every later question about its staff's expectations.

Recorded calls and meetings

Recordings are a separate and stricter problem. Federal law follows the one-party rule described above, but California, among other states, makes it an offense to record a confidential communication " without the consent of all parties". A meeting recording or call transcript in which a customer or candidate took part, recorded under a one-party notice, may not satisfy an all-party state, and even where the recording was lawful the consent usually covered the meeting, not a later licence. The safe course for an AI lot is to exclude recordings with outside participants, or obtain their consent, and to treat internal recordings as needing the same notice and de-identification as the rest. Voices raise one more issue: a voiceprint is a biometric identifier under Illinois' biometric privacy law, covered in the general privacy guide.

Union and workplace discussions

Staff conversations about pay, working conditions or organising are protected concerted activity under section 7 of the National Labor Relations Act. In 2022 the Labor Board's General Counsel announced a plan to protect employees " from intrusive or abusive electronic monitoring"; that memo was rescinded in February 2025, so it is history rather than current enforcement policy. Section 7 itself has not changed. The rights questions buyers' counsel ask take the cautious line: union and HR channels and any discussion of pay or conditions are excluded, and any collective bargaining agreement is checked for data and monitoring clauses.

4. California: employee data under the CCPA

California is where employee messages stop being an internal matter. Until the end of 2022, the California Consumer Privacy Act exempted personal information collected about job applicants, employees, owners, directors, officers and contractors in that role. The exemption "shall become inoperative on January 1, 2023", and it did. The state's privacy agency says plainly that consumers include " California residents that are employees or job applicants, and contacts for business customers, vendors, or independent contractors", and that the employee exemptions expired on 31 December 2022. A California employee's name, email address, messages and anything they reveal about themselves at work are personal information like any consumer's.

That has direct consequences for a licence. Licensing personal information to a third party for money or other valuable consideration is a sale under the Act's definition, "for monetary or other valuable consideration", which brings the duty to give notice before selling and the right to opt out. And the Act treats " the contents of a consumer's mail, email, and text messages unless the business is the intended recipient of the communication" as sensitive personal information. Whether an employer counts as the intended recipient of messages its staff exchange is not settled. Messages between staff and outsiders, and personal messages sent through work tools (to a doctor, a family member, a lawyer), are where the line falls hardest. Former employees count as much as current ones: their messages are still personal information about them.

For a California-covered company there are two workable routes. One is to give every current and former California employee notice and an opt-out before any sale, then remove those who opt out. The other, which most holders choose, is to remove employee personal information to the CCPA's deidentified standard: reasonable technical measures, a public commitment not to re-identify, and contracts obliging every recipient to the same. De-identified information is not personal information under the Act, so the sale rules do not attach to it. The other state privacy laws generally exclude people acting in an employment or commercial context, so California is usually the binding state for staff data; the general guide has the state-by-state table. If you have staff in the EU or UK, the European rules are stricter still: consent from employees is rarely valid given the dependency of the employment relationship, and only truly anonymous data leaves the GDPR's scope.

5. The third parties inside the messages

A company's email and chat are full of people who are not its employees and never agreed to anything: customers writing to support, job candidates in recruiting threads, vendors and partners negotiating contracts, friends and family in the odd personal message. Each of them has their own privacy position. A customer in California is a consumer under the state's privacy law; a candidate is a job applicant, whom California covers as well; a business customer's employee is a business contact, also covered in California since 2023. None of them gave the company any permission beyond the conversation they were having.

The harder problem is often not personal information but other companies' information. A shared Slack channel with a partner, an email thread with a supplier's engineers, a customer's contract under negotiation: each can contain information the company received under a confidentiality agreement that limits its use to the relationship. Buyers' counsel ask whether shared channels, external threads, partner folders and third-party attachments are excluded or reviewed, and whether the holder can list which counterparties appear. If the business is a service provider to other businesses, the customer content in its messages raises the contract problem described in the general guide as well.

The Spirit Airlines records sale shows how this plays out when it is not handled first. Spirit's archive included about 100 million emails across its staff's mailboxes. After the auction, vendors objected that their own data inside Spirit's email, Teams and SharePoint was not estate property, and several moved to enforce their confidentiality agreements. Employees' advocates objected too, and 119 members of Congress asked Spirit and Google to halt the transfer of former employees' data until protections were in place. The court-appointed privacy ombudsman had looked only at consumers: she wrote that she did not investigate or reach any conclusion about risks to employees or third parties. The sale hearing, first set for August, has been adjourned five times. A holder outside bankruptcy has no ombudsman and no court to resolve these objections; it has to solve them before the licence, or face them as claims after it.

6. Privileged and confidential material that must come out

Some material cannot be fixed by removing names, because the problem is the content itself. It has to be found and excluded before anything leaves, and buyers increasingly expect it. The Spirit sale agreement, for example, states that the assets " shall not include any communications, documents, or other information protected by any attorney-client privilege", and requires the buyer to return or destroy anything privileged that slips through. One law firm advising holders puts it bluntly: exclude high-risk data entirely rather than relying on de-identification, including privileged, HR, payroll, health, union and customer-confidential material.

Privilege deserves the most care, because the damage is permanent. Communications between the company and its lawyers for legal advice are protected only while they stay confidential, and a voluntary disclosure to a licensee is the kind of disclosure that waives protection. The federal rule that rescues mistakes is narrow: it protects only an inadvertent disclosure made in a federal proceeding or to a federal office or agency, where the holder took reasonable steps to prevent it and to fix it. A commercial transfer of mailboxes to an AI buyer is neither. If privileged advice about a dispute ends up in a training set, the other side in that dispute may argue privilege is gone.

Your own trade secrets are a business decision rather than a legal bar. A licence of de-identified records still teaches a model how your company works, and a buyer may resell or sublicense what it builds. Decide what you are willing to have learned, exclude the rest, and restrict the buyer's use in the licence where you keep material in ( the rights question buyers' counsel ask covers both).

7. Your software vendors' terms

Your vendors' terms add a contract layer between your company and its own data. As section 1 showed, the vendors agree the content is yours. What they control is how it leaves. The general pattern across the systems we track is consistent: of the 18 business systems whose terms were read, 13 let the customer export its own data freely, while 6 bar using data pulled through their APIs to train AI models. The difference is the route. An export run by your own administrator with the vendor's built-in tool is your own data leaving your own account. An app or connector pulling through the API is governed by developer terms that, increasingly, forbid AI training outright.

Two vendor issues catch holders late. The first is timing: when a company winds down and stops paying, the vendors delete. Microsoft deletes a cancelled subscription's data within 180 days at most, a Slack workspace downgraded to the free plan keeps one year of history, on a rolling basis, and Google Workspace offers no recovery window once an account is cancelled. The deletion clock shows the dates for each system. The second is prior training by the vendor itself: some vendors already learn from customer content or metadata (Atlassian's metadata contribution, for instance, is always on below its Enterprise plan, per its own trust page). A holder cannot promise a buyer exclusivity over patterns a vendor has already learned, so list each vendor's AI setting and when it was switched off.

8. De-identification

Once the material that cannot be licensed is out, de-identification deals with the people who remain. For messages it means more than deleting names. Names appear in greetings, signatures, @mentions, nicknames and email addresses; people are identifiable from roles ("our only Denver office manager"), from events ("back from her surgery"), and from combinations of ordinary details. A useful scrub finds every person the export itself lists (senders, recipients, channel members), finds them wherever they are mentioned, replaces each consistently with a stand-in so the threads still make sense, screens content for sensitive topics, and then tests the result as an attacker would. Content screening matters as much as name removal: records about health, beliefs, finances, HR matters and legal advice are flagged for a person to read, not removed by guesswork.

Done to the California standard, de-identification takes employee and third-party personal information outside the state's privacy law, and it is what the market's reference transaction used. In the Spirit sale, the estate and Google " voluntarily agreed to follow the deidentification standard adopted in the California Consumer Privacy Act", with an independent agent de-identifying corporate email and certifying each transfer to the court. Who does the work is a negotiated term: some buyers de-identify inside your environment before anything is extracted, others do it on their own systems, and the holder who chooses the provider and sees the test result before anything leaves is the one who can stand behind its warranties.

De-identification has limits that matter more for communications than for any other record type. It does not cure privilege (the waiver problem is about content, not names), it does not cure confidentiality agreements (another company's pricing is still its pricing without a name on it), and it does not cure recording consent (the problem is how the recording was made). That is why the order of work is exclusion first, then de-identification, then testing. Our de-identification standard sets out how each step is done and checked, and the de-identification tool runs on your own computer, so the original records never leave it.

9. Worked example: an accounting firm's email and Teams

Example (illustrative, not a real firm). An 80-person accounting and advisory firm has offices in New York and Connecticut and four remote staff in California. It runs on Microsoft 365 (Outlook, Teams, SharePoint) and has a small Slack workspace for its internal software team. A buyer has offered to license ten years of its email and Teams, and law and accounting are among the fields where buyers report especially high demand.

Ownership and export. The work product of employees is the firm's; three former contract bookkeepers signed engagement letters without an assignment clause, so their documents are listed and excluded. Microsoft's terms confirm the firm owns its customer data and can extract it during the subscription, so the firm's own administrator runs the export with Microsoft's built-in tools. The buyer's offer to "connect and pull it for you" through an app is declined.

Notices. New York has required acknowledged monitoring notices since 2022; the firm has given them since its handbook update that year, but staff hired before then signed the old handbook, so it confirms acknowledgments exist for everyone. Connecticut's amended notice law took effect on 1 October 2026, and the firm updates its posting to say where monitoring occurs. Neither notice mentions licensing content, so the firm treats them as a precondition, not as consent.

California and the third parties. The four California employees, and California-resident clients, are consumers under the state's privacy law, so the firm chooses to de-identify all personal information to the California standard rather than run a notice and opt-out. The firm's clients are the bigger issue: client emails carry tax return information, and a tax preparer that discloses information furnished for preparing a return, or uses it for any other purpose, commits a federal misdemeanor absent an exception or the client's specific consent. Every client-matter folder, every thread with a client domain, and every attachment containing return data is excluded. What remains is the firm's internal operating history: how engagements were staffed, scheduled, reviewed, escalated and closed.

Privilege and confidentiality. Threads with the firm's outside counsel, and a folder from a malpractice claim, are excluded. Engagement letters with clients contain confidentiality clauses; client confidential information is already out with the client folders. Teams meeting recordings with clients are excluded entirely; internal recordings are excluded because the firm's notice covered meetings, not licensing.

Result. The lot is the firm's internal email and Teams, without client matters, legal advice, HR, health and recordings, de-identified and tested by a provider the firm chose, with a licence that binds the buyer not to re-identify, gives knowledge-qualified warranties tied to the firm's rights file, and restricts use of what remains. It is smaller than "ten years of email", and it is the part that can be licensed.

Questions people ask

Can a company use employee emails for AI training? For its own internal AI use, a company that owns its systems and has given proper notices is on firmer ground; licensing them to an outside buyer needs more. The company generally owns its staff's work product, but it must deal with California employees' privacy rights (in force since the employee exemption became inoperative on 1 January 2023), the outside parties in the messages, privilege and vendor terms. A de-identified copy, with the high-risk material excluded, is how most holders do it.

Do employees have to consent? Federal law does not generally require each employee's consent for a company to access stored messages on its own system, which the Stored Communications Act's provider exception covers. But in California, licensing employees' personal information is a sale requiring notice and an opt-out unless it is de-identified, and in the EU and UK employee consent is rarely valid at all. Notice laws in New York, Connecticut, Delaware and Maine also apply to monitoring.

Does the company own its employees' Slack messages? As a matter of copyright, work produced within the scope of employment is a work made for hire owned by the employer, and Slack's customer is the company. That does not give the company rights over the personal information or third-party confidential information inside the messages.

Is it legal to sell Slack data? It can be, if you export it yourself through Slack's own admin export rather than an API app (Slack's API terms bar using API data to train a large language model), exclude privileged, HR and partner material, and de-identify the rest. Private channels and direct messages need the higher-plan export.

What about former employees' emails? They are treated like current employees' messages. In California, former staff remain consumers whose personal information is in the records, and their old mailboxes often hold more sensitive material (departure discussions, disputes) than current ones, so screen them with particular care.

Can my company license recorded meetings and calls? Treat them as the hardest category. California and other all-party consent states make recording a confidential communication without everyone's consent an offense, and even lawful recordings were usually consented to for the meeting, not for a licence. Exclude recordings with outside participants unless they consent.

What this means for you

If you are considering licensing your company's internal communications, work in this order. First, confirm title: export from your own systems with each vendor's own admin tool, list contractors without assignments, and refuse any archive that did not come from your systems. Second, check notices: your handbook and acceptable-use policy, and the state monitoring notices if you have staff in New York, Connecticut, Delaware or Maine. Third, exclude privileged material, other companies' confidential information, HR, health, union, regulated client data and recordings with outsiders. Fourth, de-identify the rest to the California standard and test it before anything leaves. Fifth, write it down in a rights file your warranties can rest on.

The readiness tool walks through the rights questions in order, the rights hub explains each one and links every system's page, and the licence terms page shows the clauses buyers propose. To see what your records might fetch, start with a valuation, and read what sells for why communications are the part buyers value most. AIData.Broker acts as the holder's agent in these sales: the holder licenses its own records to the buyer, and we settle the rights file with the holder before any buyer sees anything. For related questions, see is it legal to sell customer data?, selling customer data in bankruptcy, what a data licensing agreement contains and the selling guide.