Xero
Accounting · xero.com · last read 2026-11-16
At a glance
- Is Xero GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Xero itself publishes, each answer linked to its source and the date we read it.
- Does Xero have a data processing agreement (DPA)?
- Yes. Xero publishes a data processing agreement at xero.com. It gives 30 days' notice before a new subprocessor is added. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the Xero DPA is current?
- On 2026-11-09, Xero's DPA at xero.com printed “Last updated on 11 February 2025”. Source and date
- Does Xero have a SOC 2 report?
- Xero says a SOC 2 report is available on request (no type given). In Xero's words: “If you don’t have a Xero login, you can request the latest available ISO 27001 certificate or SOC 2 report by completing a request form.” We read this on 2026-10-08. Source and date
- Is Xero ISO 27001 certified?
- Xero states ISO/IEC 27001 certification (2022 edition, as Xero names it), and says the certificate or audit report is available on request. In Xero's words: “Xero is certified as compliant with ISO/IEC ISO27001:2022, the premier global information security management system (ISMS) standard.” We read this on 2026-10-08. Source and date
- How does Xero transfer personal data out of the EU?
- Xero's agreement relies on the EU standard contractual clauses and the UK transfer addendum. We found no entry for Xero on the official Data Privacy Framework List. Source and date
- Where does Xero store EU customer data?
- We found no statement of an EU data location on a page we could reach. Not the same as none existing. Source and date
- Who are Xero's subprocessors?
- Xero lists 21 third-party subprocessors; 21 of them name at least one processing country outside the EEA. We last read the list on 2026-10-08. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Xero (NZ) Limited |
|---|---|
| HQ | NZ |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | — |
| US CLOUD Act reach | Not determined from the sources read |
| Source | xero.com · 2026-10-08 |
Data location
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Not stated | — | xero.com | 2026-10-08 |
The same question for every vendor: where SaaS vendors store EU data.
Xero's subprocessor list names AWS, Microsoft and Google for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
21 third parties · 11 of the vendor's own group companies · 21 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| Adobe | US | Electronic signing service provider |
| Amazon Web Services | US | Cloud infrastructure service provider |
| Anthropic | US | Conversational artificial intelligence services |
| Avalara | US | Sales tax look-up (United States) |
| CloudFactory | GB | Data extraction and processing |
| Confluent | US | Cloud infrastructure service provider |
| Datadog | US | Cloud monitoring service provider |
| Fivetran | US | Cloud infrastructure services provider |
| Google Cloud Platform | US | Cloud infrastructure service provider |
| Infosys | IN | Technology consulting provider |
| Mailgun Technologies | US | Transactional email processing |
| Microsoft Azure | US | Cloud infrastructure service provider |
| Mixpanel | US | Platform instrumentation |
| OpenAI | US | Conversational artificial intelligence services |
| Snowflake | US | Cloud infrastructure service provider |
| Stripe | US | Online payment processing |
| Sumo Logic | US | Cloud monitoring service provider |
| Superchoice | AU | Payroll processing (Australia) |
| Tink | GB | Bank feed aggregator (UK) |
| Twilio Inc | US | cloud communications provider |
| Yodlee | US | Bank feed aggregator (US) |
Xero's own group companies listed as subprocessors (11)
| Company | Country | Purpose |
|---|---|---|
| Syft Analytics Group South Africa Proprietary Limited | — | support and similar services |
| Syft Analytics Inc. | — | support and similar services |
| Syft Analytics Operations South Africa Proprietary Limited | — | support and similar services |
| Xero (NZ) Limited | NZ | support and similar services |
| Xero (Singapore) Pte. Ltd. | SG | support and similar services |
| Xero (UK) Limited | GB | support and similar services |
| Xero Australia Pty Limited | AU | support and similar services |
| Xero Limited | NZ | support and similar services |
| Xero Software (Canada) Ltd. | CA | support and similar services |
| Xero South Africa (Pty) Ltd. | ZA | support and similar services |
| Xero, Inc. | US | support and similar services |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · xero.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | SCC module 3 |
| Transfer mechanism | Swiss FADP clauses |
| Transfer mechanism | UK Addendum |
| Notice of new subprocessors | At least 30 days' notice, by updating its online sub-Processors page |
| If you object to one | Customer may object on reasonable data protection grounds within 14 days of notice; Xero will discuss a resolution; if none is possible, Xero may decline the appointment or suspend/terminate on one month's notice, or Customer may terminate on one month's written notice |
| If you object to one | If the objection can't be resolved, Customer may terminate the Agreement with one month's written notice |
| Obligations passed to subprocessors | Data protection terms imposed on sub-processors requiring protection to the standard of Applicable Data Protection Law and consistent with the Addendum; Xero remains liable for sub-processor breaches |
| Breach notification | without undue delay |
| Deletion when the service ends | After a 7-year post-termination retention period (or sooner at Customer's request), Xero deletes or returns the Data, unless applicable law requires retaining some or all of it |
| Getting your data back | On termination or expiry Xero retains a copy of the Data for 7 years so the Customer can regain access, then deletes or returns it |
| Requests from data subjects | Reasonable and timely assistance (at Customer's expense) where platform functionality is insufficient; requests made directly to Xero: advises the person to contact the Customer and promptly informs the Customer with full details |
| Audit | Xero audited against SOC 2 and ISO/IEC 27001:2022 by an independent third party; on request, subject to confidentiality, a copy of the SOC 2 report is provided to the customer or its non-competitor third-party auditor. The DPA states no on-site audit right. |
| Processing on your instructions | Xero processes Personal Data on the Customer's behalf in accordance with its documented instructions, which are set out in full in the Agreement and this Addendum; any change must be agreed in writing |
| Confidentiality of staff | Persons authorised to process the data are subject to a duty of confidence aligned with Xero's confidentiality obligations under the Agreement |
| Security measures | Appropriate technical and organisational measures for the duration of the Agreement, including the measures in Annex A |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
On 2026-11-09, the agreement printed: Last updated on 11 February 2025
at xero.com
Last updated 2025-02-11
This version is in our copies from 2026-10-09.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
Assurance
Does Xero have a SOC 2 report?
Xero says a SOC 2 report is available on request (no type given). We read this on 2026-10-08.
- Available on request “If you don’t have a Xero login, you can request the latest available ISO 27001 certificate or SOC 2 report by completing a request form.”
Source: xero.com, 2026-10-08
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
Is Xero ISO 27001 certified?
Xero states ISO/IEC 27001 certification (2022 edition, as Xero names it), and says the certificate or audit report is available on request. We read this on 2026-10-08.
- Available on request “Xero is certified as compliant with ISO/IEC ISO27001:2022, the premier global information security management system (ISMS) standard.”
Source: xero.com, 2026-10-08
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| ISO/IEC ISO27001:2022 · ISO27001 | Available on request | — | xero.com | 2026-10-08 |
| PCI DSS v4.0, SAQ A · PCIDSS | Claimed | We're a level 2 merchant & outsource card processing to level 1 providers. | xero.com | 2026-10-08 |
| SOC 2 · SOC2 | Available on request | Xero’s cloud-based accounting system | xero.com | 2026-10-08 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Xero
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Xero
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Xero
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Xero
- Data Privacy Framework List (US): checked 2026-11-16, no entry under Xero
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Xero
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Xero
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Xero
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Xero
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Xero
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
Not yet collected. This row will say not declared only once we have read a lifecycle or security page and found no period stated — see support windows.
Vulnerability reporting: no security.txt at the well-known path (read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-10-08 |
| dpa | Public | full | 200 | 2026-10-09 |
| residency | Public | full | 200 | 2026-10-08 |
| subprocessors | Public | full | 200 | 2026-10-08 |
History
Nothing has moved since we started watching this vendor on 2026-10-08. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.