Privacy Policy — TWW MCP Drive & Calendar

Last updated: 28 August 2026 (revised the same day to cover controlled creation and editing)

TWW MCP Drive & Calendar ("the Service") is a private internal tool operated by The White Willow ("we", "us"). It is not offered to the public. This policy explains exactly what Google user data the Service touches and what happens to it.

1. Whose data the Service accesses

The Service accesses data from only two pre-authorised Google accounts, both owned by the operator. The permitted accounts are fixed in server-side configuration and enforced in the Service's own code before any Google API call is made. There is no sign-up, and no other person's Google account can be connected to the Service.

2. What Google user data is accessed

Under these four OAuth scopes:

Scope	What it permits	Read/write
drive.readonly	Search and read files in the account's Google Drive, including file names, metadata (type, size, owner, modification date, links) and file contents	Read
drive.file	Create files and folders, and edit or delete only the files this Service itself created	Write, per-file
calendar.events	Read, create, reschedule, edit and cancel calendar events, including attendees and reminders	Read + write
calendar.calendarlist.readonly	Read the list of calendars the account owns or subscribes to	Read

Reading and writing are deliberately asymmetric. The Service can read the whole Drive but will only modify files it created itself. It holds per-file write access (drive.file) rather than the unrestricted drive scope, and it additionally stamps every file it creates with a private marker and refuses to modify anything unstamped — the refusal happens inside the Service, before any write is attempted.

Likewise, calendar.events covers events only. The Service does not hold the broader calendar scope, so it cannot administer calendar sharing or permissions, create or delete whole calendars, or change Calendar account settings.

Nothing in the Service can share a file, change permissions, or alter who can see anything, and there is no tool that deletes arbitrary Drive files.

3. Purpose

The sole purpose is private search, retrieval, document creation and schedule management on behalf of the account owner. Every action — read or write — happens only in direct response to a request the account owner makes. The Service performs no background scanning, no crawling, no indexing, and no scheduled or autonomous access. It never creates, edits or cancels anything on its own initiative.

Files the Service creates are placed in a dedicated TWW AI Workspace folder in the account's own Drive unless the account owner names another destination.

4. Whether content is stored

Google user content is not stored by us. File contents, calendar events and search results are retrieved on demand, returned in the response to the request that asked for them, and then discarded. The Service writes no copy of any Google user content to any disk, database, data warehouse, or log that we control.

Content the Service creates — documents, spreadsheets, folders and calendar events — is written into the account owner's own Google Drive and Google Calendar, where it belongs to them under their own Google account. We keep no separate copy.

What does exist, briefly:

• In-memory only, per running container: authenticated Google API client objects are reused for the life of a container instance. These hold credentials, not content.
• Operational logs: the hosting platform records standard HTTP request metadata (timestamp, path, status code). Request and response bodies are not logged. If a Google account that is not on the permitted list attempts to sign in to the Service, that rejected sign-in and its email address are written to the operational log so we can see attempted misuse.

5. How OAuth credentials are stored

The account owner authorises the Service once per account. Google returns a refresh token, which is stored in Google Secret Manager (Google Cloud project tww-mcp, region asia-south1), encrypted at rest by Google.

• The stored record contains only the refresh token, the token type, and the granted scope list. It contains no Google user content.
• Tokens are written once, by an operator running a provisioning utility under their own administrator credentials. The production service has read-only access to that secret (roles/secretmanager.secretAccessor) and cannot write, alter, or add to it.
• Access tokens derived from the refresh token are short-lived, held in memory only, and never written to storage.

6. Sharing with third parties, and AI processing

We do not sell, rent, publish, or trade Google user data, and we do not share it for advertising, profiling, or analytics purposes.

6.1 No use for AI/ML model development

Google Workspace API data obtained through this Service — Google Drive content and metadata, and Google Calendar content and metadata — is not used to develop, improve, or train generalized or non-personalized artificial intelligence or machine-learning models. This applies to us and to the processors listed below.

6.2 Transmission to the account holder's chosen AI assistant

This Service is a Model Context Protocol (MCP) server. It has no user interface of its own. It is operated through an AI assistant client chosen by the account holder.

When, and only when, the account holder issues a request, the Drive or Calendar content responsive to that request is transmitted to that assistant solely to fulfil that specific, user-requested feature — answering the question the account holder just asked. The data is not transmitted at any other time, is not sent anywhere else, and is not retained by this Service afterwards.

The assistant clients currently used with this Service are:

• OpenAI ChatGPT Business. Under OpenAI's current policy, business and workspace data is excluded from model training by default.
• Anthropic Claude (including Claude Code). On Claude consumer plans (Free, Pro, Max), Anthropic's model-improvement / data-training setting governs whether conversation content may be used to improve models. The account holder must ensure this preference is switched OFF before using this Service to retrieve Drive or Calendar data through Claude. This is an operating condition of the Service, not an optional recommendation.

We state this as the configuration we require and maintain. We do not make representations on behalf of OpenAI or Anthropic beyond their published policies, and account holders should confirm their own account settings.

6.3 Infrastructure processors

Google Cloud provides hosting (Cloud Run) and credential storage (Secret Manager) for the Service, and processes data solely to operate it. No other party receives Google user data.

7. Retention

Google user content: not retained. Credentials: retained until the account owner revokes access or we delete the stored secret. Operational logs: retained per Google Cloud Logging's default retention (30 days) and contain no Google user content.

8. How to revoke access

The account owner may revoke the Service's access at any time at myaccount.google.com/permissions by selecting TWW MCP DriveCal and choosing Remove access. Revocation takes effect immediately and the stored refresh token stops working. To have the stored credential deleted as well, email the contact below.

9. Limited Use compliance

The Service's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically:

• Google user data is used only to provide and improve the user-facing feature described in section 3 — private search, retrieval, document creation and schedule management requested by the account holder.
• Google user data is not transferred to others except as set out in section 6, and only to provide that feature, or as required by law.
• Google user data is not used for advertising, and is not sold.
• Google user data is not used to develop, improve, or train generalized or non-personalized AI or ML models, as stated in section 6.1.
• No human reads Google user data except with the account holder's explicit consent for a named purpose, to comply with applicable law, or as necessary for security (for example investigating abuse).

10. Security

Transport is HTTPS throughout. The Service endpoint requires OAuth authentication and accepts only an explicit allow-list of operator identities. Credentials are held in Google Secret Manager, and the production runtime identity has read-only access to them.

11. Contact

Abhishek Jain — abhishek@whitewillow.in
The White Willow

12. Changes

Material changes will be posted on this page with a revised "Last updated" date.