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

Sub-processor Notification Subscription Mechanism

Medium severity Medium confidence Explicitdocumentlanguage Unique · 0 of 352 platforms
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for Slack Create a free account to receive the weekly governance digest and monitor one platform for governance changes.
Create free account No credit card required.
Document Record

What it is

This provision establishes an opt-in notification mechanism through which customers can receive advance notice of new sub-processors for services they actively subscribe to, accessed by completing a designated form.

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)

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.

Consumer impact (what this means for users)

The agreement establishes that sub-processor change notifications are delivered on an opt-in basis only; customers who do not subscribe to the notification form will not receive advance notice of new sub-processors added to services they use. Subscription requires completing a separate form, as stated in the document.

What you can do

⚠️ These actions may provide transparency or partial mitigation but may not fully address the underlying issue. Effectiveness varies by jurisdiction and individual circumstances.
  • Opt Out of Arbitration
    Navigate to the sub-processor notification subscription form linked within the document, complete the form identifying the covered services for which you hold an active subscription, and submit to begin receiving advance notifications of sub-processor changes.

Cross-platform context

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

Compare across platforms →

Monitoring

Slack has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Get Monitor Or create a free account →
▸ 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 Slack Sub-Processors (Salesforce)

ConductAtlas Analysis

Institutional analysis (Compliance & governance intelligence)

(1) REGULATORY LANDSCAPE: GDPR Article 28(2) requires that processors inform controllers of intended sub-processor changes and provide the controller an opportunity to object. This provision represents Salesforce's disclosed mechanism for satisfying that obligation. The adequacy of an opt-in notification model as a mechanism for satisfying Article 28 notice obligations may require evaluation under applicable supervisory authority guidance. Relevant enforcement authorities include EU national data protection authorities and the UK ICO. (2) GOVERNANCE EXPOSURE: Medium. Organizations that have not subscribed to the notification form may not receive timely advance notice of sub-processor changes, which could affect their ability to exercise contractual objection rights within any notice period specified in their DPA. The document does not specify the advance notice period provided through this mechanism. (3) JURISDICTION FLAGS: Heightened exposure exists for EU and EEA customers whose DPAs require a specific advance notice period before a new sub-processor is engaged. UK GDPR obligations mirror this requirement. Organizations acting as processors on behalf of their own customers face downstream notification obligations that depend on receiving timely upstream notice from Salesforce. (4) CONTRACT AND VENDOR IMPLICATIONS: Legal teams should confirm that their DPA with Salesforce specifies the notice period Salesforce commits to provide before engaging new sub-processors, and that the notification subscription mechanism delivers notice within that period. Organizations that act as data processors for their own customers should assess whether the Salesforce notification mechanism provides sufficient lead time to fulfill their own sub-processor notification obligations. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should verify that their organization has subscribed to the Salesforce sub-processor notification form for all active service subscriptions, document this subscription as part of vendor management records, and establish an internal process for reviewing sub-processor change notifications against existing data transfer impact assessments and DPA obligations.

Full compliance analysis

Regulatory citations, enforcement risk, and due diligence action items.

Track 3 platforms — free Get Monitor

Free: track 3 platforms + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.

Provision details

Document information
Document
Slack Sub-Processors (Salesforce)
Entity
Slack
Document last updated
July 6, 2026
Tracking information
First tracked
July 6, 2026
Last verified
July 6, 2026
Record ID
CA-P-013437
Document ID
CA-D-00931
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
c9a4265bad5be0ead8d6b94ae1851641116635e9c04e0405cd39f87622f9770f
Analysis generated
July 6, 2026 23:13 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Slack
Document: Slack Sub-Processors (Salesforce)
Record ID: CA-P-013437
Captured: 2026-07-06 23:13:04 UTC
SHA-256: c9a4265bad5be0ea…
URL: https://conductatlas.com/platform/slack/slack-sub-processors-salesforce/sub-processor-notification-subscription-mechanism/
Accessed: July 7, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Get Compliance

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

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.

How does this clause affect you?

The agreement establishes that sub-processor change notifications are delivered on an opt-in basis only; customers who do not subscribe to the notification form will not receive advance notice of new sub-processors added to services they use. Subscription requires completing a separate form, as stated in the document.

Is ConductAtlas affiliated with Slack?

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