Embedded media
Is Calendly GDPR compliant?
Calendly may only run after the visitor has agreed. It is not strictly necessary for the website to work, so loading it on arrival, before any choice, is the single most common way sites get this wrong.
- Category
- Embedded media
- Needs consent
- Yes
- Leaves the EEA
- Yes
- Can be self-hosted
- No
- Recognised by
- calendly.com
- Typical cookies
- __cf_bm
What does Calendly do?
Embedded appointment booking. The widget loads from Calendly and processes the visitor's data before they have chosen anything, so load it behind consent or link out to the booking page instead.
Does Calendly need consent?
Yes. Calendly is Embedded media, which is never strictly necessary for a website to function. Under ePrivacy Article 5(3), and its national transpositions, storing or reading anything on the device for that purpose requires consent first, and that consent has to be as easy to refuse as it is to give.
ePrivacy Art. 5(3) · TDDDG § 25 (DE) · TKG 2021 § 165(3) (AT) · GDPR Art. 6(1)(a)
Does Calendly send data outside the EEA?
Yes. Calendly processes data outside the European Economic Area, so you need a transfer mechanism under Chapter V and you have to say so in your privacy policy. In practice this means standard contractual clauses, or a provider certified under the EU-US Data Privacy Framework.
How do we detect Calendly?
We load your page in a real browser as a first-time visitor who clicks nothing, then look at what it contacted. Calendly is recognised by requests to calendly.com, and we report whether it merely loaded or actually sent data, and whether it set a cookie before any choice was made.
Check your websiteThis describes the service as it is normally deployed. Your own configuration decides what actually happens, which is what a scan of your site shows. Not legal advice.