Google Calendar sync

Connect Google Calendar and your two calendars stay in step: bookings taken on Slot’d appear in Google, and time you’re already busy in Google stops clients booking over it.

Connecting is optional and off by default. Slot’d has no access to your calendar until you connect it yourself, and none after you disconnect.

What it does

Slot’d → Google. When a client books, reschedules or cancels, the matching event is created, moved or removed on your Google Calendar. You see your work in the calendar you already live in.

Google → Slot’d. Events already on your Google Calendar mark you busy, so those times stop being offered to clients. This is what prevents a client booking you during something Slot’d doesn’t know about — a dentist appointment, another job, a school run.

Connecting

Settings → Calendar sync → Connect Google Calendar. Google asks you to sign in and approve the access described below; approving returns you to Slot’d with sync live. The Calendar page also has a Google Calendar shortcut straight to these settings.

Exactly what Slot’d asks for

Two permissions, and no others:

Permission	Why Slot’d needs it
`https://www.googleapis.com/auth/calendar.events`	Create, update and delete the events for your Slot’d bookings, and read the timing of your existing events so those hours can be marked busy.
`https://www.googleapis.com/auth/userinfo.email`	Read the email address of the Google account you connected, so Slot’d can show you which account is linked and connect the right one if you have several.

What Slot’d does not ask for. There is no request for Gmail, Drive, Contacts, or anything outside Calendar. Slot’d cannot read your mail or your files, because it never asks for permission to.

What Slot’d reads, and what it stores

Slot’d reads when your existing events start and end — the busy-time picture — and writes events for your own bookings.

It does not store the contents of your personal calendar. Titles, guests, notes and locations of events Slot’d did not create are used to work out busy time and are not kept. What is stored is the connection itself and the link between a Slot’d appointment and the Google event it created, so that a later reschedule or cancellation updates the right one.

Your calendar data is never sold, never used for advertising, and never shared with other providers or clients.

Disconnecting

Settings → Calendar sync → Disconnect. This revokes Slot’d’s access with Google immediately and deletes the stored connection. You can also revoke it from your Google Account permissions page — either way works, and either way Slot’d stops having access at once.

Events Slot’d already wrote to your calendar stay where they are; disconnecting stops future sync rather than erasing your history. Delete any you don’t want, in Google Calendar, as normal.

If sync stops working

Reconnect first — Settings → Calendar sync → Disconnect, then Connect again. That resolves nearly everything, because it mints a fresh token.

Sync covers the calendar of the account you connected. If you keep work in a second Google account, connect the one your working calendar actually lives in.

Limited Use

Slot’d’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.