Privacy notice
Effective October 17, 2026
Workspace Connect is an independent, open-source local setup tool maintained by Zohaib Arsalan. It connects Google Drive and Google Docs to MCP-compatible coding agents, including Codex and Claude Code, using the third-party workspace-mcp server.
What the connector accesses
You supply your own Google OAuth client and choose a Google account on Google’s consent screen. The enabled Drive and Docs scopes can permit searching and reading files, creating and editing documents, changing file metadata, and managing sharing or deletion through the tools exposed by the upstream server. Your Google account’s existing access permissions still apply. Review the requested permissions before granting access.
How Google data is used
Google data is used to carry out the work you request through your coding agent. The local connector forwards MCP requests to the upstream server, which communicates with Google’s APIs. Workspace Connect has no hosted service that collects your Google files, no telemetry collector, and no advertising service. The maintainer does not receive your OAuth credentials or document content through this project.
Workspace Connect’s use and transfer of information received from Google APIs will follow the Google API Services User Data Policy, including its Limited Use requirements. The connector does not sell Google data, use it for advertising, or operate a service to train general-purpose AI models on it.
Your coding agent and AI provider
Document contents and tool results returned to Codex, Claude Code, or another agent may be processed, retained, or transmitted by that agent and its AI provider under your selected account settings and their separate terms. Workspace Connect does not control those providers. Read the provider’s data policies before using sensitive documents, and configure the agent’s approval and data controls appropriately.
Local storage and retention
The default configuration directory is
~/.config/workspace-connect, unless you choose another
directory. OAuth client credentials and access/refresh tokens are stored
there by the connector and upstream server. The credential importer
creates private directories and restricts the imported client file to
owner-only access on systems supporting POSIX permissions. These are
local files, not a promise of encrypted storage.
Your coding agents may retain their own conversation history, tool results, files, and logs. Google retains documents and related data under your Google account. Those copies follow the respective application’s retention controls.
Disconnecting and deleting data
You can revoke this app’s access from your Google Account connections, remove the MCP registration from your coding agents, and delete the chosen local credential directory. Revoking access does not delete Google documents, agent history, backups, or copies already retained by an AI provider. Manage those separately in the relevant service. Do not post credentials or private document content in GitHub issues.
This public website
This is a static GitHub Pages website. It has no Google sign-in form, does not request access to your account, and does not receive Google documents. It uses no analytics, tracking scripts, advertising, or project-managed cookies. GitHub may process technical request information under the GitHub Privacy Statement. This site uses system fonts and does not load third-party font services.
Contact and updates
For project or privacy questions, use the repository issue tracker without including private data. Changes to this notice will be published here with an updated effective date and retained in the repository’s history.