A company can license its Slack data for AI training only as far as its Slack plan lets it export the data and Slack's terms allow the route it uses. Private channels and direct messages export only on Business+ and Enterprise, and Slack's API Terms bar outside apps from training a large language model on API Data (export help page checked November 9, 2026; API Terms effective October 10, 2025).
A Slack export is one input to AI training data licensing, where a license is one outcome and keeping the archive is another. Not licensing is a valid result.
Each plan limit, term date and program ask below comes from Slack's or the program's own page and carries its check date; the DataPacts Editorial Team explains how we source, date and check every figure.
What Licensing Slack Data for AI Training Involves
Licensing Slack data means granting an AI developer, or a vendor that supplies one, the right to train on an exported copy of the workspace's messages, while the company keeps its own copy. Slack Technologies, LLC, a Salesforce company, runs Slack, and its terms set what can leave a workspace.
Slack is a common source in the programs that ask for company data. Mercor's Brendan Foody, who describes himself as its CEO, states that Slack appears at 55 % of the more than 300 enterprises Mercor works with, ahead of GitHub and Google Drive at 53 % each (LinkedIn post, checked November 9, 2026). SimpleClosure, a shutdown service, states that 95 % of the workspaces on its AssetHub include Slack (published September 3, 2026, checked November 9, 2026).
Chat as a data type, across Slack, Teams and Google Chat, is covered under selling chat messages for AI training. This page stays on what is specific to Slack: plan limits, Slack's terms and the programs that name it.
What Each Slack Plan Lets an Owner Export
Slack's export scope depends on the plan, and only Business+ and Enterprise reach private channels and direct messages. The table compares the four plans as of November 9, 2026, from Slack's help pages.
| Plan | Public channels | Private channels and DMs | Route | Notes | Source |
|---|---|---|---|---|---|
| Free | yes, messages and file links | no; private Salesforce channels by application | standard export | file links only from the last 90 days; history older than one year deleted from 2024-08-26 | slack.com help 201658943; help 29414264463635 |
| Pro | yes | no; private Salesforce channels by application | standard export | none recorded | slack.com help 201658943 |
| Business+ | yes | yes, by application | Workspace Primary Owner approves; described as for legal and regulatory compliance | none recorded | slack.com help 201658943 |
| Enterprise | yes | yes, after Org Owners contact Support to enable self-serve export | Org Owners via Support | by conversation type, member or workspace; JSON or TXT | slack.com help 201658943 |
Public Channels on Free and Pro
Free and Pro workspaces export public channel messages and file links, and nothing from other private channels or direct messages. On Free, file links reach back only 90 days from the export. Both plans have one narrow route that Slack's help page describes, private Salesforce channels by application, which does not extend to other private channels or to direct messages.
A license built on a Free or Pro workspace therefore covers public channel messages and no direct messages.
Private Channels and Direct Messages on Business+ and Enterprise
Private channels and direct messages leave Slack only through an approved export on Business+ or a Support-enabled export on Enterprise.
- Business+: Workspace Owners apply, and the Workspace Primary Owner approves; Slack's help page describes the purpose as legal and regulatory compliance.
- Enterprise: Org Owners contact Support to enable self-serve export, which then runs by conversation type, member or workspace, in JSON or TXT.
This page does not state whether Slack accepts a Business+ application made for a data license. The Primary Owner's approval is in practice the first internal decision point.
Message History, File Links and Export Formats
An export holds only the history the workspace still has, and Slack's help page describes exports as containing file links. On Free workspaces, Slack began deleting history older than one year on August 26, 2024, which caps a Free archive at about a year of messages.
The help page names file links, and this page therefore does not claim that attached files travel with an export. Enterprise exports come as JSON or TXT.
Slack API Terms and LLM Training
Slack's API Terms govern apps that read Slack through its API, and since 2025 they bar apps offered outside the organization from training a large language model on that data. The change has a dated timeline.
What the API Terms Prohibit for Outside Apps
Two rules apply to apps distributed outside the organization: no training of a large language model on API Data, and no bulk export unless an additional agreement allows it. The API Terms state that such apps "must not… use API Data to train a large language model", and a company weighing a license needs the rights audit for data you want to license to place platform terms among its other obligations.
- LLM training: prohibited for outside apps, effective October 10, 2025.
- Bulk export: prohibited for outside apps except where an additional agreement expressly allows it.
The API Terms cover access through the API. They do not describe the workspace export tool, and this page does not state what Slack's customer agreement says about relicensing exported content.
When the API Terms Changed
Slack announced the change on May 29, 2025, applied it to new apps at once and to existing apps from June 30, 2025, and the current API Terms are effective October 10, 2025. Slack's Supplemental Terms were last updated on February 27, 2026, as of November 9, 2026.
Connector Access by Data Programs Under the API Terms
Some data programs connect to a company's systems instead of receiving an export, and a connection that reads Slack through the API runs into the API Terms. Centific states it connects in-scope systems read-only, Mercor lists a "Connect" step, Scale AI states it anonymizes inside the company's environment before extraction, and Avelence states no default system access (all checked November 9, 2026). The comparison of buyer connectors vs native exports sets out how these routes differ.
No Slack statement says whether a given program's connector is an app distributed outside the organization or holds an additional agreement, so a seller asks the program in writing.
Slack's Own AI Policy vs a Company Licensing Its Workspace
Slack's own policy on training AI with customer data is a separate question from a company's decision to license its workspace to an AI developer. Slack states that it does not train generative AI models on Customer Data without affirmative opt-in consent (privacy principles, checked November 9, 2026); that is Slack's claim about its own conduct.
Slack's policy does not decide whether a company may license its exported messages. Settings that let users and workspaces stay out of Slack's own AI features are covered under opting out of AI training, which this page does not repeat.
Data Programs That Ask for Slack Data
Fourteen programs on record name Slack among the data they ask for, each listed here with its role and the date its page was checked. The table is alphabetical, carries no payout figures, and shows each program's own wording as of November 9, 2026.
| Program | Role | What it states it asks for | One published term relevant to Slack data | Checked | Source |
|---|---|---|---|---|---|
| Avelence seller advisory | intermediary (broker) | "Slack/Teams" | de-identification on a separate copy; no default system access | 2026-11-09 | avelence.com |
| Centific Enterprise Data | data vendor | "email, calendar, Teams, Slack, Google Chat" | 188 supported applications; read-only connection to in-scope systems | 2026-11-09 | centific.com/enterprise-data |
| Collinear AI paid data licensing | RL-environment builder | "Slack" | teams of about 50+; one-time snapshot; seller keeps ownership | 2026-11-09 | collinear.ai/data-acquisition |
| Handshake AI Data Partnerships | human-data platform | Slack among sources named, "+1K more" | "All data is scoped, de-identified, and confidential" | 2026-11-09 | joinhandshake.com/ai/data-partnerships |
| Labelbox Prism | data vendor | "cross-system interaction data (Salesforce, Jira, Slack)" | exclusive by default; distressed and wound-down companies eligible | 2026-11-09 | prism.labelbox.com/faq |
| Mercor Data Monetization | human-data platform | "Slack" among 100+ supported tools | Connect step; automated extraction and de-identification | 2026-11-09 | mercor.com/data |
| Nyne data partnerships | data vendor | "chat (Slack, Teams, Google Chat)" | 20+ full-time U.S. W-2 employees, 3+ years | 2026-11-09 | nyne.ai/data-partnerships |
| Ooak Data partner program | RL-environment builder | "Slack" | raw data deleted within 30 days of delivery | 2026-11-09 | ooakdata.com/partner |
| Polyshares data licensing | data vendor | "Slack and Teams" | "defined term" on the home page vs "Perpetual exclusive license" in its track record | 2026-11-09 | polyshares.com |
| Scale Data Partnerships | human-data platform | "chat (Slack, Teams, Google Chat)" | anonymizes inside the company's environment before extraction | 2026-11-09 | scale.com/data-partnership |
| SimpleClosure AssetHub | intermediary (shutdown service) | "WorkspaceData (Slack, Google Drive, email, Notion, Figma)" | sensitive employee, compensation, health and personal information excluded | 2026-11-09 | simpleclosure.com/product/assethub |
| SuperAnnotate Data Partnerships | human-data platform | "Slack threads, email chains, handover notes" | "licensing rights for a set period, not selling the data" | 2026-11-09 | superannotate.com/data-partnerships |
| The Corner (micro1 referral page) | intermediary (referral) | closed companies with "substantial Slack or Teams history" | raw data kept at most 180 days, then deleted | 2026-11-09 | thecorner.ai/data/partnerships |
| Turing Project Lazarus | human-data platform | Slack among selectable systems, under "How your team communicated" | non-exclusive; 90-day Turing-only selling window | 2026-11-09 | lazarus.turing.com |
Intermediaries place or refer data and do not acquire it.
Payment timing and exclusivity differ between programs. Mercor states payout by wire typically within 2 to 4 weeks of the signed agreement, Turing states a 90-day window in which it alone sells the record, and Labelbox Prism is exclusive by default. Polyshares shows two wordings on its own pages, "defined term" and "Perpetual exclusive license", so a seller asks which applies. Payouts sit with AI data partnership payouts and program terms compared, each dated.
Staff Messages and Customer Content in a Slack Archive
A Slack archive holds staff direct messages and often messages from customers and other outside people, and exporting them is not the same as having a basis to license them.
SimpleClosure states that its AssetHub excludes sensitive employee, compensation, health and personal information. Slack's help pages in the record do not say how messages from other organizations in shared channels export, so this page does not describe that case.
The steps for staff are set out under employee notice and consent when licensing internal communications.
Benefits, Risks, Downsides and Alternatives of Licensing Slack Data
Licensing Slack data can turn a dormant archive into license income, and it also exposes staff and customer messages that cannot be recalled once a model has trained on them.
- Benefits:
- A dormant archive can earn license income; SimpleClosure states that startup assets typically sell for tens of thousands to hundreds of thousands of USD (September 3, 2026, an intermediary's range claim, not a price for Slack data).
- A time-limited, non-exclusive license leaves the company free to use its own copy.
- Risks:
- Labelbox Prism states that models already trained on the data cannot be unlearned, so a license cannot be reversed in practice.
- Staff and customer messages can carry personal data and confidentiality duties.
- Bulk export through the API is barred for outside apps without an additional agreement with Slack.
- Downsides:
- Only Business+ and Enterprise reach private channels and direct messages, so the richest material may be out of reach on other plans.
- De-identification, rights review and staff steps take time before any buyer sees a sample.
- Alternatives:
- Not licensing, and keeping the archive for internal use.
- Licensing public channels only.
- A time-limited, non-exclusive license.
- Commissioning or supplying a Slack replica for an RL environment instead of the messages.
No option is a default; the choice depends on the plan, the rights audit and tolerance for an irreversible grant.
Where Slack Data Fits Among Source Systems and the Seller Process
Slack is one source system among several a company may license, and its export comes after the readiness check and before de-identification and the choice of buyer. Compare export rights and mechanics by source system, where Microsoft Teams data export follows different rules and Jira data export rights cover issue history. The full sequence to sell or license company data to AI companies runs in this order:
- Data sale readiness
- Data inventory for an AI data sale
- Company data that cannot be licensed
- PII removal and de-identification
- The data manifest
- Choosing a buyer for your data
- AI data licensing agreement
Slack Archives of a Closed or Insolvent Company
A closed company can license its Slack archive only if someone with authority still controls the workspace before the plan lapses or history ages out. Ooak Data states that wind-down deals close with a director, liquidator or administrator signing, and The Corner states that closed companies need 25+ staff at peak and substantial Slack or Teams history (both checked November 9, 2026). Free workspaces also lose history older than one year. Read selling data from a shut-down or defunct company for the rest. Deadlines before a shutdown are covered under exporting company data before shutting down.
Slack Replicas Built for RL Environments
Some AI developers do not buy Slack data at all but commission replicas of Slack as RL environments, and one interviewee in Epoch AI's survey of January 12, 2026 put a high-fidelity replica at around USD 300,000. That is one interviewee's claim, and the background is in how RL environments are built and bought.
Program Pages Named on This Page
The program terms above come from each program's own page, checked November 9, 2026. Profiles follow, alphabetically within each group.
- Hubs: company data partnership programs, who buys AI training data
- Profiles: Avelence (intermediary), Centific, Collinear AI, Handshake AI data buyer profile, Labelbox Prism, Mercor data buyer profile, Nyne, Ooak Data, Polyshares, Scale AI, SimpleClosure (intermediary), SuperAnnotate, The Corner (intermediary, micro1 referral page), Turing Project Lazarus
Frequently Asked Questions
Can a company sell its Slack data to AI companies?
Yes, a company can license its exported Slack data where its plan, its contracts and the law allow, usually as a license rather than a sale. The plan sets what can be exported, and the API Terms bar outside apps from training a large language model on API Data.
Which Slack plan can export private channels and direct messages?
Only Business+, by an application the Workspace Primary Owner approves, and Enterprise, where Org Owners ask Support to enable export. Free and Pro export neither, apart from private Salesforce channels by application.
Does Slack train AI models on workspace messages?
Slack states that it does not train generative AI models on Customer Data without affirmative opt-in consent. That is Slack's claim, checked November 9, 2026.
What is Slack data worth to an AI buyer?
No public price exists for Slack data as such; SimpleClosure, an intermediary, states startup assets typically sell for tens of thousands to hundreds of thousands of USD (September 3, 2026). Methods are in how much company data is worth to AI companies.