# Can you license your company's SaaS data to AI companies?

URL: https://sellmydatatoai.net/data-rights
Reviewed: 2026-11-08

Under the terms of all 12 platforms we reviewed, the customer company keeps ownership of the data it stores. The limits sit in API and developer terms: Slack, Google Workspace, Zendesk, HubSpot and Zoom restrict AI training on data pulled through their APIs, while native admin exports carry fewer conditions. Privacy law and third-party content usually decide the case. Confirm with your own counsel.

Companies keep many of their most valuable records in SaaS tools, and the first question from buyers and sellers is whether the platform's terms allow an export to be licensed for AI training. We read each platform's own terms, help center and developer documentation in November 2026 and quoted the clauses that matter.

> **How to read the verdicts** Yes means a clause we found restricts AI model training on some platform data, usually data pulled through the platform's APIs. No means we found no such clause in the terms we reviewed. Unclear means the terms are ambiguous or we could not review them in full. None of these verdicts tells you whether your own license is lawful.

## Which platforms restrict AI training on exported data?

Five of the 12 platforms restrict AI training on data pulled through their APIs, four are unclear and three have no restriction we could find. Each row links to the full page with the clause, the export tools and a preparation checklist.

| Platform | Who owns the data | Native export tool | Plan needed | AI-training restriction in the terms |
| --- | --- | --- | --- | --- |
| [Slack](https://sellmydatatoai.net/data-rights/slack) | Customer, under the Slack Supplemental Terms | Workspace export from admin settings. Discovery API for approved partners | Any plan for public channels. Business+ or Enterprise for private channels and DMs | Yes: Slack API Terms, Data Usage by Third Parties: apps may not "use API Data to train a large language model" |
| [Microsoft 365](https://sellmydatatoai.net/data-rights/microsoft-365) | Customer, under the Microsoft DPA | Microsoft Purview eDiscovery export. Teams Export APIs in Microsoft Graph | Microsoft 365 E3 or E5 license for the eDiscovery user | Unclear: no AI clause found. Microsoft APIs Terms of Use §3(b)(14) bars you to "Redistribute or resell" data obtained using the APIs |
| [Google Workspace](https://sellmydatatoai.net/data-rights/google-workspace) | Customer, under section 5.1 of the Workspace terms | Admin console Data Export tool. Google Vault | Any edition for Data Export, run by a super admin. Vault on editions that include it | Yes: Workspace API User Data and Developer Policy: no using user data to "create, train, or improve a machine learning or artificial intelligence model" |
| [Zendesk](https://sellmydatatoai.net/data-rights/zendesk) | Customer, under section 3.1 of the Zendesk MSA | Account data export (JSON, CSV, XML). REST API | Suite Growth or higher, or Support Professional or Enterprise, with export enabled by Support | Yes: Zendesk Developer Terms §3.6(iii): no use of API Data for "creating, training, or improving any general AI model" |
| [Salesforce](https://sellmydatatoai.net/data-rights/salesforce) | Customer, under section 6.3 of the Salesforce MSA | Data Export Service (weekly or monthly CSV files) | Weekly on Enterprise, Performance and Unlimited. Monthly on all editions except Database.com | No: no AI-training clause found in the MSA (September 15, 2025) or the AI Acceptable Use Policy (August 5, 2025) |
| [HubSpot](https://sellmydatatoai.net/data-rights/hubspot) | Customer, under section 5.1 of the Customer Terms of Service | Record exports (CSV, XLS, XLSX). CRM APIs | Any plan, user with export permissions | Yes: HubSpot Developer Terms §4.B.8: "must not use Customer Data or Content to train, fine-tune, improve" AI |
| [GitHub](https://sellmydatatoai.net/data-rights/github) | Customer, under section D.3 of the GitHub Terms of Service | git clone. Organization migration archives. REST API | Any plan for git clone. Organization owner for migration archives | No: no restriction found on licensing your own content. Terms of Service D.3: "You own Your Content" |
| [GitLab](https://sellmydatatoai.net/data-rights/gitlab) | Customer, under section 8.4 of the Subscription Agreement | Project file export. git clone | Free, Premium or Ultimate, with the Maintainer or Owner role | No: no restriction found on your own content. GitLab Duo AI Terms §3.3 bar using AI Functionality to train a competing model |
| [Atlassian](https://sellmydatatoai.net/data-rights/atlassian) | Customer, under section 13 of the Atlassian Customer Agreement | Cloud site backup. Confluence space export | Site or organization admin for backups. Space admin for space exports | Unclear: no AI clause found. Atlassian Developer Terms §9.2: "You may not sell any End User Data." |
| [Notion](https://sellmydatatoai.net/data-rights/notion) | Customer, according to Notion's help center | Workspace export (HTML, or Markdown and CSV). Page export to PDF | Workspace settings access. PDF with subpages on Business and Enterprise | Unclear: no AI clause confirmed. We could not retrieve the text of Notion's Master Subscription Agreement or Developer Terms |
| [Zoom](https://sellmydatatoai.net/data-rights/zoom) | Customer, under section 10.4 of the Zoom Terms of Service | Cloud recording files and VTT transcripts. Zoom APIs | Pro, Business, Education or Enterprise with cloud recording | Yes: Zoom API License and Terms of Use §2.8: no use of Customer Content to "train, develop, evaluate, test, improve, or modify" AI models |
| [Intercom](https://sellmydatatoai.net/data-rights/intercom) | Customer, under section 3.2 of the Intercom Terms of Service | Inbox transcript exports. Amazon S3 export (JSON). Conversations API | Inbox seat and export permissions | Unclear: no AI clause found. Developer Terms §3.2.1(g) bar copies of "any data obtained using the Intercom Service" beyond what is necessary |

## Who owns company data stored in SaaS platforms?

All 12 platforms say the customer owns or keeps the rights in its data. The wording varies, from "You own Your Content" in GitHub's Terms of Service to "SFDC acquires no right, title or interest from Customer" in the Salesforce Main Services Agreement, but none of the vendors claims ownership of what you store.

Ownership against the vendor does not settle the question. Your privacy notices, customer contracts, employee policies and the rights of people outside your company usually decide whether a license is possible, as our guide on [whether you can legally sell company data](https://sellmydatatoai.net/guides/can-you-legally-sell-company-data-for-ai) explains.

## Why do API terms matter more than the main contract?

API and developer terms are where AI restrictions sit. Slack, Google Workspace, Zendesk, HubSpot and Zoom each restrict training AI models on data pulled through their APIs, and Zendesk and HubSpot apply their developer terms to customers writing scripts for their own use.

Native admin exports usually sit under the main subscription agreement instead, and none of the main agreements we could read restricts customers from AI training on their own data. How you extract the data can change which terms apply, so choose the route with counsel before anyone writes code.

## What else decides whether a SaaS export is licensable?

- US privacy law, starting with the CCPA, which defines a sale as sharing personal information "for monetary or other valuable consideration"
- Sector rules such as HIPAA and the Gramm-Leach-Bliley Act where health or financial data could be present
- FTC expectations that you keep the privacy promises made when the data was collected
- Third-party content from customers, guests, shared channels, inbound email and open-source code
- UK GDPR and EU GDPR if any of the people in the data are in the UK or EU, covered in our [privacy law guide](https://sellmydatatoai.net/guides/gdpr-and-selling-data-for-ai-training)

## How do you prepare any platform export for a buyer?

1. **Pick the extraction route**: Prefer the platform's native admin export, and get counsel's view on the API or developer terms before any API pull.
2. **Scope what goes in**: Decide which channels, mailboxes, projects or date ranges carry value, and leave the rest behind.
3. **Remove third-party content**: Take out guests, shared channels, inbound email from outside parties, client documents and code you cannot clear.
4. **De-identify and test**: Follow a documented method and test a random sample, as our [de-identification guide](https://sellmydatatoai.net/guides/de-identification-for-ai-training-data) describes.
5. **Write the manifest**: Record counts, date ranges, systems and exclusions in a [data manifest](https://sellmydatatoai.net/guides/how-to-build-a-data-manifest), and check license warranties against our [licensing agreement checklist](https://sellmydatatoai.net/guides/ai-data-licensing-agreement-checklist).

If you want a view on whether your platform data is licensable and what buyers might pay, start with a [data valuation](https://sellmydatatoai.net/data-valuation). We are a broker, not a law firm, so take independent legal advice before you sign any license.

## Frequently asked questions

### Do SaaS platforms own the data my company stores in them?

Not under the terms we reviewed. All 12 platforms say the customer owns or keeps the rights in its data, in wording that ranges from "You own Your Content" in GitHub's Terms of Service to "Customer retains ownership of all Service Data" in the Zendesk Main Services Agreement. Most vendors keep a license to run and improve their services, and some, such as HubSpot and Intercom, may use the data to train their own AI.

### Why do API terms matter if my company owns the data?

Because API and developer terms are where most AI restrictions sit. Slack, Google Workspace, Zendesk, HubSpot and Zoom restrict AI training on data obtained through their APIs, and Zendesk and HubSpot apply their developer terms to customers writing scripts for their own use. Owning the data does not stop a contract from limiting what you do with copies you pull through an API.

### Is a native admin export safer than an API extraction?

Often it carries fewer contractual conditions. Native exports, such as Slack's workspace export, Google's Data Export tool or Zendesk's JSON export, sit under the main subscription agreement, and none of the main agreements we could read restricts AI training by customers. That does not make the export lawful to license. Privacy law, your own privacy promises and third-party content still apply, so confirm the route with counsel.

### Does a platform's AI-training restriction bind the AI buyer?

Usually not directly, because the buyer did not sign your platform contract. The restriction binds you, and a buyer's license will normally ask you to warrant that you have the right to license the data for training. If the data came through an API with an AI-training ban, that warranty may be hard to give. Our [licensing agreement checklist](https://sellmydatatoai.net/guides/ai-data-licensing-agreement-checklist) covers the warranties buyers ask for.

## Sources

- [Slack Supplemental Terms](https://slack.com/slack-supplemental-terms), Slack, accessed November 2026
- [Slack API Terms of Service](https://slack.com/terms-of-service/api), Slack, accessed November 2026
- [Microsoft Products and Services Data Protection Addendum (DPA)](https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA), Microsoft, accessed November 2026
- [Microsoft APIs Terms of Use](https://learn.microsoft.com/en-us/legal/microsoft-apis/terms-of-use), Microsoft Learn, accessed November 2026
- [Google Workspace Terms of Service](https://workspace.google.com/terms/premier_terms/), Google, accessed November 2026
- [Google Workspace API User Data and Developer Policy](https://developers.google.com/workspace/workspace-api-user-data-developer-policy), Google for Developers, accessed November 2026
- [Main Services Agreement](https://www.zendesk.com/company/agreements-and-terms/main-services-agreement/), Zendesk, accessed November 2026
- [Zendesk Developer Terms](https://www.zendesk.com/company/agreements-and-terms/zendesk-developer-terms/), Zendesk, accessed November 2026
- [Main Services Agreement](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/salesforce_MSA.pdf), Salesforce, accessed November 2026
- [Artificial Intelligence Acceptable Use Policy](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/policies/ai-acceptable-use-policy.pdf), Salesforce, accessed November 2026
- [Customer Terms of Service](https://legal.hubspot.com/terms-of-service), HubSpot, accessed November 2026
- [HubSpot Developer Terms](https://legal.hubspot.com/developer-terms), HubSpot, accessed November 2026
- [GitHub Terms of Service](https://docs.github.com/en/site-policy/github-terms/github-terms-of-service), GitHub Docs, accessed November 2026
- [GitHub Acceptable Use Policies](https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies), GitHub Docs, accessed November 2026
- [GitLab Subscription Agreement](https://handbook.gitlab.com/handbook/legal/subscription-agreement/), GitLab Handbook, accessed November 2026
- [GitLab Duo AI Terms (Additional Terms)](https://handbook.gitlab.com/handbook/legal/ai-functionality-terms/), GitLab Handbook, accessed November 2026
- [Atlassian Customer Agreement](https://www.atlassian.com/legal/atlassian-customer-agreement), Atlassian, accessed November 2026
- [Atlassian Developer Terms](https://developer.atlassian.com/platform/marketplace/atlassian-developer-terms/), Atlassian Developer, accessed November 2026
- [Privacy practices](https://www.notion.com/help/privacy), Notion Help Center, accessed November 2026
- [Notion AI security and privacy practices](https://www.notion.com/help/notion-ai-security-practices), Notion Help Center, accessed November 2026
- [Zoom Terms of Service](https://www.zoom.com/en/trust/terms/), Zoom, accessed November 2026
- [Zoom API License and Terms of Use](https://www.zoom.com/en/trust/legal/zoom-api-license-and-tou/), Zoom, accessed November 2026
- [Terms of Service](https://www.intercom.com/legal/terms-and-policies), Intercom, accessed November 2026
- [Intercom Developer Terms](https://developers.intercom.com/docs/publish-to-the-app-store/intercom-developer-terms), Intercom Developers, accessed November 2026
- [California Consumer Privacy Act of 2018, Civil Code section 1798.140](https://cppa.ca.gov/regulations/pdf/cppa_act.pdf), California Privacy Protection Agency, accessed November 2026
- [AI (and other) Companies: Quietly Changing Your Terms of Service Could Be Unfair or Deceptive](https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/02/ai-other-companies-quietly-changing-your-terms-service-could-be-unfair-or-deceptive), Federal Trade Commission, accessed November 2026

---

Get a data valuation: https://sellmydatatoai.net/data-valuation