eucsoft

Data processing agreements of 120 SaaS vendors: Article 28 terms compared

We read the data processing agreement each vendor publishes and recorded what it commits to: how personal data leaves the EEA, how much warning you get before a new subprocessor, how fast you hear about a breach. Here are the counts, with every agreement one click away.

114of 120 rely on the EU standard contractual clauses
30 daysmedian notice of a new subprocessor, where a period is stated (80 of 120)
30of 120 put a number of hours on breach notification
20of 120 say anything about a transfer impact assessment

What Article 28 GDPR requires, and what the DPAs say

A data processing agreement (DPA) is the contract GDPR Article 28 requires whenever a vendor processes personal data on your behalf. It has to describe the processing (subject-matter, duration, nature and purpose, types of data, whose data) and oblige the vendor to do the things in the table below.

The article says what the contract must cover, not how long anything takes. It sets no number of days for notice of a new subprocessor, none for objecting to one, and no deadline in hours for telling you about a breach. Each agreement fills those in itself, and that is what we counted. We record 5 of the 11 points; the rest are marked as not recorded, which is a gap in our reading, not in the agreements.

RequirementDPAsWhat they say
Process only on your documented instructions
Art. 28(3)(a)
—Not recorded yet
Transfer data outside the EEA only on those instructions, under a lawful mechanism
Art. 28(3)(a); Art. 44 to 46
116 of 120name a transfer mechanism they rely on; 114 rely on the standard contractual clauses. Details
Bind staff who handle the data to confidentiality
Art. 28(3)(b)
—Not recorded yet
Take the security measures Article 32 requires
Art. 28(3)(c)
—Not recorded yet
Engage a subprocessor only with your authorisation, and tell you of changes
Art. 28(2), 28(3)(d)
118 of 120say how a new subprocessor is announced; 7 to 180 days of notice (80 state a number). Details
Give you the chance to object to a new subprocessor
Art. 28(2)
117 of 120say how you can object; 5 to 90 days to object (68 state a number). Details
Pass the same obligations down to each subprocessor
Art. 28(4)
—Not recorded yet
Help you answer people exercising their rights
Art. 28(3)(e)
—Not recorded yet
Help you with security, breach notification and impact assessments
Art. 28(3)(f); Art. 33(2)
118 of 120say when they tell you of a breach; 24 to 72 hours (30 state a number). Details
Delete or return the data when the service ends
Art. 28(3)(g)
—Not recorded yet
Give you the information to show compliance, and allow audits
Art. 28(3)(h)
119 of 120set out audit or information rights. Details

This compares published agreements; it is not a template. Ranges are the lowest and highest figure any agreement states, counted as written (some mean business days). A term an agreement does not mention is left out of the range, not counted as zero.

How data leaves the EEA

A transfer mechanism is what makes it lawful to move personal data out of the EEA. We count only the mechanisms an agreement relies on, not ones it lists as possible. Most agreements rely on several at once, so the rows add up to more than 120.

Mechanism the agreement relies onVendorsShare
Standard contractual clauses (any module)11495%
SCC module 2 (controller to processor)8067%
SCC module 3 (processor to processor)6857%
SCC module 1 (controller to controller)2521%
SCC module 4 (processor to controller)1412%
UK Addendum to the SCCs8369%
Swiss FADP clauses5143%
EU-U.S. Data Privacy Framework4941%
UK IDTA108%
Binding Corporate Rules54%

49 agreements name the EU-U.S. Data Privacy Framework, almost always next to the standard contractual clauses rather than instead of them. Whether a vendor is actually on the DPF list today is a separate question, answered from the official register on the transfers page. 4 agreements name no mechanism we could record: DATEV, Pennylane, Piwik PRO, Snowflake.

Warning before a new subprocessor

Under GDPR Art. 28(2) a processor may add a subprocessor only after telling you, so you can object. The agreement sets how much warning that is. 80 of 120 state a number of days, 38 describe how notice is given without a period, and 2 say nothing we could record.

18 under 15 days · 23%10 15 to 29 days · 13%51 30 days · 64%1 more than 30 days · 1%

The usual figure is 30 days. These 28 agreements give less, which is a shorter window for you to object, not a breach of anything:

VendorDaysAs the agreement puts it
Wix7At least 7 days before the change, by email to customers who subscribe to notifications via the sub-processor list
Aircall1010 business days prior notice of sub-processor changes (SCC Clause 9 Option 2)
Airtable10At least 10 days' written notice before authorizing new sub-processors, by email to the address in the DPA signature block
Amplitude10Schedule B (Subprocessor List) updated at least 10 business days before the new subprocessor gets access to Personal Data; email notification available by subscribing via subprocessor.notifications@amplitude.com
Asana1010 business days before authorization, automatic notice to customers subscribed to updates on the Subprocessors page (in an emergency, as soon as reasonably practicable)
Granola10At least 10 days' prior notice by updating the Subprocessor List (trust.granola.ai/subprocessors); may also notify via customer contact information, the Granola website or the Services
Lusha10At least 10 days in advance, by updating the sub-processor list; customer can sign up to receive notices of changes
Mailchimp10At least 10 days before adding or removing a subprocessor, by email to customers who subscribe via a link
Miro10At least 10 days prior notice of a new or replacement subprocessor, if the customer subscribes to notifications; Subprocessor List is updated
Mollie10Prior notice with at least 10 calendar days to object; for expedited engagements (to protect data or avoid material service disruption), notice as soon as reasonably practicable
Perplexity1010 business days' prior notice of new/replacement subcontractors (other than Model Providers), via update to Trust Center Subprocessor List and in-app/in-product notification or email (email only if Customer subscribed to alerts)
SiteGround10At least 10 days in advance, specific written notice of additions or replacements to the agreed sub-processor list
Vanta10At least 10 days before a new sub-processor processes Personal Data: added to the list at trust.vanta.com/subprocessors and notified to subscribers. Customers who do not subscribe waive prior notice.
Adobe14At least 14 days before the new sub-processor processes personal data, by email to addresses subscribed via Adobe's sub-processor website
Langdock14At least 14 days before engagement, by publication at https://trust.langdock.com/subprocessors and by email to those subscribed on that page
PostHog14at least 14 days in advance of updates to the Subprocessor list, with an opportunity to object
Postmark (ActiveCampaign)14Module Two: 14 days in advance, specific written notice to data exporter of additions/replacements to agreed list
Zapier1414 days' advance written notice, via email, a posting, online portal notification, or other reasonable means
Figma15At least 15 days before processing begins; added to sub-processor list and written notice to customers subscribed to notifications
Freshworks15At least 15 days' prior notice of planned additions or replacements to the subprocessor list
Klaviyo15At least 15 days' notice of proposed additions or replacements, by email to the designated address associated with Customer's account
Smartsheet1515 days' prior written notice to Customer's SysAdmin; temporary subprocessors notified without undue delay after appointment
SurveyMonkey1515 days' notice under SCC Clause 9 option 2 (general written authorisation)
Intercom20At least 20 days before adding or replacing Sub-processors; customers must email dataprotection@intercom.io to join the distribution list to receive notice
New Relic2121 days' prior notice of new core third-party sub-processors, provided customer signs up for notifications at the New Relic sign-up URL
Make28At least 4 weeks before engaging any new sub-processor
Snowflake2828 days in advance, by email to Sub-processor Site subscribers and to customer-designated 'privacy notices' recipients
T Cloud Public28At least four weeks in advance, express written notice to the controller of intended additions or replacements to the agreed subprocessor list

Days are counted as each agreement writes them. Some mean business days, which is longer than the number suggests; the wording beside each figure says which.

Time to object to a new subprocessor

Notice is only useful if you can act on it. Article 28(2) gives you the opportunity to object; the agreement decides how long you have and what objecting leads to. 117 of 120 agreements say how you can object, and 68 of them give a number of days, from 5 to 90. The median is 15 days. The others tie the objection to the notice period or to "before the subprocessor is engaged", or set no period.

9 under 10 days · 13%26 10 to 15 days · 39%3 16 to 29 days · 4%25 30 days · 37%4 more than 30 days · 6%

Counted from the day of notice, as each agreement writes it; business days, calendar days and weeks are kept as written (four weeks is shown as 28). At Google the way to object within the 90 days is to end the agreement. Mollie's agreement states two figures, 5 and 10 days; both are shown as written, and it is left out of the median and the bar. What happens after an objection, often good-faith talks and then the right to end the affected service, is quoted on each vendor's page.

Hearing about a breach

You have 72 hours to notify your supervisory authority of a personal data breach (GDPR Art. 33), so how fast your processor tells you matters. 30 of 120 agreements commit to a number of hours. Of the rest, 82 promise notice "without undue delay", the phrase Art. 33(2) uses, and leave the clock to you.

VendorHoursAs the agreement puts it
Aircall24promptly after detection; no later than 24 hours after detection where European Data Protection Law applies; by email to Admin User Email Address
3DS Outscale48as rapidly as possible once aware, at the latest within 48 hours, by email
Anthropic48without undue delay, in any event within 48 hours, in writing
Cursor48without undue delay, and in any event within 48 hours
Netlify48without undue delay, and in any event within 48 hours
Piwik PRO48without undue delay; if possible within 48 hours of becoming aware
Stripe48without undue delay; no later than 48 hours for data subject to the GDPR or UK GDPR, after becoming aware
Supabase48without undue delay and, where feasible, within 48 hours
Wire48within 48 hours
Zapier48without undue delay, and not later than 48 hours after discovery
Zendesk48without undue delay and within 48 hours of a confirmed personal data breach
1Password72within 72 hours (or otherwise without undue delay) of becoming aware of a material Personal Data Breach
Airtable72without undue delay, and in any event no later than 72 hours after substantiation
Apollo.io72without undue delay, and in any event within 72 hours of confirmation
Atlassian72without undue delay and, where feasible, within 72 hours of becoming aware
Attio72without undue delay and in any event within 72 hours of becoming aware
CookieYes72without undue delay, and in any event within 72 hours of discovery
Databricks72without undue delay and no later than 72 hours after becoming aware, in writing
Dropbox72promptly and without undue delay; commercially reasonable efforts to notify within 72 hours of confirming a Security Incident
Figma72without undue delay and, where feasible, within 72 hours
Granola72without undue delay (typically within 72 hours)
HubSpot72without undue delay, no later than 72 hours after becoming aware
KnowBe472without undue delay and, where feasible, no later than 72 hours after becoming aware
Lusha72without undue delay and, where feasible, within 72 hours of becoming aware
Microsoft72without undue delay and, in any event, within 72 hours
n8n72without undue delay and, where feasible, no later than 72 hours after becoming aware
OpenRouter72without undue delay and in any case within 72 hours of becoming aware
Smartsheet72without undue delay, and in any event within 72 hours of confirming the breach, in writing
Snowflake72without undue delay, and where feasible within 72 hours after becoming aware
Vimeo72without undue delay and, where feasible, within 72 hours of becoming aware

Audits and information

Article 28(3)(h) requires the vendor to give you the information you need to show compliance and to allow audits, including inspections. 119 of 120 agreements set out how. What they offer varies: a third-party report such as SOC 2 or an ISO 27001 certificate, answers to questions, an audit by you or an auditor you appoint, or several of these in turn, often with limits on how often and on how much notice you give. Those limits are written in too many ways to count fairly, so the wording is quoted on each vendor's page rather than reduced to a number here.

Transfer impact assessments

Since the Schrems II judgment, an exporter relying on standard contractual clauses has to assess whether the law of the destination country undermines them. That is your assessment to make, but a vendor can help with one. Only 20 of 120 agreements mention it at all. The documents vendors publish for it are on the transfer impact assessments page. What the agreements say:

VendorWhat the agreement says
1PasswordParties document the transfer assessment (Clause 14(b)) and make it available to the competent supervisory authority on request; importer makes best efforts to provide exporter with relevant information
AdobeOn written request, Adobe Ireland provides evidence of its evaluation of privacy and security controls for the third-country transfer, covering additional measures, safeguards and risk considerations
Anthropicon request, information reasonably necessary for Customer to complete a TIA
AtlassianInformation to help customers conduct data transfer impact assessments is published (linked)
CloudflareReasonable assistance with customer's transfer adequacy assessment, to the extent able, at customer's cost
FreshworksParties adopt additional protections required by their transfer impact assessment, if any, described in Schedule 2
Grafana LabsData Transfer Assessment for transfers to the US, published at https://grafana.com/legal
IntercomIntercom's Transfer Impact Assessment available upon request
JotformParties document the transfer assessment (Clause 14(b)) and make it available to the competent supervisory authority on request
KlaviyoOn request, vendor provides information reasonably necessary for customer to complete a TIA (or UK TRA); vendor may charge for TIA assistance
NetlifyOn customer request, Netlify provides information to assess transfers, including applicable transfer impact assessments, subject to confidentiality
OVHcloudClient must assess whether the SCCs are effective; OVHcloud will provide relevant information on request to assist
OneTrustBefore transferring Data outside the EEA, OneTrust reviews the adequacy of data protection in the third country and applies supplementary measures where necessary
PleoPleo performs transfer impact assessments as required under applicable data protection laws, including the GDPR
Postmark (ActiveCampaign)Exporter is responsible for checking whether the laws of the destination country stop the Importer from complying; the Importer will make commercially reasonable efforts to tell the Exporter if it can no longer comply
SiteGroundSiteGround is deemed to perform appropriate risk assessments when transferring Customer Data outside the UK, EU and EEA; nothing said about providing or publishing an assessment
VantaNo TIA document is provided; for transfers out of the EEA, UK or Switzerland, the parties meet as needed to consider whether the importer country's laws give broadly equivalent protection, whether extra measures are needed, and whether the transfer is still appropriate
ZendeskCustomer may need to perform a data transfer assessment; Zendesk provides reasonable assistance on request
ZoomZoom performs a case-by-case assessment of whether supplementary measures are needed for onward transfers to third countries
ZoomInfoParties assess local laws and practices of the destination country (Clause 14(b)), document the assessment, and make it available to the competent supervisory authority on request

An agreement that is silent may still be backed by a published assessment elsewhere on the vendor's site. This counts what the agreement itself commits to.

Download the data (CSV): every row with its source and the date it was read.Cite as: eucsoft, “What SaaS data processing agreements say”, https://eucsoft.com/en/findings/agreements/, data read up to 2026-11-09.

How this was counted

Each agreement is the one the vendor publishes, read between 2026-10-09 and 2026-11-09. A model transcribed the terms; every recorded term carries a verbatim quote, checked against the stored copy of the agreement, and a person reviewed it before it was published. Vendors whose agreement sits behind a login, an NDA or a download are not counted, so this is 120 of the 160 vendors in the registry, not all of them. The figures recalculate whenever an agreement is read again. The full method is on the methodology page.

No verdicts. A 10-day notice period or an agreement without a breach deadline is a fact about a contract, not a judgement of the vendor. Whether it is acceptable depends on what you process with the tool, which is yours to decide.