Calendly
How to configure Calendly at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Unlock additional website features
Overview
This guide explains how to implement different privacy configurations for an embedded Calendly scheduler and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Calendly inline, pop-up and badge embeds on the website. Calendly LLC is a US company.
What the service does in this scope. Calendly shows its own cookie banner in embedded pages by default; it can be hidden with hide_gdpr_banner=1. Calendly uses cookies even if the banner is hidden, and recommends waiting to load Calendly until users accept performance cookies.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Link to the Calendly booking page (no embed on the website). |
| Configuration B — Higher risk | Inline or pop-up embed loaded after Consenter consent; Calendly banner hidden. |
Configuration A without website consent. A plain link sets nothing on your website; Calendly handles cookies on its own domain. No Consenter entry is required, but mention Calendly in the privacy policy.
Step 1 — Configure Calendly
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | — (external link) | Unlock additional website features |
| 2 | Integration | Website code | Link to calendly.com/... | Embed code with widget.js |
| 3 | Calendly cookie banner | hide_gdpr_banner=1 | — | Hidden (Consenter handles consent) |
| 4 | Loading | Consenter script blocking | — | After consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Calendly is a US enterprise subject to the US CLOUD Act; list the United States.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Entry needed | No | Yes |
| Processing purposes | — | Unlock additional website features |
| Tracking method | No tracking | Third party tracking (crosssession, cross-website) |
| Identifier | No identifier | Device identifiers |
| Data categories | — | Browsing and interaction data, Device characteristics, Device identifiers, IP address, User-provided data, direct identifier |
| Legal role of data recipient | — | Processor |
| Personalisation model | — | No personalisation |
| Maximum storage duration | — | Per Calendly cookie notice |
| Processing location | — | United States |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on