How we keep your data safe

This page lists the security measures that run on Book Your Calendar today. Each one is checked against our code and settings, and we update the page when they change.

Last updated

Security at a glance

What protects your account, your bookings and your clients’ payments.

Sign-in

Clerk runs sign-in, with breached-password checks and bot protection on sign-up.

Encryption

HTTPS for every page. Microsoft Outlook, Zoom and Razorpay connection tokens are encrypted before we save them.

Rate limits

Limits on our API, and stricter ones on password and email checks.

Payments

Card details go to the payment provider, such as Razorpay. We never see or store card numbers.

On every request

  • HTTPS only, with HSTS for one year
  • Sign-in checked before any account page or private API
  • Rate limits on API requests
  • A request ID on every response, for tracing
  • Requests larger than 10 MB refused

What we never store

  • Your password (Clerk holds it; we only pass it on to check it)
  • Card numbers or card security codes
  • Google Calendar sign-in tokens (they stay with Clerk)
  • Microsoft Outlook, Zoom and Razorpay tokens in plain text

Security measures in detail

How each part works, in plain terms.

Sign-in and passwords

Accounts are run by Clerk on our own sign-in domain, clerk.bookyourcalendar.com.

What this covers

Passwords need at least 8 characters, and Clerk refuses passwords found in known data breaches
Bot protection on sign-up (Cloudflare Turnstile, through Clerk)
Disposable email addresses and email sub-addresses are blocked at sign-up
Accounts are locked after repeated failed attempts

Changing your password or email

Changes in Settings go through one server-side service that checks it is you.

What this covers

Your current password is checked first
Limited attempts, then a short wait
A new email is confirmed with a code sent to that address
After a password change, your other devices are signed out (on by default)
Passwords are never stored, logged or shown back to you by us

Encrypted connection tokens

When you connect Microsoft Outlook, Zoom or Razorpay, we encrypt the access and refresh tokens before saving them.

What this covers

AES-256-GCM encryption with a key held outside the database
If encryption fails, the token is not saved at all
Google Calendar access goes through your Clerk sign-in; we do not store Google tokens
Phone numbers in our WhatsApp delivery log are encrypted

Secure connections

Every page and API call is served over HTTPS.

What this covers

HSTS for one year, including subdomains, with the preload directive
Pages cannot be framed by other sites (clickjacking protection)
Camera, microphone and location access turned off for our pages

Rate limits

Request counts are kept in Upstash Redis, in Mumbai, next to our servers.

What this covers

Separate limits for sign-in, payments, subscriptions and public pages
Limited requests get a 429 answer with a Retry-After time

Request protection

Checks that stop other sites, or altered links, acting for you.

What this covers

Forms and actions that change payments, bookings or settings carry a CSRF token that the server checks
Reschedule and cancel links in booking emails are signed with a server-side secret, so they cannot be guessed or edited
Signatures are compared in constant time

Webhook signature checks

Messages from our providers are accepted only with a valid signature.

What this covers

Razorpay payment and subscription webhooks: HMAC SHA-256 signature
Clerk account webhooks: Svix signature
A webhook without a valid signature is refused

Payments

Clients pay on the payment provider’s own page, such as Razorpay Checkout.

What this covers

Card details go straight to the payment provider, never to our servers
Our database has no fields for card numbers
Razorpay holds PCI DSS certification; it is Razorpay’s, not ours
Payment confirmations are verified with the provider’s signature

Privacy and your data

Where your data lives and the rules we follow.

India’s DPDP Act

We handle personal data under India’s Digital Personal Data Protection Act, 2023. Our privacy policy explains what we collect, why, and how to reach our grievance officer.

Read the privacy policy

Data location

Your booking data is stored in Mumbai, India. The app runs on Vercel with its servers in Mumbai, and the database is MongoDB Atlas on AWS in Mumbai.

See our sub-processors

Google user data

We use Google Calendar data only for the scheduling features you turn on, as the Limited Use section of our privacy policy describes.

Read the Limited Use section

Browser extension

The Book Your Calendar extension asks only for storage and clipboard write access. It talks only to bookyourcalendar.com, and runs on one site: Gmail, to add the booking link button.

Extension privacy details

Encryption and access

Who and what can reach your data.

Encryption

  • HTTPS for all traffic between your browser and our servers
  • Microsoft Outlook, Zoom and Razorpay tokens encrypted with AES-256-GCM before saving
  • Database connections over TLS (MongoDB Atlas requires it)
  • Data at rest encrypted by MongoDB Atlas

Access control

  • Account pages and private APIs need a signed-in session
  • Admin APIs are limited to named platform admins
  • Database audits use least-privilege access
  • Password and email changes are recorded in an account security log

How a request is checked

The steps a request to Book Your Calendar passes through.

1. Rate limit and size

Too many requests, or a body over 10 MB, are refused before any work is done.

2. Session

Account pages and private APIs check your Clerk session. Without one, you are sent to sign in.

3. Route checks

Routes check that the record belongs to you or your team, and check CSRF tokens and signatures where they apply.

Before a page or API runs

  • Rate limits by route type
  • Request size limit (10 MB)
  • Sign-in check for private areas
  • A request ID on every response

Logs and tracing

  • Request IDs to trace a problem end to end
  • The password check never logs or repeats your password
  • Account security events recorded with the time and outcome
  • Server timing shows durations only, never personal data

Records and checks

What we keep track of, so we can investigate a problem.

Request IDs

Every response carries a request ID, so a reported problem can be traced.

Account security log

Password changes, email changes and wrong current-password attempts are recorded.

Admin access

Admin APIs are limited to named platform admins, and every API call is rate limited.

Least-privilege audits

Database checks run with access limited to what the check needs.

Report a security issue

If you find a security problem, email us with the steps to reproduce it. Please do not access other people’s data or disrupt the service while testing.

Send security reports to support@bookyourcalendar.com. Our contact details are also in security.txt.

How we handle personal data under India's DPDP Act: DPDP Act page.