Privacy

Cookieless Scheduling Pages: Why and How

October 2026 · 6 min read · By

A cookieless booking page is a privacy-first booking page that sets no first-party cookies, ships no third-party cookies, and functions correctly regardless of whether the invitee has cookies disabled entirely. It's the baseline for any tool claiming to be privacy-first.

What cookies typically show up on booking pages

Inventory a typical scheduling tool's booking page in DevTools, and you'll usually find: Google Analytics cookies (_ga, _gid), the tool's own session cookie, a consent-management cookie, sometimes a Mixpanel or Segment ID cookie. That's 4-6 cookies on what should be a single-purpose form.

Why cookieless is the right default

Cookies are trackable across sessions, domains (with third-party cookies), and sometimes devices. The EU ePrivacy Directive requires consent for any non-essential cookie. A booking page that's cookieless avoids the consent-banner dance entirely.

What functionality needs cookies (and how to replace it)

Cart state: not relevant for scheduling — each booking is a fresh transaction.

User preferences: timezone detection is the main one. Use the browser's Intl.DateTimeFormat API instead — no cookie required.

Anti-spam: Session IDs for rate-limiting can be tied to IP + fingerprint instead of cookies, or skipped if you rely on reCAPTCHA v3.

CSRF tokens: SameSite-first-party tokens can be delivered via header instead of cookie for the booking endpoint.

Cal Clear's booking page and cookies

Cal Clear's own booking-page code sets no cookies. Timezone is detected via JS API and rate-limiting is IP-based. The one exception is Google reCAPTCHA spam protection — on by default, and it can be turned off per link — which sets Google's own cookie.

This is part of our privacy-first scheduling pillar guide — 18 articles covering every privacy angle.

Frequently Asked Questions

Will my booking page work in browsers with cookies disabled?

Cal Clear's own booking-page code doesn't rely on cookies. If reCAPTCHA is on for the link (the default), Google's reCAPTCHA script uses its own cookie.

Do I still need a cookie banner on a cookieless page?

No. The ePrivacy Directive consent requirement applies to non-essential cookies. If you set none, there's nothing to ask consent for.

Try privacy-first scheduling, free

Cal Clear runs no analytics or ad trackers on booking pages and auto-deletes booking data on your schedule. Start at calclear.app.