Provision record
Slack · Slack Sub-Processors (Salesforce) · View original document ↗

Sub-processor Notification Subscription Mechanism

Medium confidence Unique · 0 of 343 platforms
Stay ahead of the changes
Track Slack and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what Slack's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

Generated by a model from the captured document; not read by a person

Under GDPR Article 28, controllers are entitled to object to changes in sub-processor arrangements. This provision establishes the operational mechanism through which Salesforce delivers advance sub-processor change notifications, making subscription to this mechanism a compliance dependency for organizations that need to exercise sub-processor objection rights under their DPAs.

⚠

Interpretive note: The document does not specify the advance notice period provided through the notification mechanism, which is material to assessing whether the mechanism satisfies GDPR Article 28 objection opportunity requirements under applicable DPA terms.

Cross-platform context

See how other platforms handle Sub-processor Notification Subscription Mechanism and similar clauses.

Compare across platforms →
▸ View Original Clause Language DOCUMENT RECORD
"
Salesforce Customers may subscribe to notifications of new sub-processors for those Covered Services for which Customer has a then-current active subscription by filling out this form.

Excerpt from Slack's Sub-Processors (Salesforce)

Provision details

Document information
Document
Slack Sub-Processors (Salesforce)
Entity
Slack
Tracking information
First captured by ConductAtlas
July 6, 2026
Text quoted from version
CA-V-007326, captured Oct. 3, 2026
Record ID
CA-P-013437
Document ID
CA-D-000931
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-007326)
633d33dea4692a8c1fa6732a616786a4d5fa92a5e3ac5e06960f58cc0b75be51
Analysis generated
July 6, 2026 23:13 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-007326, captured Oct. 3, 2026 (checked Oct. 5, 2026)
Not the current version. The document's current version is CA-V-007725, captured Oct. 21, 2026; this clause has not been re-checked against it.
Citation Record
Entity: Slack
Document: Slack Sub-Processors (Salesforce)
Record ID: CA-P-013437
Version: CA-V-007326
Captured: 2026-10-03 00:29:54 UTC
SHA-256: 633d33dea4692a8c…
URL: https://conductatlas.com/platform/slack/slack-sub-processors-salesforce/provision/CA-P-013437/sub-processor-notification-subscription-mechanism/
Accessed: Nov. 17, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Slack's Sub-processor Notification Subscription Mechanism clause do?

Under GDPR Article 28, controllers are entitled to object to changes in sub-processor arrangements. This provision establishes the operational mechanism through which Salesforce delivers advance sub-processor change notifications, making subscription to this mechanism a compliance dependency for organizations that need to exercise sub-processor objection rights under their DPAs.

Is ConductAtlas affiliated with Slack?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Slack.