eucsoft

Wire

Messaging · wire.com · last read 2026-11-16

At a glance

Is Wire GDPR compliant?
No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Wire itself publishes, each answer linked to its source and the date we read it.
Does Wire have a data processing agreement (DPA)?
Yes. Wire publishes a data processing agreement at wire.com. It describes how a new subprocessor is announced but states no notice period. It commits to telling you of a personal data breach within 48 hours. Source and date
Which version of the Wire DPA is current?
On 2026-11-09, Wire's DPA at wire.com printed “Last Update: March 12, 2025”. Source and date
Is Wire ISO 27001 certified?
Wire states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. In Wire's words: “Wire is proudly ISO 27001 and ISO 27701 certified, demonstrating our commitment to protecting your data and privacy.” We read this on 2026-10-08. Source and date
How does Wire transfer personal data out of the EU?
Wire's agreement relies on the EU standard contractual clauses. We found no entry for Wire on the official Data Privacy Framework List. Source and date
Does Wire offer EU data residency?
The EU is the default region for this vendor. Source and date
Who are Wire's subprocessors?
Wire lists 11 third-party subprocessors; 1 of them name at least one processing country outside the EEA. We last read the list on 2026-10-08. Source and date
How do you report a security vulnerability to Wire?
Wire publishes a security.txt at wire.com naming vulnerability-report@wire.com or security@pydio.com or https://account.wire.com/user-profile/?id=7c83c960-43cf-40c5-b17e-1fda33ad8b63 or https://account.wire.com/user-profile/?id=c95740dd-1ff7-48dd-b946-8b36ea25ebad. Source and date

The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.

Identity

Legal entityWire Swiss GmbH
HQCH
Parent company—
Ultimate ownership—
EU contracting entity—
LEI5299009GLMJXTGQK5061
US CLOUD Act reachNot determined from the sources read
Sourcewire.com · 2026-10-08

Legal entity from the vendor's own terms. LEI, registered country and parent company from the Global LEI Index (GLEIF); ownership is left empty where GLEIF names no parent. The CLOUD Act row is arithmetic over those countries, not an assessment of risk.

Wire data residency

RegionEU data locationMinimum planSourceObserved
EUEU by default—wire.com2026-10-08

EU: The document says Wire's servers are in Germany and Ireland, under "Servers in the EU / European data sovereignity". It doesn't name a plan, an option the customer has to choose, or a cost.

The same question for every vendor: where SaaS vendors store EU data.

Wire's subprocessor list names AWS for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.

Subprocessor chain

11 third parties · 1 of the vendor's own group companies · 1 with a country outside the EEA · all read 2026-10-08

SubprocessorCountryPurpose
Amazon Web Services EMEA SARLEUHosting
Box, Inc.EUSignature Management
Cloud TempleEUInfrastructure for processing/hosting Wire Drive content for customers subscribed to the EU sovereign instance
Cloud Temple SASEUWire Drive hosting (EU sovereign instance only)
ContractHero GmbHEUContract Management
Countly Ltd.DEProduct Analytics
Google Cloud EMEA LimitedEUE-mail provider
Hubspot Inc.EUWebsite Hosting & Marketing Activities, CRM Services
Salesforce, Inc.DECRM Services
Stripe Payments Europe, Limited (SPEL)USPayment Services
Zendesk, Inc.EUCustomer Support
Wire's own group companies listed as subprocessors (1)
CompanyCountryPurpose
Wire Germany GmbH—Development of the 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 · wire.com

TermWhat the agreement says
Transfer mechanismSCC (module not stated)
Notice of new subprocessorsAdvance notice in writing or text form, including the planned date of the change; no notice period stated
If you object to onePrincipal may object within fourteen days of notice
Obligations passed to subprocessorssubcontracting based on a contractual agreement in accordance with Article 28 (2) to (4) GDPR
Breach notificationwithin 48 hours
Deletion when the service endswhen the services end, or on the Principal's request, Wire hands over or destroys/erases the data in a data-protection compliant manner, unless Art. 17(3) GDPR reasons conflict; deleted data may remain in encrypted backups for a limited period under ordinary overwrite cycles, and in security/operational logs for a limited period
Getting your data backwhen the services end, or on the Principal's request, Wire hands over all documents, processing results and related data files, as an alternative to erasing them
Requests from data subjectsrequests sent directly to Wire are forwarded to the Principal immediately and handled only on documented instructions; Wire may charge for support
AuditInspections by Principal or designated auditor after consultation, during normal operating hours without disruption; evidence may be codes of conduct, certifications, third-party reports (e.g. ISO/IEC 27001/27701); on-site may require NDA; Wire may claim appropriate remuneration
AuditWire may provide current certificates, reports or excerpts from independent bodies (e.g. auditors, DPOs, IT security audits) as evidence of its measures; approved codes of conduct or certifications are also acceptable
Processing on your instructionsonly on the Principal's documented instructions, unless required by law (Wire notifies the Principal first unless prohibited on public-interest grounds)
Confidentiality of staffonly employees bound by confidentiality obligations and familiar with data protection provisions process personal data
Security measuresdata processing security per Art. 28(3)(c) and Art. 32 GDPR, with measures appropriate to the risk

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 Update: March 12, 2025 at wire.com

Last updated 2025-03-12

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

Is Wire ISO 27001 certified?

Wire states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-10-08.

  • Claimed “Wire is proudly ISO 27001 and ISO 27701 certified, demonstrating our commitment to protecting your data and privacy.”

Source: wire.com, 2026-10-08

On the same list Wire also names ISO/IEC 27701. Each standard's page says how it relates to ISO/IEC 27001.

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.

SchemeStatusScopeSourceObserved
Cyber Essentials · CyberEssentialsClaimed—wire.com2026-10-08
ISO 27001 · ISO27001Claimed—wire.com2026-10-08
ISO 27701 · ISO27701Claimed—wire.com2026-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

RegisterOffering, as the register names itStatusLevelValid untilObserved
Global LEI Index (GLEIF)Wire Swiss GmbH · Wire Swiss GmbHISSUEDCH2027-03-242026-10-09

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

ProductSupport periodStateSBOMSourceObserved
Wire—Not declaredunknownsupport.wire.com2026-10-19

Vulnerability reporting: vulnerability-report@wire.com, security@pydio.com, account.wire.com, account.wire.com (security.txt, expires 2027-08-01; read 2026-10-17)

How other vendors publish theirs: security.txt across the registry.

Documents

What we read, how it was disclosed, and when.
DocumentDisclosureTranscriptionHTTPObserved
certificationsPublicfull2002026-10-08
dpaPublicfull2002026-10-09
lifecyclePublicfull2002026-10-19
residencyPublicfull2002026-10-08
subprocessorsPublicfull2002026-10-08
tiaPublicfull2002026-10-20

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.