Can you license your Slack, Google or Microsoft data to AI buyers?
· Company Data Advisors
Slack's terms say the customer owns its workspace data, but its API terms block third-party apps from bulk export or LLM training. What that means for a license.
Slack's own terms say the customer owns the messages and files in its workspace, and Google's terms say the same. Microsoft's page speaks of control and processing rather than ownership. The restrictions that make news sit in Slack's API terms, which limit what a third-party app can do with data pulled through the API. Our reading: the route a buyer uses to collect the data matters as much as who owns it, because a buyer that reads your workspace through an app and a buyer that receives an export your admin ran may fall under different terms.
This is a reading of public terms, not legal advice. Your contract with each vendor, your plan and any other agreements you signed can change the answer, so have counsel read them before you share anything.
Who owns the data in your Slack workspace?
Slack's User Terms of Service state that content submitted to the service, "such as messages or files", is Customer Data and "is owned by Customer". The terms add that the customer can manage "permissions, retention and export settings" and "enable or disable third party integrations." The same section makes the customer solely responsible for obtaining "any rights, permissions or consents" from its users that are "necessary for the lawful use of Customer Data" (Slack User Terms).
Two points follow for an owner. The company, not the employee who wrote the message, is the party that controls the workspace. And the duty to deal with employees' and others' rights sits with the company, which is why, in our view, employees' and customers' information in the records needs an answer before any license is signed.
What do Google and Microsoft say?
Google's Cloud Terms of Service, which its Workspace terms page says now cover Workspace and apply from each customer's renewal, state that "as between the parties" the customer "retains all Intellectual Property Rights in Customer Data" and that Google will only access, use and process Customer Data in accordance with the Cloud Data Processing Addendum (Google terms). Negotiated or older agreements may differ, so read the one you signed.
Microsoft's privacy overview says it processes customer data "as per customers' documented instructions" and for business operations, and that the data "isn't used for user profiling, advertising, or market research" (Microsoft Learn). We did not find a plain ownership sentence on that page, so check your Microsoft agreement and its data protection addendum for the exact wording.
None of these ownership pages names AI licensing. They say who owns the data and who may process it. They don't say what you may do with an export afterward,.
What do Slack's API terms restrict?
Slack's API Terms of Service restrict third-party app providers, not the company that owns the workspace. The terms, effective October 10, 2025, say a provider of an app "offered for use outside your organization" may not "use API Data to train a large language model", may not "bulk export Slack message and file data except where expressly allowed by an additional agreement", and may not "create persistent copies, archives, indexes, or long-term data stores of other organizations' API Data" (Slack API Terms). The Discovery API is limited to "security and compliance use cases."
Computerworld reported that Salesforce, Slack's owner, published the restrictions on May 29, 2025, stopping Slack data from being ingested into outside language models. Hunton Andrews Kurth described the terms as prohibiting bulk export, long-term copies and use in large language models. The version quoted above is the later one, effective October 10, 2025. The long-term copy ban is worded for the Data Access and Real-Time Search APIs, and the bulk export ban excepts apps on the Discovery API for approved security and compliance uses.
That matters here because several buyers describe collecting data through connections to your accounts. The terms speak of apps offered outside your organization, so whether a given buyer's connector counts is a question for that buyer and for counsel. It is a fair thing to ask in writing.
How does a Slack export work, and who can run one?
Slack's help center says workspace owners and admins can export messages and file links from public channels in JSON format on all plans. Exports of private channels and direct messages are not offered on Free or Pro plans. On Business+, Workspace Owners can apply for a self-serve export tool "for legal and regulatory compliance", and applications "require approval from the Workspace Primary Owner". On Enterprise, Org Owners request access through Slack Support (Slack export help). Free workspaces can export only links to files from the last 90 days.
In practice, private channels and direct messages are the hardest records to export. A company should find out which plan it is on, who its Primary Owner is and whether it would need to apply, before it applies to any buyer.
How do buyers collect Slack and email data?
Buyers' published processes differ in who runs the extraction: your team, or the buyer through a connection to your accounts.
| Buyer | Collection, as summarized on our buyer page |
|---|---|
| Mercor | You connect your accounts; extraction and anonymization are automated; it says no data leaves your systems until you approve it |
| Mode | Your team signs in to the approved systems; Mode exports and de-identifies the agreed copy |
| Labelbox Prism | Read-only connectors; Prism scrubs personal information |
| Centific | A mutual NDA, then a read-only connection and automated extraction |
| Replay | Exports the data into an isolated environment for each engagement and removes personal information itself |
Each row summarizes the buyer's own published process on our Mercor, Mode, Labelbox Prism, Centific and Replay pages. Our Mercor page tells owners to check what they are authorized to share before connecting.
What should you ask before you connect or export?
Ask these in writing, and keep the answers with the contract:
- Whose credentials and which route? Does the buyer use a read-only connection, an admin export or an approved app, and under which vendor agreement?
- What does the vendor's own terms page say about that route? For Slack, read the API terms and ask whether the buyer relies on them, an additional agreement or an export you run.
- Which plan and which owner? Confirm you can run the export you are promising and whether your plan needs an application or Slack Support's approval.
- What stays out? Private channels, direct messages, customer channels shared with other companies and anything covered by a confidentiality term.
- Who else's data is inside? Customers, vendors and shared channels with other organizations may involve rights that are not yours alone; ask counsel.
- What happens to the copy? How long the buyer keeps it, whether it can be resold and how it is deleted, as set out in how license terms compare.
Where we come in
Our view: the ownership question is rarely the blocker. The route and the other people's data in the records are. Company Data Advisors is an independent advisory firm. We track each buyer's published process, read the terms with the owner, including how data would be collected, and nothing about your company is shared until you approve a specific, named buyer. Participating buyers may pay us referral fees, and we tell you which before any introduction. Owners pay us nothing, and you can apply to any buyer directly. For the full path from first form to payment, see how to sell company data to AI.
Before you apply, find out which Slack plan you are on, who the Primary Owner is and who signed your Google and Microsoft agreements. Then ask each buyer how it would collect the data. If you'd like a second read, start with the screener.
Programs in this post
More from the blog
- Is my company too small to license its data to AI buyers?
Most AI data buyers with a size floor set it at 20 to 50 employees, but law, accounting and medical firms qualify smaller, and nine programs state no minimum.
- One payment or a revenue share: how AI data buyers pay
The largest group of AI data buyers pays once. A few pay a share of every resale, and one now pays nothing upfront. How each model works and what to ask.
- How to check that an AI data buyer is legitimate
Six checks an owner can run in an afternoon before sharing records. Who the buyer is, what you pay, what it asks first, personal data, payment and license terms.
See which buyers fit your company
Eight quick questions against every program in our buyer index. Participating buyers may pay us referral fees.