What we hold, and what you can take back.

Written to be read, not to be survived. It says exactly what is stored, why it is stored, and how you get all of it back or delete it.

This page describes what CalendarBook stores, why it stores it, and how you get it back or remove it. It is written to be read, not to be survived.

What we hold about you

When you sign in with Google we receive and store your Google account id, your email address, your name and your profile picture URL. We never receive your Google password.

What your organization holds

Everything you enter — calendars, services, opening hours, customers and bookings — belongs to the organization it was entered in and lives in that organization's own isolated database. It is not pooled with any other organization's records.

Google Calendar

Connecting a Google Calendar is optional. When you connect one, CalendarBook asks Google for four permissions — to see the list of your calendars (calendar.calendarlist.readonly), to create calendars of its own (calendar.app.created), to view and edit events (calendar.events) and to see when you are busy (calendar.freebusy) — and stores the token Google gives us, so bookings keep syncing after you close the browser. With that access CalendarBook:

  • lists the account's calendars, so you can choose which one belongs to each doctor, room or table;
  • creates a new calendar in the account when you ask it to, for example one per room;
  • creates, updates and deletes the events for bookings made in CalendarBook;
  • reads your busy periods, so slots that clash with your other appointments close automatically;
  • reads the events in the calendars you linked, for the dates you are looking at, to show them on the calendar and schedule pages.

Events read from Google are shown to members of your organization and are not stored. What we do store is the token, the account's email address and name, the ids of the calendars you linked, and the start and end times of busy periods. All of it stays in your organization's own database. Google Calendar data is never sold, never used for advertising, never used to train AI models, and never shared outside your organization unless the law requires it. Disconnecting the account here revokes the token at Google and deletes it, along with the stored busy periods. You can also remove access at any time from your Google account's permissions page.

CalendarBook's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

No AI training. CalendarBook does not use, retain or transfer user data obtained through Google Workspace APIs — including Google Calendar data — to develop, improve or train generalized or non-personalized artificial intelligence (AI) and/or machine learning (ML) models. CalendarBook has no AI or ML features, and calendar data is never sent to any AI model or AI provider. This follows the Google Workspace API User Data and Developer Policy.

Cookies

Two cookies, both strictly necessary: one holds your session, one remembers which organization you were last looking at. There is no advertising or analytics tracking on this site.

Getting your data out

An owner can download the whole organization as a JSON file at any time, from Settings → Backup & danger zone. Google tokens are deliberately excluded from that export.

Deletion

Closing an organization schedules it for permanent deletion after 30 days. Until that date it can be restored; after it, the organization's database is destroyed and cannot be recovered.

To delete your own account, see how to delete your account.

Contact

Questions about any of this: use the contact page.