SaaS Ranking
Menu

Slack: what they publish

slack.com · Team chat and group messaging · checked 2026-10-26

30/100EBand E

Rank 2 of 5 in Team chat and group messaging, where the median is 26.

Public transparency score, not a product or security rating. Latest check: 2026-10-26. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

6 days since the newest dated result, 6 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Slack

slack.com · Team chat and group messaging

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 30of 100 Rank 2 of 5

Published commitments3 of 9 found

Measured behaviour2 of 3 found

Checked 2026-10-26. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Slack has no such document.

Where Slack sits in Team chat and group messaging

  1. A0 0%
  2. B0 0%
  3. C0 0%
  4. D1 20%
  5. E2 40%
  6. F2 40%
5 vendors with a score. Bands have fixed thresholds, see how the score works.

The band of Slack is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What Slack states

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-10-26.

Show the 8 addresses we checked
  1. https://slack.com/legal/dpa – reached, no match (HTTP 404)
  2. https://slack.com/dpa – reached, no match (HTTP 404)
  3. https://slack.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://slack.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://slack.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://slack.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://slack.com/trust/dpa – reached, no match (HTTP 404)
  8. https://slack.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-26.

Show the 7 addresses we checked
  1. https://slack.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://slack.com/subprocessors – reached, no match (HTTP 404)
  3. https://slack.com/sub-processors – reached, no match (HTTP 404)
  4. https://slack.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://slack.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://slack.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://slack.com/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Data location: where they say data is hosted

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://slack.com/trust/privacy/privacy-policy · checked 2026-10-26

Show the 7 addresses we checked
  1. https://slack.com/security – reached, no match (HTTP 200)
  2. https://slack.com/trust – reached, no match (HTTP 200)
  3. https://slack.com/legal/privacy – reached, no match (HTTP 404)
  4. https://slack.com/privacy – found, but behind a sign-in
  5. https://slack.com/privacy-policy – found, but behind a sign-in
  6. https://slack.com/compliance – reached, no match (HTTP 404)
  7. https://slack.com/legal/privacy-policy – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-26.

Show the 3 addresses we checked
  1. https://status.slack.com/ – reached, no match (HTTP 200)
  2. https://slack.com/status – reached, no match (HTTP 200)
  3. https://slack.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-10-26.

Show the 1 address we checked
  1. https://slack.com/ – third-party requests before any interaction: a.slack-edge.com, a11179690159.cdn.optimizely.com, api.company-target.com, cdn.cookielaw.org, cdn3.optimizely.com, d34u8crftukxnk.cloudfront.net, fonts.gstatic.com, geolocation.onetrust.com, jnn-pa.googleapis.com, logx.optimizely.com, www.google.com, www.youtube-nocookie.com, www.youtube.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-10-26.

Show the 8 addresses we checked
  1. https://slack.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://slack.com/subprocessors – reached, no match (HTTP 404)
  3. https://slack.com/sub-processors – reached, no match (HTTP 404)
  4. https://slack.com/legal/dpa – reached, no match (HTTP 404)
  5. https://slack.com/dpa – reached, no match (HTTP 404)
  6. https://slack.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://slack.com/trust/subprocessors – reached, no match (HTTP 404)
  8. https://slack.com/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-26.

Show the 6 addresses we checked
  1. https://slack.com/legal/sla – reached, no match (HTTP 404)
  2. https://slack.com/sla – reached, no match (HTTP 404)
  3. https://slack.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://slack.com/trust/sla – reached, no match (HTTP 404)
  5. https://slack.com/uptime – reached, no match (HTTP 404)
  6. https://slack.com/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 5
✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://slack.com/pricing · checked 2026-10-26

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000; includeSubDomains; preload

    Read at https://slack.com/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://slack.com/

    max-age=31536000; includeSubDomains; preload

    Read at https://slack.com/

Source: https://slack.com/ · checked 2026-10-26

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page FedRAMP, HIPAA (not counted: the sentence does not carry it), ISO/IEC 27001, ISO/IEC 27017, ISO/IEC 27018 (unclear from the sentence), ISO/IEC 27701 (unclear from the sentence), SOC 2 (unclear from the sentence), TISAX. The sentence we kept does not carry this finding on its own, so it counts in no list and no figure.
    Show the 8 exact wordings

    Federal Risk and Authorization Management Program (FedRAMP) Slack is FedRAMP Moderate authorized to meet the compliance needs of organizations in the public sector.

    Read at https://slack.com/trust/security

    ational security and data privacy standards Health Insurance Portability and Accountability Act (HIPAA) Slack can be configured for HIPAA compliance, including electronically protected health informat

    Read at https://slack.com/trust/security

    cts our organization and your data at every layer Compliance certifications and attestations ISO/IEC 27001 Information Security Management System (ISMS) Download certificate ISO/IEC 27017 Security Con

    Read at https://slack.com/trust/security

    ttestations ISO/IEC 27001 Information Security Management System (ISMS) Download certificate ISO/IEC 27017 Security Controls for the Provision and Use of Cloud Services Download certificate ISO/IEC 27

    Read at https://slack.com/trust/security

    IEC 27017 Security Controls for the Provision and Use of Cloud Services Download certificate ISO/IEC 27018 Protection of Personally Identifiable Information (PII) Download certificate ISO/IEC 27701 Pr

    Read at https://slack.com/trust/security

    e ISO/IEC 27018 Protection of Personally Identifiable Information (PII) Download certificate ISO/IEC 27701 Privacy Information Management System (PIMS) Download certificate ISO/IEC 42001 Information t

    Read at https://slack.com/trust/security

    42001 Information technology — Artificial intelligence — Management system Download certificate SOC 2 (Type Ⅱ) Trust Services Principles SOC 3 Service Organization Controls Download report GovSlack S

    Read at https://slack.com/trust/security

    authorization Trusted Information Security Assessment Exchange Scope-ID SHYV0T Assessment-ID AMHN37 TISAX and TISAX results are not intended for the general public.

    Read at https://slack.com/trust/security

Source: https://slack.com/trust/security · checked 2026-10-26

✓

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

Source: https://slack.com/.well-known/security.txt · checked 2026-10-26

✓

Named privacy contact (DPO or privacy address)

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://slack.com/trust/privacy/privacy-policy · checked 2026-10-26

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Slack

5 found · 7 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-26.

Investigate 7 open evidence questions
  1. Data processing agreement

    Please share the current data processing agreement for the product and plan we are considering, including its annexes and signing process.

    Inspect this check
  2. Subprocessor list

    Which subprocessors apply to our product, what does each process, and in which countries? Please share the current list.

    Inspect this check
  3. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  4. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  5. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  6. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  7. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.