Where 38 SaaS vendors publish their subprocessor lists
The link to each vendor’s subprocessor list and how it announces changes, as its own pages state. Subscribe to the vendors you rely on, so a new subprocessor does not reach your data unnoticed.
| Vendor | List | How changes are announced | Source |
|---|---|---|---|
| Subprocessor list | Customers can subscribe to change notifications through a form on the list page. The DPA commits to at least ten days' written notice of a new subprocessor, with objections by email to legal@airtable.com within ten business days. | airtable.com | |
| Subprocessor list | AWS updates the list at least 30 days before engaging a new sub-processor and emails changes to people who subscribe for updates. | aws.amazon.com | |
| Subprocessor list | Customers who subscribe to updates are notified by email ten business days before a new subprocessor is authorised, or as soon as reasonably practicable in an emergency. Customers may object within 30 days. | asana.com | |
| Subprocessor list | Customers can subscribe by email to sub-processor updates; Atlassian notifies subscribers at least 30 days before a new sub-processor processes customer personal data. | atlassian.com | |
| Subprocessor list | Box updates the page when subprocessors change and offers opt-in email notifications; no notice period is stated on the page. | box.com | |
| Subprocessor list | Customers who subscribe to notifications get at least 30 days' notice before a new sub-processor takes effect and may object within 30 days; customers who do not subscribe waive prior notice. | calendly.com | |
| Subprocessor list | Canva posts details at least 30 days before adding or replacing a sub-processor and offers a notification sign-up. Customers may object by email within 10 days of notification. | canva.com | |
| Subprocessor list | ClickUp emails notice at least 30 days before a new subprocessor processes customer personal data, and customers may object in writing within ten business days, with termination as the sole remedy if unresolved. | clickup.com | |
| Subprocessor list | Cloudflare adds new sub-processors to the public list at least 30 days before they start processing personal data and offers an RSS feed for changes. Customers may object on reasonable data protection grounds within 10 days of notification. | cloudflare.com | |
| Subprocessor list | Datadog updates the public list at least 30 days before appointing a new subprocessor and offers change notifications through the list page. Customers may object on reasonable data protection grounds by emailing privacy@datadoghq.com within 15 days of a change notice. | datadoghq.com | |
| Subprocessor list | The DPA says the list is on the Deel Trust Center with a subscription for notices, and Deel aims to give 30 days' notice of changes and no less than 15 days in any event. Customers may object in writing on reasonable data protection grounds within 15 days. | deel.com | |
| Subprocessor list | Docusign gives 30 days' prior notice of new subprocessors, posted as Trust Center alerts with an RSS feed; customers with a reasonable objection may terminate if no alternative is offered. | docusign.com | |
| Subprocessor list | Dropbox informs subscribed customers of new sub-processors in advance; customers may object within 60 days of notice or of publication, and may terminate if the objection cannot be accommodated. | assets.dropbox.com | |
| Subprocessor list | Customers who subscribe through the sign-up form receive written notice at least 15 days before a new sub-processor begins processing customer content, and may object on reasonable data protection grounds during that period. | figma.com | |
| Subprocessor list | Fireflies.ai will notify customers of changes to the subprocessor list before engaging a new subprocessor, and customers have 30 days from notice to object by email. | fireflies.ai | |
| Subprocessor list | GitHub updates the list and notifies subscribers (via gh.io/subscribe) 30 days before a new subprocessor gets access to Customer Personal Data; customers who object may terminate the affected subscription without penalty. | github.com | |
| Subprocessor list | Customers can subscribe to change notifications on the list page, and Gong notifies before a new sub-processor processes customer data without stating a notice period. Objections must reach Gong in writing within five business days of the notice. | gong.io | |
| Subprocessor list | Google notifies the customer's notification email address at least 30 days before a new subprocessor starts processing Customer Data; the customer may object by terminating within 90 days. | cloud.google.com | |
| Subprocessor list | One subprocessor list covers Grammarly, Superhuman Mail, Docs, Superhuman Go and GPTZero. Customers who opt in through a form linked from the list get at least 30 days' notice of new subprocessors and may object on data protection grounds. | superhuman.com | |
| Subprocessor list | Customers who opt in to email updates through HubSpot's subscription form are notified at least 30 days before a change and may object within 30 days. | legal.hubspot.com | |
| Subprocessor list | Intercom notifies customers at least 20 days before adding or replacing a sub-processor; customers join the notification list by emailing dataprotection@intercom.io and may object within 20 days. | intercom.com | |
| Subprocessor list | Under the DPA Jasper gives 10 days' notice of a new sub-processor, and customers may object in writing within those 10 days. The public list (version 4, effective 28 October 2025) says notice is given by updating that page. | jasper.ai | |
| Subprocessor list | Loom is covered by Atlassian's sub-processor list. Customers who subscribe by email are notified at least 30 days before a new sub-processor processes personal data and may object during that period, with termination of the affected product as the sole remedy. | atlassian.com | |
| Subprocessor list | Microsoft updates the Online Services Subprocessor List at least six months before a new subprocessor processes Customer Data; AI subprocessors get at least 30 days' notice with an option to disable them, and other personal data at least 30 days. | learn.microsoft.com | |
| Subprocessor list | Subscribed customers get at least 10 days' notice before a new subprocessor is engaged and may object within 30 days. | miro.com | |
| Subprocessor list | Changes are published as Sub-processor Notices to customers who subscribe to updates. Customers may object within seven days of publication, and may terminate the affected services if no workaround is found within 30 days. | monday.com | |
| Subprocessor list | Notion publishes a subprocessor list and says subprocessors are reviewed at least annually. The public pages we checked do not say how changes are announced or give a notice period. | trust.notion.com | |
| Subprocessor list | Customers subscribe by emailing subprocessors@okta.com with an executed DPA; Okta notifies subscribers before authorising a new subprocessor, and customers may object within 30 business days. No fixed advance notice period is stated. | okta.com | |
| Subprocessor list | The trust portal lists a Subprocessors item. The public pages we checked do not say how changes are announced or give a notice period. | trust.openai.com | |
| Subprocessor list | Otter.ai says it will endeavour to notify the account owner of new subprocessors to the extent the agreement requires and posts updates on the page. Under the DPA customers may object within 30 days of notice, and if Otter.ai keeps the subprocessor it informs the customer at least 30 days before it processes customer personal data. | otter.ai | |
| Subprocessor list | The DPA says the current list is on the trust center, and customers subscribe to new sub-processor notices by emailing privacy@rippling.com, with 30 days to object after notice. The list on app.rippling.com requires a login, and prospects must ask their sales representative for access. | app.rippling.com | |
| Subprocessor list | Customers with an active subscription can subscribe to notifications of new sub-processors through a form; Salesforce notifies subscribers before authorising a new sub-processor and customers may object within 30 days of the notice. | salesforce.com | |
| Subprocessor list | Slack's sub-processors are listed in Salesforce's combined Infrastructure and Sub-processors document (published 2 November 2026). Customers with an active subscription can subscribe to notifications of new sub-processors via a form; no notice period is stated in the document. | salesforce.com | |
| Subprocessor list | Users who subscribe to email notifications get at least 30 days' notice of new subprocessors and may object within 30 days. | stripe.com | |
| Subprocessor list | One list covers Twilio, SendGrid and Segment services, and customers can subscribe to change notifications. Subscribers get at least 30 days' notice of new infrastructure providers and at least 10 days for other sub-processors, and may object in writing within that notice period. | twilio.com | |
| Subprocessor list | Customers can register to receive notifications of new subprocessors. No notice period is stated on the list page. | workday.com | |
| Subprocessor list | Zendesk updates its Sub-processor Policy at least 30 days before a new sub-processor takes effect, with optional email notification; customers may object within 30 days. | zendesk.com | |
| Subprocessor list | Under the DPA, Zoom notifies customers at least 30 business days before a new sub-processor starts processing, by email to addresses subscribed on the sub-processor page (7 business days after the fact in emergencies); customers may object within 15 business days. | media.zoom.com |
Not on this list
These vendors did not publish a subprocessor list on the pages checked. That is not proof they lack it; ask them.
Tell us which one. We add profiles every week and email you when yours is live.
More lists
Terms used here
Questions about this list
How much notice must a vendor give before adding a subprocessor?
Whatever the DPA says. GDPR Article 28 requires that you can object, but the notice period is contractual. The table shows what each vendor states.
Where does this come from?
From each vendor’s own trust center, security, legal and privacy pages, as recorded in its profile. Every row links to the page it rests on, so check the source before you rely on it.