Links last opened 26 October 2026. Record confirmed by a person on 27 October 2026. 2 recorded changes, listed below.
Sage contracts through Sage Software, Inc., registered in United States. Its trust center is published at https://trust.sage.com/. Its customer data processing agreement, also called a data processing addendum, is published by Sage itself; the link is below. Its sub-processor list is published by Sage itself; the link is below. We open those pages every day — last on 26 October 2026 — and a person last went through this record on 27 October 2026.
A ready row. Replace the purpose with what your client actually uses Sage for.
| Subprocessor | Legal entity | Country | Purpose | Transfer | DPA |
|---|---|---|---|---|---|
| Sage | Sage Software, Inc. | US | Finance | — | https://www.sage.com/en-us/legal/terms-and-conditions/product-and-service-terms-and-conditions/data-processing-agreement/ |
Changes we noticed on Sage's own pages, each with the page we saw it on. The vendor does not publish this, and neither does anyone else.
26 October 2026
I cannot provide a change note because the removed content failed to load. Please provide the specific text that was removed from Sage's data processing agreement so I can explain what changed and its significance.
25 October 2026
I don't have the actual text content of the lines that were added to Sage's data processing agreement. Without seeing the specific changes, I cannot write accurate change notes about what was modified and why it matters for your compliance documentation. Please provide the actual text of the added line(s) so I can describe the change accurately.
Enter your website: each service it loads, what it is for and links to its own DPA, in a minute or two. No sign-up.
Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.
Six of them. All finance in the registry.