Vonage
Communications API · vonage.com · last read 2026-11-09
At a glance
- Is Vonage GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Vonage itself publishes, each answer linked to its source and the date we read it.
- Does Vonage have a data processing agreement (DPA)?
- Yes. Vonage publishes a data processing agreement at vonage.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
- Does Vonage have a SOC 2 report?
- Vonage states SOC 2 Type 2 on its own page, but does not say there how to get a report. In Vonage's words: “Note: SOC 2 Type II covers the following services: Network Registry API, Verify API, SIM Swap API, Number Verification API, Identity Insights API, and Vonage QoD API.” We read this on 2026-11-09. Source and date
- Is Vonage ISO 27001 certified?
- Vonage states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-11-09. Source and date
- How does Vonage transfer personal data out of the EU?
- Vonage's agreement relies on the EU standard contractual clauses, the EU-U.S. Data Privacy Framework and the UK transfer addendum. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Vonage Business Inc. |
|---|---|
| HQ | US |
| Parent company | Telefonaktiebolaget LM Ericsson |
| Ultimate ownership | SE |
| EU contracting entity | Vonage B.V. |
| LEI | 98450057EFE9D01O5335 |
| US CLOUD Act reach | Contracting entity incorporated in the US |
| Source | vonage.com · 2026-11-09 |
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.
Subprocessor chain
Processing terms
From the vendor's data processing agreement · read 2026-11-09 · vonage.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | EU-U.S. DPF |
| Transfer mechanism | SCC module 1 |
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | SCC module 3 |
| Transfer mechanism | SCC module 4 |
| Transfer mechanism | UK Addendum |
| Notice of new subprocessors | at least 30 calendar days where commercially feasible, solely by email to customers subscribed via the Notification Mechanism form |
| If you object to one | Written objection within 10 calendar days of notice if it reasonably demonstrates a material risk of non-compliance; good-faith negotiation; if no resolution within 10 days, either party may terminate only the affected part of the Services |
| Breach notification | without undue delay (to the extent permitted by applicable law) |
| Audit | On written request, once per year (more often after a confirmed Security Incident or regulatory request), Vonage makes available reasonable information showing compliance; at Customer's expense unless the audit finds material non-compliance |
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
We found no version number or date in the agreement as we read it.
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 Vonage have a SOC 2 report?
Vonage states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-11-09.
- Claimed “Note: SOC 2 Type II covers the following services: Network Registry API, Verify API, SIM Swap API, Number Verification API, Identity Insights API, and Vonage QoD API.”
Source: developer.vonage.com, 2026-11-09
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 Vonage ISO 27001 certified?
Vonage states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-11-09.
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 |
|---|---|---|---|---|
| CSA Star · CSA | Claimed | Listed for Core API (SMS/Voice) and Vonage Network APIs (VNA). | developer.vonage.com | 2026-11-09 |
| HIPAA | Claimed | Obtained for Core API (SMS/Voice) & VNA (Network APIs), Video API, Vonage AI Media Analyzer (Formerly ASR), and Vonage AI Studio. | developer.vonage.com | 2026-11-09 |
| ISO 27001 · ISO27001 | Claimed | Obtained for Core API (SMS/Voice) & VNA (Network APIs), Vonage AI Media Analyzer (Formerly ASR), and Vonage AI Studio; Pending for Video API. | developer.vonage.com | 2026-11-09 |
| PCI DSS · PCIDSS | Claimed | Service Provider Certification for Vonage AI Media Analyzer (Formerly ASR); Pending for Video API and Vonage AI Studio; Not Required for Core API (SMS/Voice) & VNA. | developer.vonage.com | 2026-11-09 |
| SOC 2 Type II · SOC2T2 | Claimed | Obtained for Core API (SMS/Voice) & VNA (Network APIs), Video API, and Vonage AI Media Analyzer (Formerly ASR); Pending for Vonage AI Studio. For VNA, covers Network Registry API, Verify API, SIM Swap API, Number Verification API, Identity Insights API, and Vonage QoD API. | developer.vonage.com | 2026-11-09 |
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 |
|---|---|---|---|---|---|
| Global LEI Index (GLEIF) | Vonage B.V. · Vonage B.V. | ISSUED | NL | 2027-04-08 | 2026-11-09 |
| Global LEI Index (GLEIF) | VONAGE BUSINESS INC. · VONAGE BUSINESS INC. | ISSUED | US-DE | 2027-06-04 | 2026-11-09 |
- ACN qualified cloud (Italy): checked 2026-11-09, no entry under Vonage; Vonage B.V.; Vonage Business Inc.
- DORA critical ICT third-party providers (ESAs): checked 2026-11-09, no entry under Vonage; Vonage B.V.; Vonage Business Inc.
- ENS certificates of conformity (CCN, Spain): checked 2026-11-09, no entry under Vonage; Vonage B.V.; Vonage Business Inc.
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-09, no entry under Vonage; Vonage B.V.; Vonage Business Inc.
- FedRAMP Marketplace (US): checked 2026-11-09, no entry under Vonage; Vonage B.V.; Vonage Business Inc.
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-09, no entry under Vonage; Vonage B.V.; Vonage Business Inc.
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.
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: the well-known path returns an HTML page, not a security.txt (read 2026-11-09)
How other vendors publish theirs: security.txt across the registry.
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-11-09 |
| dpa | Public | full | 200 | 2026-11-09 |
History
Nothing has moved since we started watching this vendor on 2026-11-09. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.