WhatsApp Business
Communications API · business.whatsapp.com · last read 2026-11-16
At a glance
- Is WhatsApp Business GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what WhatsApp Business itself publishes, each answer linked to its source and the date we read it.
- Does WhatsApp Business have a data processing agreement (DPA)?
- Yes. WhatsApp Business publishes a data processing agreement at whatsapp.com. It describes how a new subprocessor is announced but states no notice period. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the WhatsApp Business DPA is current?
- On 2026-11-09, WhatsApp Business's DPA at whatsapp.com printed “Last updated: 22 August 2025”. Source and date
- Does WhatsApp Business have a SOC 2 report?
- WhatsApp Business states SOC 2 Type 2 on its own page, but does not say there how to get a report. In WhatsApp Business' words: “We have obtained SOC 2 Type II and ISO 27001 reports.” We read this on 2026-10-08. Source and date
- Is WhatsApp Business ISO 27001 certified?
- WhatsApp Business 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. Source and date
- How does WhatsApp Business transfer personal data out of the EU?
- WhatsApp LLC is on the official Data Privacy Framework List (status: Active). Source and date
- Does WhatsApp Business offer EU data residency?
- The vendor documents an EU region but states nothing about which plan reaches it or what it costs. Source and date
- How do you report a security vulnerability to WhatsApp Business?
- WhatsApp Business publishes a security.txt at whatsapp.com naming https://www.facebook.com/whitehat/report/. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | WhatsApp LLC |
|---|---|
| HQ | US |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | WhatsApp Ireland Limited |
| LEI | 984500DBD07752F00118 |
| US CLOUD Act reach | Contracting entity incorporated in the US |
| Source | whatsapp.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.
WhatsApp Business data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Terms not stated | — | developers.facebook.com | 2026-10-09 |
EU: The optional data_localization_region parameter enables local storage of data-at-rest, with "EU (Germany): DE" listed as a supported value. The document names no plan and no cost for it.
The same question for every vendor: where SaaS vendors store EU data.
Subprocessor chain
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · whatsapp.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | other |
| Notice of new subprocessors | Advance notice of sub-processor changes, subject to applicable law; period and method not stated |
| If you object to one | If the objection is reasonable, the customer may tell WhatsApp in writing and stop using the Business Services |
| Obligations passed to subprocessors | Written agreement imposing obligations on the sub-processor no less rigorous than those on WhatsApp under the Data Processing Terms; WhatsApp remains fully liable for the sub-processor's performance |
| Breach notification | without undue delay |
| Deletion when the service ends | On termination of the Business Terms, stop processing and delete personal information within the period set in the Business Terms, unless law requires further storage or WhatsApp has an independent right or obligation to use it |
| Requests from data subjects | assists the customer by appropriate technical and organisational measures, insofar as possible, to respond to data subject rights requests; no handling of requests sent directly to the vendor is specified |
| Audit | On request, the information and assistance reasonably necessary to show compliance; no on-site audit stated |
| Processing on your instructions | only in accordance with the customer's instructions as set out in the Business Terms and these Data Processing Terms |
| Confidentiality of staff | persons authorised to process are bound by appropriate obligations of confidentiality |
| Security measures | appropriate technical and organizational measures, including those listed in the Data Security Terms |
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: 22 August 2025
at whatsapp.com
Last updated 2025-08-22
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 WhatsApp Business have a SOC 2 report?
WhatsApp Business states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-10-08.
- Claimed “We have obtained SOC 2 Type II and ISO 27001 reports.”
Source: developers.facebook.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 WhatsApp Business ISO 27001 certified?
WhatsApp Business 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 “We have obtained SOC 2 Type II and ISO 27001 reports.”
Source: developers.facebook.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 27001 · ISO27001 | Claimed | Cloud API | developers.facebook.com | 2026-10-08 |
| SOC 2 Type II · SOC2T2 | Claimed | Cloud API | developers.facebook.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
| Register | Offering, as the register names it | Status | Level | Valid until | Observed |
|---|---|---|---|---|---|
| Data Privacy Framework List (US) | EU-U.S. Data Privacy Framework · WhatsApp LLC | Active | non-HR data | 2027-01-23 | 2026-10-09 |
| Data Privacy Framework List (US) | Swiss-U.S. Data Privacy Framework · WhatsApp LLC | Active | non-HR data | 2027-01-23 | 2026-10-09 |
| Global LEI Index (GLEIF) | WHATSAPP LLC · WHATSAPP LLC | ISSUED | US-DE | 2027-08-01 | 2026-10-09 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
- Data Privacy Framework List (US): checked 2026-11-16, 2 entries under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under WhatsApp Business; WhatsApp Ireland Limited; WhatsApp LLC
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
| Product | Support period | State | SBOM | Source | Observed |
|---|---|---|---|---|---|
| — | Not declared | unknown | faq.whatsapp.com | 2026-10-19 |
Vulnerability reporting: facebook.com (security.txt, expires 2026-12-02; read 2026-11-02)
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 |
| dpa-de | Public | full | 200 | 2026-10-09 |
| lifecycle | Public | full | 200 | 2026-10-19 |
| residency | Public | full | 200 | 2026-10-09 |
| tia | Public | full | 200 | 2026-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.