WeTransfer

File transfer · wetransfer.com · last read 2026-11-09

Identity

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.

Data location

No data-location observation recorded yet.

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

WeTransfer'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

17 third parties · 13 with a country outside the EEA · all read 2026-10-25

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-25 · wetransfer.com

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

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

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-09, no entry under WeTransfer; Wetransfer B.V.
• ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-09, no entry under WeTransfer; Wetransfer B.V.
• CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-09, no entry under WeTransfer; Wetransfer B.V.
• DORA critical ICT third-party providers (ESAs): checked 2026-11-09, no entry under WeTransfer; Wetransfer B.V.
• Data Privacy Framework List (US): checked 2026-11-09, 1 entry under WeTransfer; Wetransfer B.V.
• ENS certificates of conformity (CCN, Spain): checked 2026-11-09, no entry under WeTransfer; Wetransfer B.V.
• EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-09, no entry under WeTransfer; Wetransfer B.V.
• FedRAMP Marketplace (US): checked 2026-11-09, no entry under WeTransfer; Wetransfer B.V.
• GPAI Code of Practice signatories (European Commission): checked 2026-11-09, no entry under WeTransfer; Wetransfer B.V.
• SecNumCloud qualified services (ANSSI, France): checked 2026-11-09, no entry under WeTransfer; Wetransfer B.V.

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-25)

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

Documents

History

Nothing has moved since we started watching this vendor on 2026-10-25. Changes appear here only after a human has reviewed them.

Every reviewed change across the registry, newest first: vendor changes.