Paradraw
29 published9 named, not published0 expected, not published90 relationships3045 clauses
Every legal document Slack publishes, and the ones its own terms name that nobody published. Free to read.Other companies
highStructure

Slack Brand Terms of Service | Legal reads as part of the agreement, and nothing in the set refers to it

Slack Brand Terms of Service | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

highStructure

Slack Developer Programme Agreement | Legal reads as part of the agreement, and nothing in the set refers to it

Slack Developer Programme Agreement | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

highStructure

Slack Marketplace Agreement | Legal reads as part of the agreement, and nothing in the set refers to it

Slack Marketplace Agreement | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

highStructure

Slack Supplemental Terms | Legal reads as part of the agreement, and nothing in the set refers to it

Slack Supplemental Terms | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

highStructure

Platform beta terms | Legal reads as part of the agreement, and nothing in the set refers to it

Platform beta terms | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

  • PBTL — first clause

    “Customers who agreed to the platform beta services terms prior to the Effective Date listed below can find such terms available here. Effective: 14th September 2022”

Wrong? Ask for access to correct it.

highStructure

Software integration supplement | Legal reads as part of the agreement, and nothing in the set refers to it

Software integration supplement | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

  • SISL — first clause

    “This Software Integration Supplement (the "Supplement") is a legally binding agreement. Please read it carefully. By clicking "Install" or enabling or using a Slack (defined below) software integration and/or any updates…”

Wrong? Ask for access to correct it.

highGap

CCPA names a United States-specific Data Processing Addendum we could not find published

California Consumer Privacy Act (CCPA) FAQ | Legal ¶17 refers to a United States-specific Data Processing Addendum. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • CCPA ¶17

    “Slack offers our customers a United States-specific Data Processing Addendum that supplements the Customer Terms of Service or any MSA. This addendum incorporates the obligations and requirements set forth by the CCPA. P…”

Wrong? Ask for access to correct it.

highStructure

Customer-specific supplement | Legal reads as part of the agreement, and nothing in the set refers to it

Customer-specific supplement | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

highStructure

Slack Marketplace Agreement | Legal is drafted as if it could incorporate Slack Partner Programme terms and conditions | Legal

Slack Marketplace Agreement | Legal is a binding and Slack Partner Programme terms and conditions | Legal is a perimeter document. ¶2 reads: "You, on behalf of the individual, company or legal entity that developed the Application for listing on the Slack Marketplace, agree to abide by the Slack API Terms of Service, as updated from time to time, and as supplemented by these Slack Marketplace Terms…"

  • SMAL ¶2

    “You, on behalf of the individual, company or legal entity that developed the Application for listing on the Slack Marketplace, agree to abide by the Slack API Terms of Service, as updated from time to time, and as supple…”

  • TOS — first clause

    “Slack Partners”

Wrong? Ask for access to correct it.

highStructure

Platform beta terms | Legal is drafted as if it could incorporate Slack Partner Programme terms and conditions | Legal

Platform beta terms | Legal is a binding and Slack Partner Programme terms and conditions | Legal is a perimeter document. ¶7 reads: "To the extent that the Customer enables, uses or tests a Beta Service that (a) requires the use of any Slack software integration, the software integration supplement found at https://slack.com/terms-of-service/slack-integrations shall apply, and (b) requires…"

  • PBTL ¶7

    “Beta Services. From time to time, Slack may make certain Services, features or functionality available to the Customer, at no charge, which may be designated by Slack as a beta, pilot, limited release, developer preview,…”

  • TOS — first clause

    “Slack Partners”

Wrong? Ask for access to correct it.

highStructure

Data request policy | Legal is drafted as if it could outrank Slack Partner Programme terms and conditions | Legal

Data request policy | Legal is a public notice and Slack Partner Programme terms and conditions | Legal is a perimeter document. ¶2 reads: "In the event of any inconsistency between the provisions of this Data Request Policy and the Customer Terms of Service or written agreement with the Customer, as the case may be, the Customer Terms of Service or written agreement will prevail."

  • DRPL ¶2

    “Slack receives requests from government agencies, users and other third parties to disclose data other than in the ordinary operation and provision of the Services. This Data Request Policy outlines Slack's policies and …”

  • TOS — first clause

    “Slack Partners”

Wrong? Ask for access to correct it.

highStructure

Slack API Terms of Service | Legal reads as part of the agreement, and nothing in the set refers to it

Slack API Terms of Service | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

highStructure

User terms of service | Legal reads as part of the agreement, and nothing in the set refers to it

User terms of service | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

highStructure

Slack Community Forum terms of service | Legal reads as part of the agreement, and nothing in the set refers to it

Slack Community Forum terms of service | Legal is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

mediumGap

TOS names 2 documents we could not find published

Slack Partner Programme terms and conditions | Legal ¶6 names Customer Terms and Acceptable Use Policy. None appears in the sitemap, the legal index or the trust centre. They may exist and be available on request.

  • TOS ¶6

    “Additional terms. This Agreement does not grant you any right to access or use our online workspace productivity tools and platform (the 'Services') or any of our non-public application programming interfaces, which will…”

Wrong? Ask for access to correct it.

mediumGap

AI names a Slack Terms we could not find published

Privacy principles: search, learning and artificial intelligence | Legal ¶2 refers to a Slack Terms. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • AI ¶2

    “Our mission is to build a product that makes work life simpler, more pleasant and more productive. Our guiding principle as we build this product is that the privacy and security of Customer Data is sacrosanct, as detail…”

Wrong? Ask for access to correct it.

mediumGap

SATS names a Slack Application Developer Policy we could not find published

Slack API Terms of Service | Legal ¶5 refers to a Slack Application Developer Policy. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • SATS ¶5

    “These API Terms, together with the Slack Application Developer Policy form a binding 'Contract' between you and us. 'We', 'our' and 'us' refer to the applicable Slack entity in the section entitled 'Which Slack entity ar…”

Wrong? Ask for access to correct it.

mediumGap

SCFT names a Community Forum guidelines we could not find published

Slack Community Forum terms of service | Legal ¶26 refers to a Community Forum guidelines. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • SCFT ¶26

    “Slack Community Forum is intended to be a place for users of Slack products and services to connect, communicate and share information, experiences, tips and thoughts on Slack products and services. To ensure and foster …”

Wrong? Ask for access to correct it.

mediumGap

SLA names a App Developer Policy we could not find published

Slack Developer Programme Agreement | Legal cl. 2.3 refers to a App Developer Policy. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • SLA cl. 2.3

    “2.3. Our responsibilities. We shall use commercially reasonable efforts to (i) give advance notice of any planned downtime and (ii) provide the Developer Services in accordance with laws and government regulations applic…”

Wrong? Ask for access to correct it.

mediumGap

SLA names a Developer Documentation we could not find published

Slack Developer Programme Agreement | Legal cl. 2.5 refers to a Developer Documentation. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • SLA cl. 2.5

    “2.5. Usage restrictions and limitations. You shall not (a) make the Developer Services or Developer Resources available to any person or entity other than Users, (b) sell, resell, rent or lease the Developer Services or …”

Wrong? Ask for access to correct it.

mediumGap

SSTL names a Salesforce Main Services Agreement we could not find published

Slack Supplemental Terms | Legal ¶2 refers to a Salesforce Main Services Agreement. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • SSTL ¶2

    “The Salesforce Main Services Agreement ('MSA') and these Slack Supplemental Terms ('Supplemental Terms') are legally binding and govern your acquisition and use of Slack. These Supplemental Terms apply in addition to the…”

Wrong? Ask for access to correct it.

lowStructure

Data request policy | Legal is published but no other document refers to it

Data request policy | Legal sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

Held back

51 readings, on top of the 22 above

Each puts two clauses side by side that answer the same question differently, and quotes both.

Accounts are invite-only for now. Leave an address and we will come back to you.

I work here

The drawing, in words

Slack’s legal documents

Slack publishes 29 legal documents. Its own terms name 9 more that we could not find published. Every cross-reference inside them resolves.

Published 29

Named, not published 9

  • Slack Terms
  • Customer Terms
  • Acceptable use policy
  • Slack Application Developer Policy
  • Community Forum guidelines
  • App Developer Policy
  • Developer Documentation
  • Salesforce Main Services Agreement
  • Data processing terms

Named in Slack’s own terms and not found in its sitemap, legal index or trust centre. It may exist and be available on request.

How they connect 67

  • 34 times a document cite another document
  • 19 times a document depend on another existing
  • 7 times a document rely on a definition from another
  • 3 times a document incorporate another by reference
  • 2 times a document say which document wins on a conflict
  • 2 times a document amend another

Read from slack.com on 25 September 2026. A description of how the documents fit together, not legal advice. Is this your company?