Privacy Policy

gtasks-mcp — Google Tasks MCP Server

Effective date: 1 April 2025  •  Last updated: 1 April 2025

1. Overview

This Privacy Policy describes how gtasks-mcp ("the Application", "we", "our") collects, uses, and protects information when you authorise it to access your Google account data. The Application is privately operated and is not available to the general public.

By using this Application, you agree to the practices described in this policy.

2. Information We Access

The Application requests access to the following Google user data via the Google Tasks API:

No other Google account data (such as email, contacts, calendar, or Drive) is accessed or requested.

3. How We Use Your Data

Data accessed through the Google Tasks API is used exclusively to:

Your data is not used for advertising, analytics, profiling, training machine learning models, or any purpose other than the task management functions described above.

4. Data Storage and Retention

The Application stores the following data locally on the machine where it is self-hosted:

No Google Tasks content (task titles, descriptions, due dates, etc.) is persisted to disk by the Application. Task data is retrieved from Google's servers on demand and exists only transiently in memory during request processing.

OAuth tokens are retained until you revoke access via your Google Account permissions page or until the token file is manually deleted from the host machine.

5. Data Sharing and Disclosure

We do not sell, rent, trade, or share your Google user data with any third party, including:

Your data is never transmitted to any server other than Google's own API endpoints (tasks.googleapis.com). The Application acts as a local proxy between your AI assistant and the Google Tasks API; all network communication occurs directly between the host machine and Google.

6. Google API Services User Data Policy

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

7. Security

OAuth tokens are stored locally on the self-hosted machine and are never transmitted to any server operated by the Application's developer. Access to the host machine is the responsibility of the operator. We recommend restricting file system permissions on token.json to the user account running the server process.

8. Your Rights and Choices

You may at any time:

9. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be reflected by an updated "Last updated" date at the top of this page. Continued use of the Application after changes are posted constitutes your acceptance of the revised policy.

10. Contact

If you have any questions or concerns about this Privacy Policy or the Application's data practices, please contact the operator via the domain rsubr.in.