LegalGoogle Calendar data use

How Sigrix's Google Calendar Integration Uses Your Data

What Google Calendar data Sigrix's OAuth app can access, and why the marketplace never sees your calendar events or access token.

Last updated

  1. Scope

    This page explains how the Google Calendar integration available on Sigrix-listed AI agents and skills uses Google user data. It is separate from the Sigrix Marketplace Privacy Policy, which covers account, payment, and general marketplace-usage data.

  2. What Google Data Is Accessed

    Some Sigrix listings — for example the Google Calendar MCP server and the assistants built on it — connect to your Google Calendar through Google's OAuth sign-in. When you grant access, the integration can:

    • Read your calendar events, including searching and listing them
    • Check your free/busy availability
    • Create new calendar events on your behalf

    Sigrix does not request access to Gmail, Drive, Contacts, or any other Google product — only the Calendar access above.

  3. Sigrix Is Never in the Data Path

    The OAuth application's registered identity ("Sigrix") belongs to us — that's why Google shows our name on the consent screen, and why bundles can ship pre-configured without you creating your own Google Cloud project. But that identity is all we hold.

    The integration runs as a Google Calendar MCP server on your own machine. Sign-in and every Calendar API call — reading events, checking free/busy, creating events — go directly between your machine and Google. Sigrix's servers are never in that request path: we do not receive, transmit, process, or store your Google access token or any calendar data.

  4. Data Retention

    Because Sigrix's servers never receive your Google token or calendar data, Sigrix retains none. The access token Google issues after you sign in is cached only locally, on your own machine, by the MCP server you run — never on Sigrix infrastructure.

    You can review or revoke Sigrix's access at any time from your Google Account's third-party access settings . Revoking access there cancels the authorization immediately; removing the cached token file on your machine (or reinstalling the bundle) clears the local copy.

  5. Contact Us

    Questions about this integration or its data practices: privacy@sigrix.io.