My MCP Server — Privacy Policy
Last updated: October 26, 2026
This Privacy Policy describes how My MCP Server, a personal automation application operated by De-Mono, accesses, uses, stores, shares, retains, and deletes data obtained through Google APIs. It applies to My MCP Server’s Google OAuth integration, including its Google Sheets and Google Drive functions.
1. Application operator and contact
My MCP Server is a privately operated application for the Google account owner’s personal workflows. For privacy, access, and deletion requests, contact dead0brother@gmail.com. Homepage: https://demono.ru/my-mcp-server/.
2. Google data the application can access
Depending on the permissions the account owner grants and the features they enable, My MCP Server can access:
- Google Sheets: spreadsheet titles, sheet names, cell contents, and associated metadata, including personal lists, birthdays, reminders, nutrition records, and fitness records when they are stored in authorized spreadsheets.
- Google Drive: names, identifiers, metadata, folder structure, and contents of files or folders within the permissions granted by the user.
- OAuth authorization data: access or refresh tokens and technical account identifiers necessary to maintain the authorized connection.
- Operational information: requested operations, their outcomes, timestamps, and diagnostic records needed for operation and troubleshooting. Such records may contain identifiers or excerpts of user-requested content.
The precise Google permissions are shown on the Google OAuth consent screen. My MCP Server’s access is limited to permissions granted by the user and operations supported by the enabled integration. Granting access is voluntary.
3. How Google user data is used
My MCP Server uses Google user data only to provide the functions requested or configured by the authorized account owner:
- Read and display authorized spreadsheet records and Drive files.
- Create, edit, or organize authorized spreadsheet data, files, or folders when requested and permitted.
- Produce owner-requested summaries, reminders, and personal workflow results using authorized data.
- Return results to the connected MCP client or assistant selected by the owner.
- Maintain the authorized Google API connection, security controls, and necessary error diagnostics.
My MCP Server does not use Google user data for advertising, unrelated marketing, sale, data brokerage, or third-party surveillance. My MCP Server does not use Google Workspace API data to develop, improve, or train generalized artificial intelligence or machine-learning models.
4. Sharing and external services
My MCP Server communicates with Google APIs to perform authorized actions. When the owner invokes My MCP Server through an external MCP client or AI assistant (for example, ChatGPT), the data needed to fulfill that request may be sent to that client or assistant and processed under the provider’s privacy terms and account settings. The owner should review those terms before using such an integration with sensitive information.
The operator does not sell Google user data or share it with advertisers. Other disclosures are limited to the owner’s explicit direction, service providers technically necessary for the requested operation, security or legal obligations, or other circumstances permitted by applicable Google API policies. The application does not independently publish the owner’s private Google content.
5. Storage and security
OAuth credentials, configuration, diagnostic records, and information retrieved for active workflows may be stored on computing infrastructure controlled by the application owner. Data from Google APIs is transmitted using HTTPS. Access to private application functionality and stored credentials is intended to be limited to authorized operators and services. No online service can guarantee absolute security.
Copies of data may also exist in a connected MCP client or assistant after the owner requests a result. Those copies are governed by the receiving service’s own data retention and deletion controls.
6. Retention and deletion
Locally stored Google user data, credentials, and operational records are retained while needed for the owner’s configured workflows, troubleshooting, or lawful operational requirements, and until the owner deletes them or requests their deletion. Revoking access prevents new authorized API requests but does not automatically remove copies already stored by My MCP Server or external clients.
To request removal of Google data or OAuth credentials stored by My MCP Server, contact dead0brother@gmail.com. After verifying that the requester controls the relevant integration, the operator will remove the requested information from application-controlled active storage, subject to legal requirements and any technically necessary backup retention. Data sent to an external client must be managed through that service’s own controls.
7. Google access and permissions
Users can review or revoke My MCP Server’s Google Account permissions at https://myaccount.google.com/connections. After revocation, features depending on Google authorization may stop working until permission is granted again.
8. Limited Use and policy changes
My MCP Server’s use and transfer of information received from Google APIs is intended to follow the Google API Services User Data Policy, including its Limited Use requirements where applicable. The application limits Google user data use to the purposes described in this Policy and to user-authorized functionality.
If the application changes how Google user data is used, this Policy will be updated. Where required, affected users will be notified and asked for appropriate consent before new uses occur. The revision date at the top identifies the most recent update.
9. Contact
For questions about My MCP Server’s privacy practices or data deletion, contact dead0brother@gmail.com.