Content-Security-Policy is the browser-level control that prevents unexpected third-party scripts, fonts, and styles from loading. A strict CSP is a force-function for keeping your booking page clean.
A starter CSP for booking pages
`default-src 'self'; script-src 'self'; style-src 'self'; font-src 'self'; connect-src 'self'; frame-ancestors 'none'; object-src 'none'; base-uri 'self';` — adapt for your tool's needs.
Why it matters for your booking page
CSP Headers for Booking Pages — the Privacy-Performance Combo is a micro-decision that compounds. A single tool choice or configuration setting can mean the difference between a booking page that respects clients and one that surveils them. Cal Clear is built so these decisions default to the privacy-respecting option.
Cal Clear's take
Cal Clear ships with the privacy-first defaults: zero third-party scripts on booking pages, freeBusy-only OAuth scope, configurable auto-delete, honeypot anti-spam, and SCCs + DPA for EU data. You don't need to fiddle with settings to get good privacy — it's the baseline.
This is part of our privacy-first scheduling pillar guide — 18 articles covering every privacy angle.
Frequently Asked Questions
Is this a Cal Clear-specific issue or an industry-wide one?
Industry-wide. Most scheduling tools default to broad third-party integration and permissive data practices because that's what enterprise buyers traditionally demanded. Privacy-first is a newer product posture.
How can I verify my current scheduling tool follows these practices?
Open the booking page in DevTools, audit the network requests, read the privacy policy end-to-end, and ask for a DPA. If any step surfaces red flags, evaluate alternatives.
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.