Calendly
Scheduling · calendly.com · last read 2026-11-16
At a glance
- Is Calendly GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Calendly itself publishes, each answer linked to its source and the date we read it.
- Does Calendly have a data processing agreement (DPA)?
- Yes. Calendly publishes a data processing agreement at calendly.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
- Which version of the Calendly DPA is current?
- On 2026-11-09, Calendly's DPA at calendly.com printed “Effective Date: June 1, 2026”. Source and date
- Does Calendly have a SOC 2 report?
- Calendly 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 Calendly ISO 27001 certified?
- Calendly 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 Calendly transfer personal data out of the EU?
- Calendly's agreement relies on the EU standard contractual clauses, the EU-U.S. Data Privacy Framework and the UK transfer addendum. Calendly LLC is on the official Data Privacy Framework List (status: Active). Source and date
- Who are Calendly's subprocessors?
- Calendly lists 20 third-party subprocessors; 20 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 Calendly?
- Calendly publishes a security.txt at calendly.com naming security@calendly.com. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Calendly |
|---|---|
| HQ | US |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | — |
| US CLOUD Act reach | Contracting entity incorporated in the US |
| Source | calendly.com · 2026-10-08 |
Data location
No data-location observation recorded yet.
The same question for every vendor: where SaaS vendors store EU data.
Calendly's subprocessor list names AWS and Google for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
20 third parties · 20 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| Aiven | US | Infrastructure |
| Amazon Web Services | US | Infrastructure |
| Assembled | US | User support management |
| Cloudflare | US | Content Delivery Network (CDN) and Distributed Denial of Service (DDoS) mitigation |
| Datadog | US | Infrastructure performance monitoring and business Analytics |
| E-HAWK | US, NL | Malicious actor detection and prevention |
| Elasticsearch | US | In-app search services |
| US | Infrastructure and analytics | |
| Hex | US | Product related data analysis and visualization |
| Hyperdoc (a.k.a. Recall.ai) | US | Processes audio/video recording for Calendly Notetaker |
| Intercom | US | Customer support enablement |
| Loris.ai | US | Customer support tool |
| Monte Carlo | US | Data quality observability |
| OpenAI | US | AI features, Notetaker meeting summaries, SMS compliance |
| Redis | US, IL | Manages in-memory data storage and caching services |
| Sprig | US | Customer feedback tool |
| Temporal Technologies | US | Supports background workflows to sync Gmail metadata for contact email threads |
| Twilio | US | SMS provider and domain-based message authentication, reporting and conformance |
| Upscope | US, GB | Interactive screen sharing for customer support assistance |
| Zendesk | US | Customer service communication tool |
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 · calendly.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | EU-U.S. DPF |
| Transfer mechanism | SCC module 1 |
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | UK Addendum |
| Notice of new subprocessors | 30 days in advance notice of intended changes to the Sub-Processor list (SCC Clause 9 Option 2) |
| Notice of new subprocessors | 30 days prior, via notification mechanism to customers who sign up; non-subscribers waive prior notice |
| If you object to one | Data exporter is given the opportunity to object to intended Sub-Processor changes |
| If you object to one | Object by email within 30 days on reasonable data protection concerns; parties work in good faith; if unresolved, customer may terminate affected portion of Services without penalty |
| Obligations passed to subprocessors | written agreement with each Sub-processor containing data protection obligations at least as restrictive as this DPA |
| Breach notification | without undue delay |
| Deletion when the service ends | Securely destroy Personal Data per Customer's Instructions on Customer's request or on termination of the account(s), unless retention is required by Applicable Laws |
| Getting your data back | Return Personal Data per Customer's Instructions on Customer's request or on termination of the account(s), unless retention is required by Applicable Laws |
| Requests from data subjects | Requests made directly to Calendly: advises the data subject to submit the request to the Controller customer and informs Customer if the data subject identifies Customer as Controller; provides Services functionality and reasonably assists where Customer cannot act on the request itself |
| Audit | Within 30 days of written request, no more than once annually: most recent third-party audit/certification reports (e.g. SOC 2, ISO 27001) to customer or mutually agreed third-party auditor; further information on written request as agreed in good faith |
| Processing on your instructions | only on behalf of and in accordance with Customer's Instructions (the Agreement, this DPA and Customer's use of the Services); Calendly informs Customer promptly if it believes an Instruction conflicts with Data Protection Laws |
| Confidentiality of staff | employees, contractors, agents and auditors with access to Personal Data are under a duty of confidentiality |
| Security measures | commercially reasonable technical and organizational measures, details set out at https://calendly.com/security |
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: Effective Date: June 1, 2026
at calendly.com
In effect from 2026-06-01
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 Calendly have a SOC 2 report?
Calendly 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 “Review documentation SOC 2 (Type 2)”
Source: calendly.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 Calendly ISO 27001 certified?
Calendly 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 “PCI COMPLIANT ISO/IEC 27001”
Source: calendly.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 |
|---|---|---|---|---|
| CSA STAR · CSA | Claimed | — | calendly.com | 2026-10-08 |
| ISO/IEC 27001 · ISO27001 | Claimed | — | calendly.com | 2026-10-08 |
| PCI COMPLIANT · PCIDSS | Claimed | — | calendly.com | 2026-10-08 |
| SOC 2 (Type 2) · SOC2T2 | Claimed | — | calendly.com | 2026-10-08 |
| SOC 3 · SOC3 | Claimed | — | calendly.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 · Calendly LLC | Active | non-HR data | 2027-10-06 | 2026-10-19 |
| Data Privacy Framework List (US) | Swiss-U.S. Data Privacy Framework · Calendly LLC | Active | non-HR data | 2027-10-06 | 2026-10-19 |
| Data Privacy Framework List (US) | UK Extension to the EU-U.S. DPF · Calendly LLC | Active | non-HR data | 2027-10-06 | 2026-10-19 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Calendly
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Calendly
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Calendly
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Calendly
- Data Privacy Framework List (US): checked 2026-11-16, 3 entries under Calendly
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Calendly
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Calendly
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Calendly
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Calendly
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Calendly
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: security@calendly.com (security.txt, expires 2027-04-10; 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 |
| subprocessors | Public | full | 200 | 2026-10-08 |
| tia | Public | full | 200 | 2026-10-20 |
History
| Detected | What moved | Why | Source |
|---|---|---|---|
| 2026-10-19 | Status Active - Re-certification under Review → Active | the vendor changed it | dataprivacyframework.gov |
| 2026-10-19 | Status Active - Re-certification under Review → Active | the vendor changed it | dataprivacyframework.gov |
| 2026-10-19 | Status Active - Re-certification under Review → Active | the vendor changed it | dataprivacyframework.gov |
Every reviewed change across the registry, newest first: vendor changes.