Google Calendar · Outlook

Calendar integration

How Tide Seek uses your calendar

Contents

  1. How the connection works
  2. Permissions we request
  3. What we do not access
  4. What we store
  5. Limited Use of Google data
  6. How to revoke

Tide Seek is a B2B commercial operations platform. An AI assistant talks to the customer and books the meeting with the responsible sales rep. For it to offer times that actually exist, that rep’s calendar must be connected.

This page describes exactly what we ask for, what we do, and what we do not do with that access. The formal processing description is in the Privacy Policy, section 4.

01

How the connection works

  1. The company admin creates the sales rep’s calendar in the platform and receives a single-use link.
  2. The link goes to the sales rep, who opens it and signs in on their own Google or Microsoft account.
  3. The sales rep grants access on the provider’s consent screen. Only the account owner can consent — the admin never sees the rep’s credentials or tokens.
  4. From then on, the assistant offers free slots from that calendar and books meetings on it.

The link is single-use and expires in 7 days.

02

Permissions we request, and why exactly these

PermissionWhat it is for
.../auth/calendar.freebusy Query only busy/free intervals, so we offer real availability to the customer.
.../auth/calendar.events Create the booked meeting event and remove it when the meeting is cancelled.
openid, email Show in admin which account was connected.

We do not request the auth/calendar scope, which would grant broad access to the calendar and its settings. We ask for the minimum needed for the feature.

03

What we do not access

We do not read the content of your events. Availability uses the freeBusy endpoint, which returns only start and end times of busy periods. Titles, descriptions, attendees, attachments and locations of existing events are not accessed, not stored, and not sent to language models. The only events whose content we know are the ones the platform itself creates.

04

What we store

05

Limited Use of Google data

Our application’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: we use the data only to offer and manage meeting scheduling; we do not transfer it to third parties except as needed to provide the feature, comply with law, or in a corporate transaction; we do not use it for advertising, ad profiling, resale, or training AI models; and we do not allow humans to read it except with specific consent, for security, to comply with law, or when aggregated and anonymized.

06

How to revoke

Anytime at myaccount.google.com/permissions or by removing the calendar in the platform admin. Revocation immediately stops availability queries and creation of new events. Meetings already created remain on your calendar — they are your appointments, and deleting them without your request would alter your agenda.

The same treatment applies to Microsoft Graph (Outlook / Microsoft 365), with equivalent scopes.

Privacy questions