Effective September 25, 2026

Project Hub MCP privacy policy

Project Hub MCP is a personal, locally run desktop tool. This policy explains how its current pilot uses Google Drive and Google Sheets data. The public website is informational and does not perform Google sign-in.

Google permissions and data accessed

With your consent, Project Hub requests drive.readonly to read designated Google Drive authority documents and spreadsheets to read and write Google Sheets. Google’s Sheets scope is account-wide; it is not limited by Google to a single spreadsheet. The current code sends Sheets requests only to the fixed ProjectHub_Pilot spreadsheet and accepts only registered pilot project IDs. Drive reads in the current pilot address specific authority document IDs.

The pilot Sheet can contain project names, status, source links, session details, checkpoint summaries, and evidence URLs. The Drive documents can contain project authority and working guidance. The tool also reads a local Workspace routing policy for one registered project.

How data is used and shared

Project Hub uses this information to list registered projects, return current context and next actions with sources, register confirmed desktop sessions, record checkpoints, and flag conflicts between a saved next action and live authority. Checkpoint evidence URLs are supplied by the caller; the tool does not inspect their contents.

Project Hub returns selected results to the desktop client that invoked it, currently Codex or Claude Code. Those results may become part of that client’s conversation or records, subject to that client’s own settings and privacy terms. The MCP communicates directly with Google APIs for the requested operations. It does not send Google credentials to this website or to a chat connector.

Project Hub does not use Google user data for advertising or sell it to data brokers. Its use of information received from Google Workspace scopes follows the Google Workspace User Data and Developer Policy, including its Limited Use requirements.

Credential storage and security

Google authorization uses a Desktop OAuth client and a callback on your computer. The OAuth token is stored locally at %LOCALAPPDATA%\ProjectHubMCP\google-token.json, outside the Workspace folder. When Google refreshes an expired access token, the file is updated. The OAuth client JSON is kept outside Workspace. The public pages do not collect the token or receive the OAuth callback.

Project Hub uses local locking to coordinate its own writers. Other writers to the same Sheet can still race an append, so the tool does not promise conflict-free remote writes.

Retention and deletion

The tool reads its designated Drive documents when context is requested; it does not create a separate saved copy of those documents. Sessions, checkpoints, and conflict records written to the pilot Sheet remain in that Google Sheet until they are manually removed. The current pilot has no automatic deletion schedule for those records.

The local token file remains until it is deleted, replaced by a later authorization, or rendered unusable by revocation or expiry. Revoking Google access stops future authorized API calls, but does not delete already written Sheet rows or information already returned to a desktop client. Manage any such client records using that client’s controls.

Your choices and revocation

You can remove Project Hub’s Google access from your Google Account’s third-party connections. You can also delete the local token file from your computer and remove pilot Sheet records you no longer want. Reauthorizing Project Hub would grant access again.

For questions or deletion help, email [email protected].

This website

These pages provide information about the desktop tool. They do not ask you to enter a Google password or connect a Google account. The website host may process ordinary request data, such as IP address and browser information, to deliver the pages.