Privacy Policy — OpenCode Google Workspace
Last updated: 10 November 2026
Purpose and operator
This connector is operated by Sean Keagan for personal use. It allows the operator to ask OpenCode to perform authorised Google Workspace tasks. This website provides information only and does not offer public account registration.
Google data accessed and used
Depending on a task and the permissions granted, the connector may access account identity, Drive files and their contents, documents, spreadsheets, presentations, forms and responses, email and attachments, calendars and events, contacts, tasks, Chat data and Apps Script projects. Data is used to carry out the operator's requests, including reading, creating, editing, organising and sharing items or sending messages when instructed.
Processing and sharing
The MCP server runs on the operator's computer and communicates with Google's APIs. Content retrieved through the connector may be passed to OpenCode and its configured AI model provider to understand and fulfil a request. That provider's processing, retention and training terms depend on the account and service in use; this page does not promise that all processing stays on the computer. OpenCode session history, downloaded files and logs may also contain retrieved data. The operator does not sell Google account data or provide it to advertisers through this connector. Requested actions such as sharing a document or sending email disclose the chosen content to the intended recipients.
Credentials and retention
OAuth client credentials and account tokens are stored locally on the operator's computer. They are not published on this website. Tokens are retained while the connection is used. Session history, logs, downloaded files and model-provider records follow their respective settings and retention policies. Removing local connector data does not delete the original files held in Google Workspace.
Control, revocation and deletion
The operator can revoke this app's access through Google Account > Security > Connections to third-party apps and services at https://myaccount.google.com/connections. Revocation stops future authorised API access but does not automatically remove previously downloaded content, session history, or provider records. Those must be removed through the relevant local application or provider controls.
Contact
For questions about this personal integration, use the support email shown on its Google authorisation screen.
Changes
This page may be updated when the integration's configuration or data handling changes.