Salesforce DPA: Yes — What the SFDC Data Processing Addendum Covers
Does Salesforce offer a DPA under GDPR Art. 28?
Yes. Salesforce publishes its Data Processing Addendum as a pre-signed PDF on its legal hub. The SFDC DPA covers the Art. 28 GDPR processor framework, uses Salesforce Processor BCRs plus SCC Modules 2 and 3, and becomes binding once the customer signs page 6 and returns it.
- The Salesforce DPA is downloadable without a gate from the customer-agreements legal hub.
- It binds only after execution: sign page 6 and email it to Salesforce with your Account Number.
- Transfer mechanisms are Salesforce Processor BCRs, SCC Modules 2 and 3, and the EU-US Data Privacy Framework.
- Sub-processors are listed in the Infrastructure and Sub-processor Documentation with a 30-day objection right.
Yes — Salesforce offers a Data Processing Addendum (DPA) under GDPR Art. 28, and salesforce.com publishes the current document, pre-signed by SFDC, as a PDF on its legal hub. The Salesforce DPA (Revision August 2026, 17 pages) forms part of the Main Services Agreement or the applicable Order Form and covers the full Article 28 processor framework: processing on documented instructions, confidentiality, sub-processors, security certifications and audits, incident notification, government requests, and deletion. Transfers rest on the Salesforce Processor BCRs, EU Standard Contractual Clauses (Modules 2 and 3), and the EU-US Data Privacy Framework. Unlike most vendor DPAs, it binds only after you sign page 6 and return it to Salesforce.
This document companion walks through the DPA clause by clause, maps it against the Art. 28 GDPR checklist, and shows how German buyers execute and file it. It reflects the Salesforce legal-hub version as of November 2026 and provides general information, not advice on a specific deployment. For the broader vendor review — CRM, AI features, and the contract stack — see our Salesforce overview.
What the Salesforce DPA covers: clause-level index
The Salesforce DPA is a 17-page document with a 14-section main body and two schedules: Schedule 1 sets out the transfer mechanisms for European data transfers; Schedule 2 describes the processing and doubles as the SCC annex. Verify each element against your actual deployment rather than treating the DPA as a checkbox:
| DPA section | What the Salesforce DPA provides | What to verify for your deployment |
|---|---|---|
| How this DPA applies | Attaches to the Main Services Agreement or Order Form; the SFDC entity on that contract is the DPA party | Your signing entity must be party to the Agreement or Order Form — otherwise invalid |
| §2 Processing | Processing only on your documented instructions, for the Services and uses described in Schedule 2 | Intended uses (incl. AI features) sit within the documented scope |
| §3–§4 Rights, personnel, DPO | SFDC notifies, redirects, and assists with data subject requests; personnel confidentiality and training; group data protection officer appointed | Your response workflows; contact paths ([email protected]) in your vendor record |
| §5 Sub-processors | Written agreements; current list and notification subscription in the Infrastructure and Sub-processor Documentation; 30-day objection right; termination plus refund if no change within 60 days | Subscribe to notifications and archive the current list with its review date |
| §6 Security and audit | Measures per the Security, Privacy and Architecture Documentation; ISO 27001 and SSAE 18 SOC 2 maintained where obtained; audit program with third-party reports and conditional on-site audit (once per year, three weeks’ notice) | Certifications cover the Services you bought; DPIA assistance on request |
| §7–§8 Incidents and government requests | Incident notification without undue delay; prompt notification and challenge of unlawful government requests, with a no-back-door certification | Your breach-notification chain; documented reliance for transfer impact assessments |
| §9 Return and deletion | Return and deletion per the Security, Privacy and Architecture Documentation procedures | Deletion evidence at contract end, incl. backups |
| §10–§11 Affiliates and liability | Coverage of your affiliates; liability subject to the Agreement’s Limitation of Liability | Group entities named; liability exposure understood |
| §12 Europe provisions | BCRs, SCC Module 2 and 3 (Decision (EU) 2021/914), EU-US Data Privacy Framework recognition; Europe defined as EU, EEA, Switzerland, UK; local-laws notification with termination and refund remedy | Your transfer documentation and which mechanism applies to your flows |
| Schedule 2 | SCC annex: parties, data subject and data categories, sensitive-data stance, frequency, duration, TOMs | Your actual CRM data matches the described categories, incl. the sensitive-data clause |
Two features deserve special attention. First, the execution mechanics: the DPA arrives pre-signed by SFDC but binds only when Salesforce receives your validly completed document — treat execution as a hard gate, not a formality. Second, the transfer stack: processor BCRs combined with SCC Modules 2 and 3 are a stronger baseline than SCC-only DPAs, because BCRs survive changes that would force SCC re-papering.
The DPA also takes a notably open stance on sensitive data: Schedule 2 states that customers may submit special categories of data, with security measures described in the Security, Privacy and Architecture Documentation. That differs sharply from AI-vendor DPAs such as Cursor, which prohibit such data outright. The breadth shifts the diligence burden to you: HR-adjacent CRM records, health-related support tickets, and similar Article 9 material need a dedicated review, not just a signature.
GDPR procurement guidance: executing the Salesforce DPA in Germany
Treat the Salesforce DPA as the anchor document of the vendor file — five steps turn it into a defensible deployment record:
- Fix the contract path. The DPA binds the SFDC entity party to your Main Services Agreement or Order Form — the document notes this may be a different entity than Salesforce, Inc., the pre-signed data importer in Schedule 2. Confirm which Salesforce entity is on your Order Form and match the signing entity to it; a signature by a non-contracting group entity leaves the document invalid.
- Execute, don’t just download. Complete the signature box on page 6, have an authorized signatory sign, and email the document to [email protected] with your Account Number from the Order Form or invoice — binding occurs on SFDC’s receipt.
- Document the transfer stack. Record that BCRs, SCC Modules 2 and 3, and the EU-US Data Privacy Framework are the transfer bases, subscribe to new-sub-processor notifications, and archive the current Infrastructure and Sub-processor Documentation.
- Map data categories against Schedule 2. List what actually flows through Salesforce — customer contacts, employee records, support tickets, AI feature inputs — and confirm each matches the Schedule 2 description; flag any Article 9 GDPR material for a dedicated review.
- Register the deployment. Enter the Salesforce deployment in your Art. 30 record of processing activities, referencing the DPA revision, execution date, and audit evidence path (ISO 27001, SOC 2 via the Trust and Compliance Documentation).
For the full procurement framework — assessment criteria and documentation templates — see our GDPR AI procurement guide; German-speaking teams find the same framework in our KI-Beschaffung guide.
Art. 28 GDPR checklist for the Salesforce DPA
Article 28(3) GDPR prescribes the minimum content of a processor agreement; applied to the Salesforce DPA, the checklist looks like this:- [ ] Processing on documented instructions — §2.2 binds SFDC to process only under your instructions, the Agreement, and the Order Forms
- Confidentiality commitments — §4.1: personnel under written confidentiality agreements with training and access limits
- Security measures — §6.1 ties measures to the Security, Privacy and Architecture Documentation; cross-check against your Art. 32 GDPR requirements
- Subprocessor regime — §5: published list, notification subscription, 30-day objection right, 60-day change window with termination and refund; SFDC liable for sub-processors (§5.4)
- Data subject rights assistance — §3: notification, redirection, and assistance duties
- Deletion or return — §9: return and deletion per the Security, Privacy and Architecture Documentation; confirm evidence at contract end
- Audit and information duties — §6.3: third-party audit reports on written request and a conditional on-site audit (once per year, three weeks’ notice)
- Transfer safeguards — §12 and Schedule 1: BCRs, SCC Modules 2 and 3, EU-US Data Privacy Framework recognition
- DPIA support — §6.4: cooperation and assistance for your data protection impact assessment
Any point the DPA plus the Trust and Compliance Documentation cannot answer should be asked in writing before rollout — the answer becomes part of the procurement record.
How to obtain and sign the Salesforce DPA
Salesforce keeps the document public and ungated but, unlike vendors whose DPA attaches automatically, requires active execution:
- Download the DPA from the For Salesforce Customers page at
salesforce.com/company/legal/customer-agreements/and save the PDF (data-processing-addendum.pdf) with the access date. A separate DPA FAQs document on the same page answers recurring questions. - Check the revision. The version reviewed for this page is Revision August 2026, a 17-page PDF; note the revision line under the title to detect changes at renewal.
- Complete page 6. Fill in the signature box, confirm the signing entity matches your contracting entity, and have an authorized signatory sign. Signature on page 6 is deemed acceptance of the Standard Contractual Clauses including Schedule 2; if you prefer to execute the SCCs separately, also sign page 15.
- Return the document. Email the signed DPA to [email protected], stating your Account Number from the SFDC Order Form or invoice. Legal effect begins when SFDC receives the validly completed document (§14).
- Record and re-verify. Store version, execution date, and confirmation in your vendor management system and Art. 30 register; re-download and compare at renewal — Salesforce revises the DPA over time.
For comparison, the Anthropic DPA and the Claude DPA structure are incorporated into the vendor’s commercial terms and accessed via the customer portal. The Cursor DPA is public like Salesforce’s but binds through the terms of service without a return step. The Salesforce flow sits in between: public download, explicit execution, binding on receipt.
When the Salesforce DPA is not enough
The DPA answers the processor-contract question, not the deployment question. These obligations remain with you as the controller:
- Legal basis (Art. 6 and Art. 9 GDPR) — the DPA never provides your legal basis, including for CRM contact data and special-category records.
- Record of processing (Art. 30 GDPR) — document the Salesforce deployment yourself, with the DPA revision and execution date.
- DPIA (Art. 35 GDPR) — large-scale customer or employee datasets, or AI-assisted scoring, may require a data protection impact assessment; §6.4 obliges SFDC to assist.
- Works council questions — CRM and service-cloud rollouts that touch employee or customer-interaction monitoring can trigger co-determination duties under section 87(1) no. 6 BetrVG.
- AI feature specifics — Einstein AI and similar features process data under the same Agreement, but check their training and retention behavior against the product documentation and your instructions before rollout.
Compound Law advises businesses, startups, and in-house teams in Germany on AI and SaaS procurement, DPA and AVV review, transfer assessments, and CRM governance. If you want us to review your Salesforce deployment or another vendor contract before rollout, contact us.