Aircall
Telephony · aircall.io · last read 2026-11-16
At a glance
- Is Aircall GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Aircall itself publishes, each answer linked to its source and the date we read it.
- Does Aircall have a data processing agreement (DPA)?
- Yes. Aircall publishes a data processing agreement at aircall.io. It gives 10 days' notice before a new subprocessor is added. It commits to telling you of a personal data breach within 24 hours. Source and date
- Which version of the Aircall DPA is current?
- On 2026-11-09, Aircall's DPA at aircall.io printed “This Data Processing Agreement was last updated on January 15, 2025.”. Source and date
- Does Aircall have a SOC 2 report?
- Aircall 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. Source and date
- Is Aircall ISO 27001 certified?
- Aircall's page mentions ISO/IEC 27001 for its security programme; it does not say there that Aircall holds a certificate. In Aircall's words: “Our security program is aligned with ISO 27001 and SOC II standards.” We read this on 2026-10-08. Source and date
- How does Aircall transfer personal data out of the EU?
- Aircall's agreement relies on the EU standard contractual clauses, the EU-U.S. Data Privacy Framework and the UK transfer addendum. Aircall.io, Inc. is on the official Data Privacy Framework List (status: Active). Source and date
- Does Aircall offer EU data residency?
- The EU is the default region for this vendor. Source and date
- Who are Aircall's subprocessors?
- Aircall lists 24 third-party subprocessors; 22 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 Aircall?
- Aircall publishes a security.txt at aircall.io naming no contact. The file falls short of RFC 9116: no Contact field; no Expires field. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
No identity observation recorded yet.
Aircall data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | EU by default | — | aircall.io | 2026-10-08 |
EU: New accounts are automatically assigned a US, EU, or Australia hosting location based on the phone number/country code used at signup; the customer doesn't choose it, and no plan or cost is named. It only covers call recordings, voicemails, transcriptions and AI Assist insights. Account, billing, analytics and support data stay in the US regardless of region.
The same question for every vendor: where SaaS vendors store EU data.
Aircall'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
24 third parties · 6 of the vendor's own group companies · 22 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| Amazon Web Services | US, DE, AU | Hosting of all data in Aircall product. |
| AssemblyAI, Inc. | US | Generation of transcription from call recordings |
| Atlassian | US | Customer Support: ticketing, chatbot systems for assistance |
| Cartesia AI, Inc. | US | Provision of inputs for AI Voice Agent |
| ClickHouse | US | Data analytics and data processing services. |
| Datadog | US | Monitoring for provided services/security purposes. |
| Deepgram, Inc. | US | Generation of transcription from call recordings |
| Eleven Labs Inc. | US | Provision of inputs for AI Voice Agent |
| Intercom | US | Customer Support: ticketing, chatbot systems for assistance |
| Looker | DE | Data visualization and sync |
| Looker Data Sciences, Inc. | DE | — |
| Microsoft Corporation | US | Generation of conversation insights (Call summarisation, Key topics list, Talk ratio etc.) from voice transcriptions; Provision of inputs for AI Voice Agent |
| PartnerHero | US, RO | Customer Support: support agents |
| Pinecone | US, IE | Storage and retrieval of vector embeddings to support AI-powered search and the customer knowledge base. |
| Pusher | US, GB | Data visualization and sync |
| Pusher Ltd | US, GB | — |
| Ribbon | US | Call authentication/verification, call security and call-routing control. |
| Rudderstack | US | Data visualization and sync |
| RudderStack Inc. | US | — |
| SideGuide Technologies, Inc. | US | Retrieval and processing of customer provided source data to support customer created knowledge base within the Aircall product. |
| Startree | US | Real time call data tracking (data visualization and sync) |
| Startree, Inc. | US | — |
| Twilio | US | Voice transmission services. |
| Zendesk | US, IE | Customer Support: ticketing, chatbot systems for assistance |
Aircall's own group companies listed as subprocessors (6)
| Company | Country | Purpose |
|---|---|---|
| Aircall PTY LTD | AU | Processing activities within the provision of Aircall's product and services |
| Aircall SAS | FR | Processing activities within the provision of Aircall's product and services |
| Aircall Telecom India Private Limited | IN | Processing activities within the provision of Aircall's product and services |
| Aircall Telecom SL | ES | Processing activities within the provision of Aircall's product and services |
| Aircall UK Ltd | GB | Processing activities within the provision of Aircall's product and services |
| Aircall.io, Inc. | US | Processing activities within the provision of Aircall's product and 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 · aircall.io
| Term | What the agreement says |
|---|---|
| Transfer mechanism | EU-U.S. DPF |
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | SCC module 3 |
| Transfer mechanism | UK Addendum |
| Transfer mechanism | other |
| Notice of new subprocessors | 10 business days prior notice of sub-processor changes (SCC Clause 9 Option 2) |
| Notice of new subprocessors | Email to the Admin User Email Address of intended changes; no advance notice period stated |
| If you object to one | May reasonably object in writing within 10 business days of notice; otherwise deemed to agree; if customer objects, parties negotiate a mutually satisfactory solution |
| Obligations passed to subprocessors | contract imposing on the Subprocessor the same obligations as those imposed on Aircall under this DPA |
| Breach notification | promptly after detection; no later than 24 hours after detection where European Data Protection Law applies; by email to Admin User Email Address |
| Deletion when the service ends | After the export period ends, Aircall deletes all Personal Data it holds only for the Customer, including copies, unless applicable law requires it to be kept |
| Getting your data back | Customer may export the Personal Data, at its expense and within the Service's capabilities, during the 30 days after the Agreement terminates |
| Requests from data subjects | assists Customer, insofar as possible, in responding to data subject rights requests (access, rectification, erasure, objection, restriction, portability, automated decisions) |
| Audit | Audit by customer or approved independent third-party auditor, only if granted by applicable law and on proven reasonable grounds, a regulator request, or a direct legal right; at most once per 12 months; at least 30 days' notice; each party bears its own costs |
| Processing on your instructions | only on Customer's documented instructions, including for transfers |
| Confidentiality of staff | persons authorized to process have committed to confidentiality or are under a statutory obligation of confidentiality; access limited to personnel who need it |
| Security measures | appropriate technical and organizational measures listed in Exhibit B |
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: This Data Processing Agreement was last updated on January 15, 2025.
at aircall.io
Last updated 2025-01-15
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 Aircall have a SOC 2 report?
Aircall 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 “Aircall is SOC2 Type 2 compliant”
Source: aircall.io, 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 Aircall ISO 27001 certified?
Aircall's page mentions ISO/IEC 27001 for its security programme; it does not say there that Aircall holds a certificate. We read this on 2026-10-08.
- Mention “Our security program is aligned with ISO 27001 and SOC II standards”
Source: aircall.io, 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 |
|---|---|---|---|---|
| CSA CAIQ Level 1 · CAIQ | Claimed | A compilation of +250 common security questions. | aircall.io | 2026-10-08 |
| GDPR | Claimed | — | aircall.io | 2026-10-08 |
| ISO 27001 · ISO27001 | Claimed | information security program is aligned with ISO 27001 (alignment stated, not certification) | aircall.io | 2026-10-08 |
| SOC II | Claimed | information security program is aligned with SOC II standards (alignment stated, not attestation) | aircall.io | 2026-10-08 |
| SOC2 Type 2 · SOC2T2 | Claimed | — | aircall.io | 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 · Aircall.io, Inc. | Active | HR data, non-HR data | 2027-01-29 | 2026-10-09 |
| Data Privacy Framework List (US) | Swiss-U.S. Data Privacy Framework · Aircall.io, Inc. | Active | HR data, non-HR data | 2027-01-29 | 2026-10-09 |
| Data Privacy Framework List (US) | UK Extension to the EU-U.S. DPF · Aircall.io, Inc. | Active | HR data, non-HR data | 2027-01-29 | 2026-10-09 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Aircall
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Aircall
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Aircall
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Aircall
- Data Privacy Framework List (US): checked 2026-11-16, 3 entries under Aircall
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Aircall
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Aircall
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Aircall
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Aircall
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Aircall
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 |
|---|---|---|---|---|---|
| Aircall desktop app | — | Not declared | unknown | support.aircall.io | 2026-10-19 |
| Aircall iOS app | — | Not declared | unknown | support.aircall.io | 2026-10-19 |
Vulnerability reporting: (security.txt, no Contact field; no Expires field; 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 |
| lifecycle | Public | full | 200 | 2026-10-19 |
| residency | Public | full | 200 | 2026-10-08 |
| subprocessors | Public | full | 200 | 2026-10-08 |
| 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.