Security

What CalFlare does to keep a public booking link safe

This page lists the controls that exist in the product today. It is written to be checked, not admired. If something you need is not here, assume we do not have it and ask.

The public booking page

  • Booking confirmations sit behind a Cloudflare Turnstile bot check.
  • Bookings, slot lookups and the public assistant are rate-limited per address.
  • There are overall request ceilings and request-size limits on top of the per-address limits.
  • Double-booking is prevented on the server: the slot is re-checked at confirmation, and confirmations for one host are handled one at a time.

Accounts and sessions

  • Passwords are hashed with bcrypt. They are never stored as text.
  • Access tokens are short-lived and signed with RS256.
  • Sign-in and sign-up are rate-limited per address.

Calendar connections

  • Google and Microsoft calendars are connected with OAuth, through the provider's own sign-in.
  • The connect flow is protected with a signed state value, so the provider's response is tied to the account that started it.
  • Calendar access is used for two things: reading busy times and events, and creating the events people book.

Manage links

  • Each booking's manage link contains a 64-character random token.
  • It gives access to one booking: view, reschedule or cancel.

Webhooks

  • Endpoints must be HTTPS.
  • Targets are validated against internal and private addresses, which protects against server-side request forgery.
  • Each delivery is signed with HMAC-SHA256 so the receiver can check it came from CalFlare.
  • The secret is shown once and can be rotated. Endpoints that keep failing are switched off.

Email

  • All text typed by users, such as names, notes and answers, is HTML-escaped before it goes into an email.
  • Each email shows the time in the reader's own time zone, which avoids a class of honest mistakes.

The API and the data

  • A strict CORS allow-list decides which origins may call the API.
  • Security headers are set: HSTS, nosniff, and no framing of the API.
  • Data is stored in PostgreSQL on AWS.

The AI assistant

  • It can only offer and book times that pass the same server-side checks as the booking form.
  • Usage is capped per day, and the public assistant is rate-limited per address.
One booking, end to end

Where the checks sit

The path of a booking
Invitee opens your linkSlot lookups are rate-limited
Picks a time, fills the formRequest-size limits apply
ConfirmsCloudflare Turnstile bot check
Server re-checks the slotAgainst your calendar, one confirmation at a time
Event createdOn your primary calendar, through OAuth
Emails sentUser text HTML-escaped
Manage link issued64-character random token
Webhook deliveredHTTPS only, signed with HMAC-SHA256

What we do not claim

CalFlare does not hold security or compliance certifications today. We do not claim SOC 2, ISO 27001 or HIPAA compliance, and we do not describe the product as certified under any privacy regulation. If your organisation requires one of these from a scheduling tool, CalFlare is not yet the right choice.

There is also no single sign-on (SAML) yet.

Your part

  • Treat a webhook secret like a password. Store it outside your code, and rotate it if it may have leaked.
  • Verify the signature on every webhook before acting on it. The webhooks article has code for this.
  • Ask only for what you need in intake questions. Answers are sent to you by email.
  • Disconnect a calendar you no longer use.

Reporting a problem

If you believe you have found a security problem in CalFlare, write to contact@calflare.com with the steps to reproduce it. Please give us a chance to fix it before sharing it publicly.

For what data is held and why, see the privacy policy.

Share one link. Let people pick a time.

Connect a calendar, set your hours, and send your booking link. CalFlare is free to get started.