Connected services, explained plainly.

Identity and email

Google identity and email are used to identify the connected account and show the authorized user which account is connected. They are not used for advertising or sold.

Calendar features

The app can list calendars so the user can choose which calendars to enable. For enabled calendars, it can view events and create, update, or delete events as part of user-directed scheduling and synchronization.

Drive features

The app can browse file and folder metadata without broadly reading file contents. It can link selected folders and attachment references, and upload app-initiated files or work with files the user explicitly makes available to the app.

User control, security, and retention

Only an authorized user can start a connection from the app’s authenticated integration settings. OAuth tokens are stored encrypted at rest.

Disconnecting attempts token revocation and deletes stored OAuth credentials. Operational metadata may remain after disconnect until the user removes it in the app or requests deletion. Disconnecting does not delete files that already exist in Google Drive.

Support, access, correction, and deletion requests can be made through thecontact form.

Google scopes requested

• openid — basic sign-in identity.
• email — the connected account’s email address.
• https://www.googleapis.com/auth/calendar.readonly — list calendars and their metadata.
• https://www.googleapis.com/auth/calendar.events — view and manage events on enabled calendars.
• https://www.googleapis.com/auth/drive.metadata.readonly — browse file and folder metadata.
• https://www.googleapis.com/auth/drive.file — work with app-created or user-selected files.

Limited Use

The use of information received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

Read theGoogle API Services User Data Policyand theGoogle Workspace User Data and Developer Policy.