Salesforce · Salesforce Privacy Statement · View original document ↗

Processor Carve-Out from Privacy Statement Scope

Medium severity High confidence Explicitdocumentlanguage Unique · 0 of 343 platforms
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for Salesforce 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 Privacy Statement only covers how Salesforce handles data in its own right, not the data that enterprise customers put into Salesforce's CRM or cloud products. That data is governed by separate contracts, not this document.

This analysis describes what Salesforce'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)

Consumers whose data is held in a company's Salesforce CRM cannot rely on this Privacy Statement for rights against Salesforce. They must look to the company that collected their data in the first place.

Clause Stability Stable

0
Changes
3
Months Monitored
May 9, 2026
First Seen
May 22, 2026
Last Seen
This clause type exists across 3350 other provisions on other platforms.

Consumer impact (what this means for users)

If your personal data is stored by a business using Salesforce as their CRM tool, this Privacy Statement does not govern that data. Your rights regarding that data must be exercised with the business that collected it, not directly with Salesforce.

How other platforms handle this

Ledger Medium

At Ledger, earning and maintaining our users' trust is a top priority. That's why we are deeply committed not only to protecting your privacy and securing your personal data, but also to being fully transparent about how we handle it.

Shein Medium

enableGpcSdk: true, gpcSetting: { privacyPolicyLink: '/Privacy-Security-Policy-a-282.html' }

Target Medium

We process Global Privacy Control signals as opt-out requests for the sale or sharing of personal information.

See all platforms with this clause type →

Monitoring

Salesforce has changed this document before.

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

Start Monitor free trial Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
This Privacy Statement does not apply to the extent we process Personal Data as a processor or service provider on behalf of our customers, including where we offer to our customers various services through which our customers (or their affiliates): (i) create their own websites and applications running on our platforms; (ii) sell or offer their own products and services; (iii) send electronic communications to others.

— Excerpt from Salesforce's Salesforce Privacy Statement

ConductAtlas Analysis

Institutional analysis (Compliance & governance intelligence)

REGULATORY LANDSCAPE: This carve-out reflects the GDPR controller-processor distinction under applicable EU and UK data protection law. Under GDPR, a processor acts only on documented instructions from the controller and is subject to separate obligations. The statement's exclusion aligns with this framework, but compliance teams should confirm that Salesforce's Data Processing Addendum is appropriately executed and covers all relevant processing activities in each jurisdiction where enterprise customer data is processed. GOVERNANCE EXPOSURE: Medium. The carve-out is legally standard but operationally significant. Enterprise customers must ensure their own privacy notices to end-users accurately describe Salesforce as a sub-processor and that the DPA covers all data types and processing purposes. Failure to execute an appropriate DPA while transferring personal data to Salesforce would expose the enterprise customer to regulatory risk under GDPR and CCPA. JURISDICTION FLAGS: EU and UK enterprise customers face the highest exposure given GDPR's strict processor agreement requirements. California-based enterprises must also evaluate whether their use of Salesforce as a service provider satisfies CPRA's service provider contract requirements to avoid a 'sale' or 'sharing' characterization. CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should verify that a current, signed Data Processing Addendum is in place with Salesforce before processing personal data through any Salesforce platform. The DPA, not this Privacy Statement, governs processor-capacity data and determines audit rights, breach notification obligations, and sub-processor approval processes. COMPLIANCE CONSIDERATIONS: Legal teams should maintain a data mapping record clearly distinguishing which personal data flows are governed by this Privacy Statement versus the DPA. Any new Salesforce product deployment should trigger a review of whether existing DPA coverage extends to the new processing activity or requires amendment.

Full compliance analysis

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

Track 1 platform — free Try Monitor free for 14 days

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

Applicable agencies

  • FTC
    The FTC enforces the EU-U.S. Data Privacy Framework and has broader authority over unfair or deceptive data practices affecting US consumers, relevant to processor relationship disclosures
    File a complaint →

Applicable regulations

EU AI Act
European Union
CCPA/CPRA
California, USA
Colorado AI Act
US-CO
Connecticut Data Privacy Act Amendments
US-CT
CAN-SPAM
United States Federal
FTC Act Section 5
United States Federal
GDPR
European Union
Indiana Consumer Data Protection Act
US-IN
Kentucky Consumer Data Protection Act
US-KY
Universal Opt-Out Mechanism Expansion 2026
US
VPPA
United States Federal

Provision details

Document information
Document
Salesforce Privacy Statement
Entity
Salesforce
Document last updated
May 5, 2026
Tracking information
First tracked
May 9, 2026
Last verified
May 9, 2026
Record ID
CA-P-007217
Document ID
CA-D-00202
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
c8f21ba713a0a380cbbc7d9628803d1d80804e0588bd331250df45b9a62ac5d3
Analysis generated
May 9, 2026 16:18 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Salesforce
Document: Salesforce Privacy Statement
Record ID: CA-P-007217
Captured: 2026-05-09 16:18:56 UTC
SHA-256: c8f21ba713a0a380…
URL: https://conductatlas.com/platform/salesforce/salesforce-privacy-statement/processor-carve-out-from-privacy-statement-scope/
Accessed: June 29, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Related Analysis

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
Start Compliance free trial

Or start with Monitor →

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

Frequently Asked Questions

What does Salesforce's Processor Carve-Out from Privacy Statement Scope clause do?

Consumers whose data is held in a company's Salesforce CRM cannot rely on this Privacy Statement for rights against Salesforce. They must look to the company that collected their data in the first place.

How does this clause affect you?

If your personal data is stored by a business using Salesforce as their CRM tool, this Privacy Statement does not govern that data. Your rights regarding that data must be exercised with the business that collected it, not directly with Salesforce.

Is ConductAtlas affiliated with Salesforce?

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