Data licensing guide
By system

Licensing Slack data for AI: what Slack's terms say

By Ade Molajo · Updated · How we check figures

Quick answer

Possibly, but check Slack's terms first. Since October 2025, Slack's API terms bar third-party apps from using data obtained through Slack's APIs to train large language models, or bulk-exporting message data without a separate agreement. Those terms cover apps using Slack's APIs, not every export you make yourself, so ask the programme exactly how it would access your Slack, and take advice.

Oct 2025
Slack's API terms changed
No LLM training
on data third-party apps get through Slack's APIs
Ask
how a programme would access your Slack
DMs
and personal chat stay out

01What Slack's API terms say

Slack changed its API Terms of Service with effect from 10 October 2025. For apps used outside the organisation that built them, the terms say the app provider may not:

  • use API Data to train a large language model;
  • bulk export Slack message and file data, except where an additional agreement expressly allows it;
  • create persistent copies, archives, indexes or long-term data stores of other organisations' API Data obtained through Slack's data access and real-time search APIs.

"API Data" means messages, files, metadata and other data obtained from Slack's APIs.

Where these records usually live

Team chat

  • Slack
  • Microsoft Teams
  • Google Chat

Examples of common tools, to help you find your records. Product names and logos belong to their owners; no affiliation or endorsement.

02What that means for licensing

The terms are aimed at apps that pull data through Slack's APIs. If a programme, or a tool it uses, would connect to your workspace that way and use the data for model training, the terms are directly in the way.

Exports you make with Slack's own tools fall under your customer agreement with Slack, which the API terms don't cover. So before you scope Slack into a licence:

  1. Ask the programme exactly how it would access your Slack. An app connection, an admin export, or something else.
  2. Read your Slack customer agreement on export and use of your data.
  3. Take advice if it's unclear. This isn't legal advice.
Scoping Slack data in four steps: check access (app or own export?), pick channels (work channels only), drop dms (and shared channels), remove people (names, personal chat).01Check accessApp or own export?02Pick channelsWork channels only03Drop DMsAnd shared channels04Remove peopleNames, personalchat
Four steps before anything is shared. Agree the scope with the programme in writing.

03What to include, and what to leave out

Slack: usually licensable (Project and ops channels; Incident and support channels; How-to and process threads; Your own workspace export) versus check first or leave out (DMs and private personal chat; Shared channels with other companies; HR, health or disciplinary threads; Data pulled through a third-party app (API terms)).Usually licensableProject and ops channelsIncident and support channelsHow-to and process threadsYour own workspace exportCheck first, or leave outDMs and private personal chatShared channels with other companiesHR, health or disciplinary threadsData pulled through a third-party app (APIterms)
A starting point for scoping, not a legal test.

Slack is also one of the most personal systems a company runs. Even work channels carry names, opinions and the odd personal message, so UK GDPR applies (see our UK GDPR guide). Pseudonymising names isn't enough to take it outside UK GDPR; only proper anonymisation does.

04If Slack is out, what else carries the same knowledge?

  • Wiki and SOP pages
  • Ticket history
  • Project records
  • Shared mailboxes

Much of what's discussed in Slack ends up in tickets and wiki pages, which are simpler to license.

Take our free fit check to see which programmes you're likely to match. The programme decides.

05Questions people ask

Can I sell my company's Slack messages to AI companies?

Check two things first: Slack's terms for how the data would be accessed, and the personal data in the messages. Slack's API terms bar third-party apps from using API data to train language models.

Does Slack's ban apply to my own export?

Slack's API terms are about apps using Slack's APIs. Exports through Slack's own tools fall under your customer agreement with Slack, which the API terms don't cover. Read it, and take advice.

Do the programmes take Slack data?

Mode names Slack among its sources and says your team signs in to approved systems. Ask any programme exactly how it would access Slack and which terms apply.

What should never go in?

Direct messages, HR or health conversations, and shared channels with other companies.

Sources

Check which programmes you’re likely to matchA few short questions, about a minute. Free, no sign-up. The programme decides who qualifies.trackimpact.io/data →