bookameet.ingSign in

Draft for the owner’s review. No lawyer has read this yet.

Privacy policy

Last updated November 19, 2026

Contents

  1. In short
  2. If you have an account
  3. If you book a time
  4. What each Google permission is for
  5. Google user data
  6. Where data is kept, and who handles it
  7. Cookies
  8. How long we keep it
  9. Disconnecting and deleting
  10. Changes and contact

bookameet.ing (bookameet.ing) is run by BookAMeeting. It gives people free booking links on their Google Calendar. This policy says what we collect, why, where it’s kept and how to remove it. “We” means BookAMeeting. Questions go to hello@bookameet.ing.

In short

  • We collect what it takes to run your booking links and the bookings made with them, and nothing for advertising.
  • We don’t sell data, show ads, or use Google data to train AI models.
  • Your calendar tells us when you’re busy, not what your meetings are.
  • The times you’re open are public: anyone with your link, and any program, can see them. They show when you’re free, never what you’re doing the rest of the time.
  • Calendar tokens are stored encrypted. You can disconnect a calendar or delete your account at any time.
Contents

If you have an account

When you sign in with Google and use bookameet.ing, we store:

  • your Google account’s ID, email address and name, and the time zone your browser reports when you first sign in;
  • what you set up: your link’s name, your meeting types (titles, descriptions, lengths, questions, reminders), your working hours and your one-off links;
  • your calendar connections, as the next sections describe;
  • the bookings made with you, with what your invitees gave (see below) and a record of each change to a booking;
  • the API keys you create, with their names and when they were last used. We keep only a hash of each key, never the key itself.

An API key lets software you authorise act for you: read your open times, make one-off links, and read your bookings, including your invitees’ names, email addresses and answers. Revoke a key and it stops working.

If you join the waitlist while sign-up is by invitation, we store your email address and when you joined, and use it only to tell you when sign-up opens. It isn’t tied to an account: deleting one doesn’t remove it, so ask us to.

Contents

If you book a time

You don’t need an account to book. When you book, we store your name, email address and time zone, your guests’ email addresses, your answers to the host’s questions, the time you booked, whether you booked on the page, through the API or through the MCP server, and your reason if you cancel and give one.

The host sees these details, and so does any software the host authorises with an API key. We email you a confirmation with a link to reschedule or cancel, a reminder before the meeting if the host has one set, and a note if the meeting moves or is cancelled.

We also put the booking on the host’s Google Calendar as an event: its title names you and the host, you and your guests are its attendees, and its description holds your answers to the host’s questions and the link to manage the booking. Google then sends an invitation to you and to each guest, with the host’s calendar as the organiser. So your guests see your answers and the manage link too, and anyone with that link, guests included, can reschedule or cancel the booking.

To have your details removed from our database, write to hello@bookameet.ing; we’ll remove them by hand. That doesn’t reach the copies outside it: the event on the host’s calendar, the invitations in your guests’ calendars, and emails already sent.

If the host deletes their account, their bookings are deleted from our database with your details, and upcoming meetings are cancelled and their events deleted. Events for meetings already past stay on the host’s Google Calendar with your name, email address and answers; we can’t remove those.

Contents

What each Google permission is for

Signing in asks Google only for the first three permissions below. The three calendar permissions are asked for separately, when you choose “Connect calendar”. A calendar connects only if you grant all three: if Google’s screen comes back with any of them unticked, the connection is refused and nothing from it is stored.

Who you are at Google openid

Tells us which Google account is signing in. We store that account’s unique ID and use it only to recognise you when you sign in again. We never match accounts by email address.

Your email address email

We store your Google account’s email address to send you booking emails and to show you which account you’re signed in with. Emails we send your invitees give it as the reply-to address, so their replies reach you. When you connect a calendar, we also store that Google account’s address, to tell your connected accounts apart. When new bookings go on that account’s main calendar, the invitations Google sends for them show this address to your invitees and their guests as the organiser; when they go on another calendar you own, Google names that calendar as the organiser instead.

Your name profile

We store your name and show it on your booking pages, in emails and in the calendar events we create for your bookings. We don’t store anything else from your Google profile.

The list of your calendars https://www.googleapis.com/auth/calendar.calendarlist.readonly

Lets us see which calendars are in your Google account. We store each calendar’s name, ID and time zone, whether it’s your main calendar and whether you own it, so you can choose which calendars to check for conflicts and which one new bookings go on. This permission shows us nothing inside your calendars.

When you’re busy https://www.googleapis.com/auth/calendar.events.freebusy

Lets us see when you’re busy on the calendars we check, so we offer only times you’re free. When you connect, every calendar you own is checked and the others aren’t; you can then turn any of them on or off. From each event we use only its start and end, whether it’s cancelled, whether it’s marked busy or free, and your own reply to it (a declined event doesn’t count). We store only the start, the end and Google’s ID for the event. We don’t store titles, descriptions, attendees or locations.

Google tells us when one of these calendars changes, so your open times stay current, and just before a booking is confirmed we ask Google again whether that time is still free.

Your open times are public. The times we work out from your working hours and these busy times are shown to anyone who has your booking link, written as plain text on every booking page, and served without any sign-in by our HTTP API and MCP server to any program or AI assistant that asks. They show when you’re free; they never show why you’re busy.

Events for your bookings https://www.googleapis.com/auth/calendar.events.owned

Lets us create, change and delete events on calendars you own. We use it only for bookings made through your links. When someone books, we create the event on the calendar you chose, with the meeting’s title, your invitee’s name, your invitee and their guests as attendees, their answers to your questions, a link to manage the booking and a Google Meet link, and Google sends the invitations. We move the event when the booking is rescheduled and delete it when it’s cancelled. bookameet.ing never changes or deletes any other event.

Contents

Google user data

bookameet.ing’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

That means we use data from Google only to provide the features this policy describes, and in particular:

  • we don’t use it for advertising, and don’t sell it;
  • we don’t pass it to anyone except as this policy describes (your open times, which are public; what software you authorise with an API key reads; the events and invitations Google sends; and the companies under “Where data is kept”), or as the law requires;
  • no person reads it unless you ask us to (to help with a problem), or it’s needed for security or by law;
  • we don’t use it to train AI or machine-learning models.
Contents

Where data is kept, and who handles it

Three companies handle data for us, each only to do its part:

  • Railway, our hosting provider, runs bookameet.ing and its database, where everything above is stored. When something fails, the app writes the error to its server log there; an error can name a calendar by its Google ID, which for a main calendar is its owner’s email address. Railway’s own request logs may record visitors’ IP addresses. Backups of the database are Railway’s. Railway keeps its logs and backups according to its own retention, so data we delete can remain in a backup until that backup expires.
  • Resend sends our emails, so it handles each email’s recipient and content.
  • Google holds your calendar and the events we create, makes the Meet links and sends the invitations, under your own Google account.

Google calendar tokens are encrypted (AES-256-GCM) before they’re stored, with a key kept apart from the database. Sign-in sessions and API keys are stored only as SHA-256 hashes. We don’t store IP addresses in our database.

Beyond what this policy describes (your open times, which are public; what hosts and the software they authorise see of their bookings; the invitations Google sends; and these three companies), we share data with no one, unless the law requires it.

Contents

Cookies

bookameet.ing sets three cookies, all needed to sign you in, and none for analytics, advertising or tracking:

  • a session cookie that keeps you signed in, for up to 30 days or until you sign out;
  • a cookie that checks a sign-in started in your browser, for 10 minutes;
  • a cookie holding your browser’s time zone, set each time you sign in and read only on your first, for 10 minutes.

Booking a time sets no cookie.

Contents

How long we keep it

  • Your account and what you set up: until you delete your account.
  • Busy times: from up to about a month back to about a year ahead, refreshed as your calendar changes. Past ones are dropped each time we read a calendar afresh, every 30 days. All of a calendar’s are removed when you stop checking it or disconnect it.
  • Bookings, with their invitees’ details: as long as the host’s account exists.
  • A sign-in session stops working after 30 days, or when you sign out.
  • Waitlist addresses: until you ask us to remove yours. Deleting an account doesn’t remove one.
  • Logs and backups at Railway: according to Railway’s own retention.
Contents

Disconnecting and deleting

Disconnecting a calendar account deletes its tokens, its list of calendars and its busy times from our database, and stops Google’s change notifications. If it held the calendar new bookings go on, your links stop taking bookings until you choose another. It doesn’t withdraw the permission at Google: to do that too, remove bookameet.ing at myaccount.google.com/connections.

Deleting your account first stops your links taking bookings, then cancels your upcoming bookings (their events are deleted from your calendar and each invitee is emailed), stops watching your calendars, and then deletes from our database your account, sessions, API keys, meeting types, working hours, one-off links, calendar connections with their tokens, busy times, and every booking made with you, with its invitees’ details. Events for past meetings stay on your Google Calendar: they’re yours.

Deleting your account doesn’t withdraw the permission in your Google account either: remove bookameet.ing at myaccount.google.com/connections. It doesn’t remove a waitlist address; ask us at hello@bookameet.ing. Deleted data can remain in Railway’s backups until they expire.

You can do either while signed in, or by writing to hello@bookameet.ing from the address you sign in with.

Contents

Changes and contact

bookameet.ing isn’t meant for children under 13, and we don’t knowingly collect their data.

If we change this policy, we’ll update this page and its date. If a change affects how we use your Google data, we’ll email you before it takes effect.

BookAMeeting, hello@bookameet.ing

Contents

bookameet.ing: free booking links, for people and their AI assistants.

PrivacyTerms