Google Calendar integration

Last updated: August 20, 2026

Synk AI is a marketing agency and the software platform behind it. Our client portal at app.synkai.hu lets an agency user, a client and a candidate book meetings with each other. This page explains, in plain language, what happens when a user connects their Google Account to the portal, which permissions we request, what we never touch, and how to disconnect.

1. What the integration does

Connecting a Google Account is optional and is never required to use the portal. A user who books meetings connects their calendar so that three things work:

Free slots are real. When someone opens a booking link, the portal reads the start and end times of the existing events in the calendar of the host and offers only the slots that are genuinely free. Without this, a booking page would double book the host.
The booking lands in the calendar. When a slot is confirmed, the portal writes an event into the calendar of the host and invites the other party, so the meeting shows up on both sides with a video link.
The confirmation comes from a real person. The booking confirmation and the reminders are sent from the address of the host, so the recipient can simply reply to the person they are about to meet.

2. Which permissions we request and why

Google OAuth scope	Why the product needs it
Calendar events https://www.googleapis.com/auth/calendar.events	Reading the start and end times of existing events to compute free slots, and creating, updating or cancelling the event of a confirmed booking. We deliberately do not request the full https://www.googleapis.com/auth/calendar scope, because we never manage, create or share calendars.
Sending email https://www.googleapis.com/auth/gmail.send	Sending the booking confirmation and the reminders from the address of the user. This scope grants no read access of any kind. We request no Gmail read, modify or compose scope.
Email address https://www.googleapis.com/auth/userinfo.email	Showing which account is connected on the settings screen, so the user can verify the connection and notice if the wrong account was linked.

3. What we never access

We never read, search, modify or delete the email of the user.
We never read the content, the description or the attendee list of calendar events. Only start and end times are used, and only to compute free slots.
We never create, delete or share calendars, and we never change sharing settings.
We never sell Google user data, never use it for advertising, and never use it to train artificial intelligence or machine learning models.
We never pass Google user data to any third party. It is stored only in our own infrastructure, described below.

4. Where the data lives and how it is protected

The access and refresh tokens issued by Google are stored encrypted at rest in our database (Supabase, hosted in the European Union, AWS eu-west-3, Paris). All traffic is TLS encrypted. Database access is restricted by role based access control and row level security, so a user can only reach the integrations of their own organisation. Tokens are used only by the server side of the application; they are never exposed to the browser and never written into logs.

5. How to disconnect

A user can disconnect at any time in the portal, under the Calendar menu, on the Settings tab, using the Disconnect button. When that happens the stored tokens are deleted from our database immediately and the refresh token is revoked at Google. Access can also be revoked at any time from the Google Account itself, at myaccount.google.com/permissions. A deletion request can also be sent to info@synkaisolutions.com and is actioned within 30 days at the latest.

6. Limited Use

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