Privacy

Who is responsible

[Legal entity name], of [Registered address], operates book.select. For a guest's booking, the business that offered the page is the controller of that guest's data. We process it on the business's behalf. For an account on book.select, we are responsible for the account data. Contact [Contact email].

Guests who book

A booking collects the guest's name and email address. It may also collect a phone number, notes, answers to questions the business put on the form, the names and emails of extra guests, a time zone, and the place or video link for the meeting. If the guest cancels or reschedules, we store the reason they give. We use the IP address of the booking request to rate-limit the form and to block abuse. We do not sell guest data.

Account holders

An account stores the person's name, email, username, time zone, locale, and a hash of the password. If the person connects Google Calendar or Google Meet, we store that connection so bookings can be written to the calendar or given a meeting link. The connection is used only because the account holder turned it on. Payment settings are stored when the business enables Stripe.

Early access requests

The early access form collects an email address. It may also collect a name, a business name, and a message. We use them to reply about early access.

We email that request to ourselves. We do not store it in the app database. Plunk delivers the email and sends it through AWS SES, the email provider named under Companies that process data for us. We keep that mail for [Retention period].

Sign-in cookies

On HTTPS the sign-in cookies use the names below. On a site served over plain HTTP the __Secure- prefix is left off.

• __Secure-next-auth.session-token keeps an account holder signed in.
• __Secure-next-auth.csrf-token is the sign-in check against a forged request.
• __Secure-next-auth.callback-url stores the page to open after sign-in.
• __Secure-next-auth.pkce.code_verifier holds the sign-in proof for the code exchange.
• __Secure-next-auth.state holds the sign-in state until the provider returns.
• __Secure-next-auth.nonce holds the sign-in nonce until the provider returns.

Booking cookies

These are separate from sign-in.

The booking form can show a Cloudflare Turnstile check. This service does not set a Turnstile cookie. Cloudflare may set cookies on its own domain while the check runs.

• calcom.csrf_token protects actions such as cancelling a booking.
• uid marks a time slot a guest has selected, so another guest does not take the same slot while it is held. On HTTPS this cookie uses SameSite=None so a booking form embedded on another site can read it.

Account preference cookies

The browser sets these from the account pages. They do not use the __Secure- prefix.

• return-to remembers the page to open after an app is connected. It lasts one hour.
• calNewLocale stores the language an account holder just chose.
• calcom-timezone-dialog remembers that the time zone notice was dismissed.

Companies that process data for us

These companies handle data only to provide the part of the service named here:

• Cloudflare provides the CDN, the Turnstile check, and DNS and tunnel services.
• Plunk delivers email and sends it through AWS SES. Plunk tells us about bounces and complaints.
• Our hosting provider runs the servers in [Hosting region].
• Stripe processes card payments, and only when a business enables payments.
• Google Calendar and Google Meet are used only when an account holder connects them.

Why we use the data

We use booking data to make the booking, to send the messages the business configured, to take payment when the business enabled it, and to keep the form from being abused. We use account data to run the account and to keep it secure.

How long we keep it

Booking and account records are kept for [Retention period]. We delete or return them sooner when the business or the person asks, unless the law requires us to keep a record for a legal claim or a payment dispute.

Asking for a copy or for deletion

Email [Contact email]. A guest can also ask the business that took the booking. We will pass a guest's request to that business when the business is the controller. An account holder can ask us to delete the account at the same address.

Where the data is handled

The servers are in [Hosting region]. The companies listed above may handle data in their own regions. A guest's booking is made with the business they chose.

Changes

The date at the top of this page is the date of the current policy. We will note a material change on this page.

Contact

[Legal entity name], [Registered address], [Contact email].