Can our Slack history be licensed to AI companies, and how do we get it out?
Often yes, if the company holds the rights and strips out private and sensitive conversations first. Public channel history can be exported by workspace owners and admins on every Slack plan, while private channels and direct messages need a higher plan and Slack's approval. Some buyers skip the export and connect with read-only access instead.
What is in a Slack workspace, and why do buyers care?
A Slack workspace holds years of real work conversation: questions and answers between coworkers, project threads, handoffs, incident updates, and the back-and-forth of solving problems. Channels are usually organized by team, customer or project, so the history shows how work actually gets done.
AI companies value this kind of record because it shows people reasoning, coordinating and making decisions in plain language. That is hard to find in public web text. Threads that show a problem, the discussion, and the outcome tend to be the most useful.
Usually in scope
- Work conversations about operations
- Tickets, tasks and project histories
- Process documents and SOPs
- Orders, invoices and workflow records, de-identified
- Code repositories you own outright
Commonly left out
- HR, payroll and personnel files
- Board, legal and M&A material
- Direct messages and private channels
- Data you hold for customers under contract
- Health, financial-account or other regulated personal data
How does a Slack export work, and who can run it?
As of October 2026, Slack's help center says workspace owners and admins can export public channel content on the Free, Pro and Business+ plans, and only owners can apply for more. On Enterprise plans, org owners and admins handle exports. Members who hold Slack's Export Admin role can also export.
What you can export depends on your plan:
- Free and Pro: public channels only. Slack notes that Free workspaces get file links only for the last 90 days.
- Business+: public channels, plus private channels and direct messages after an application approved by the workspace's Primary Owner.
- Enterprise: all conversation types, after the org owner applies to Slack for access to its self-serve export tool.
- Most exports contain links to files rather than the files themselves, according to Slack's guide to its export tools.
Does Slack restrict why you export?
Yes. Slack's guide to its import and export tools says exports of private content are allowed only in limited situations, and that employment and privacy laws and company policies limit how they may be used. On Free and Pro plans, Slack says it will turn down requests for private channel and DM exports unless the owner shows a legal basis such as member consent or legal process.
On Enterprise plans, the org owner must confirm that proper employee agreements and policies are in place and that the use is lawful. Slack also notes that laws may require employers to tell employees about exports. Treat this as a legal question for your own lawyer before licensing anything beyond public channels.
Do you have to export at all?
Some buyer programs ask a Slack owner or admin to approve an app instead of running an export. The same plan limits and approval rules on private channels and direct messages still apply, so do not assume an app unlocks content your plan or policies would not let you export. Ask what the app can read, where copies are kept, and how they are deleted.
What should stay out of a Slack license?
Most companies that license chat history keep a tight scope. Common exclusions include:
- Direct messages (DMs) and private group chats, unless you have clear consent and legal advice.
- HR, payroll, legal, benefits, and leadership channels.
- Shared channels with customers or partners (Slack Connect), since the other company has rights in its own messages.
- Customer personal data, passwords, API (application programming interface) keys, and financial account numbers pasted into chat.
- Channels covered by an NDA (nondisclosure agreement) or a customer contract that limits reuse.
What about rights and contracts?
Slack's terms generally let a customer export its own workspace data, but that does not mean everything inside it is yours to license. Messages may contain customer information protected by contract, partner content, or employee personal data covered by privacy laws such as the CCPA (California Consumer Privacy Act) in California. See our guides on who owns the data and on employee and customer privacy, and talk to your lawyer before signing.
Common questions
Can we license Slack data on the Free plan?
You can export public channels on Free, but Slack says file links only cover the last 90 days and private content needs Slack's approval with a legal basis. Many companies license only public channels for this reason.
Do employees have to be told?
Slack's guide says laws and policies may require employers to notify employees about exports. Ask your lawyer what applies to you.
Are DMs worth including?
Some buyers may want them, but they carry the most privacy risk. Most companies exclude them unless consent and legal review are in place.
Does the export include attached files?
Usually not. Slack says most exports include links to files, not the files themselves.
Can we stop a connected app later?
Normally an owner or admin can remove the app and revoke its access. Confirm in the license how the buyer deletes data it already copied.
Sources
- Export your workspace data | Slack Help Center, accessed 2026-10-15
- Guide to Slack import and export tools | Slack Help Center, accessed 2026-10-15
General information, not legal, tax or financial advice.