Calendly is the market leader for booking links — and that means its free tier is the scheduling page most widely seen by potential clients. Here's an honest, DevTools-verified breakdown of what happens when someone visits a Calendly booking page in 2026.
The scripts that load
Google Analytics (GA4). Mixpanel. The Calendly first-party analytics script. A CSRF token cookie. Two Calendly session cookies. An A/B test cookie. A behavioral-analytics script for click heatmaps. Total: ~15 requests to 5-6 domains before the booking form even renders.
What gets shared with Google
Every page view, referrer, time on page, click event, form-field interaction, and device fingerprint. Associated with a persistent GA cookie that follows the invitee across the broader Google ecosystem.
What gets shared with Mixpanel
Same event-level data, stored separately by Mixpanel. Mixpanel's data-residency is primarily US; EU invitees' data crosses the Atlantic.
What Calendly reads from your calendar
On the scheduler side, Calendly requests broader calendar scopes than strictly necessary — in most configurations, it has access to event titles and descriptions, not just free/busy. Cal Clear uses freeBusy-only scope by design.
What's actually necessary for a booking
An email collector. A time slot picker. A confirmation flow. No analytics, no behavioral tracking, no A/B frameworks are required to schedule a meeting. Tools like Cal Clear demonstrate that a booking page can serve its purpose at less than 50KB and zero third-party requests.
This is part of our privacy-first scheduling pillar guide — 18 articles covering every privacy angle.
Frequently Asked Questions
Does Calendly sell my data?
Calendly's privacy policy reserves the right to share data with partners for analytics and advertising. Whether that constitutes 'selling' under CCPA is a legal debate, but the practical effect is that Calendly booking data enters the ad-tech ecosystem in ways that Cal Clear's does not.
Can I block Calendly's trackers with a content blocker?
Client-side, yes. But server-side processing (logs, API events) still occurs. If you need genuine privacy, you need a tool that doesn't run this processing server-side either.
Try privacy-first scheduling, free
Cal Clear runs zero trackers on booking pages and auto-deletes booking data on your schedule. Start at calclear.app.