Privacy Policy
How Digitons Google Drive MCP V2 handles and protects your data
1. Overview & Service Identity
This Privacy Policy explains how Digitons Google Drive MCP V2 ("the Service"), developed and operated by Digitons Development, collects, processes, stores, and protects user data when connecting ChatGPT and OpenAI Agents to Google Drive.
2. Multi-User Architecture & Zero Shared Credentials
The Service is built on an isolated multi-user architecture:
- Each user connects their own personal or organizational Google account.
- There is no global Google service account, master user, or shared credential.
- User A cannot view, access, or modify files belonging to User B.
- MCP tool handlers never trust client-supplied user identifiers; all operations are bound cryptographically to the authenticated user identity.
3. Data Accessed & Handled
When you invoke Google Drive tools through ChatGPT, the Service accesses the following data strictly on an on-demand basis:
- Google Drive Files & Metadata: File names, IDs, MIME types, folder structures, and file contents requested explicitly during your ChatGPT conversation.
- Google Account Identity: Email address and profile display name retrieved from Google's userinfo endpoint to verify and display connection status.
- OAuth Authentication Tokens: Google OAuth 2.0 access and refresh tokens necessary to maintain authorized API communication.
We do not perform background harvesting, bulk indexing, or training of machine learning models on your Google Drive files.
4. Google Scopes Requested
The Service requests authorization for:
https://www.googleapis.com/auth/drive: Permits searching, reading, creating, and updating Google Drive files as instructed by you in ChatGPT.https://www.googleapis.com/auth/userinfo.email: Identifies the connected Google account for connection status reporting.https://www.googleapis.com/auth/userinfo.profile: Displays your account name on the connection confirmation page.
The Service's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Server Storage & Security Safeguards
We implement technical and organizational measures to safeguard your credentials and session state:
- File System Permissions: Persistent credential storage files (e.g.,
google-users.json) are stored outside web-accessible deployment directories and protected with strict POSIX file permissions (mode0600, readable and writable only by the process owner). Parent directories are restricted with mode0700. - Storage Classification: Data is protected via operating system access controls, filesystem permissions, and process isolation. Data files are not encrypted at rest.
- One-Time Link Tokens: Linking your Google account uses cryptographically random link tokens (
glink_...). Only a SHA-256 hash of the token is stored on the server. Tokens expire in 10 minutes (OAUTH_GOOGLE_LINK_EXPIRY_SECONDS=600) and are atomically deleted upon first use to prevent replay. - No Tokens in URLs: MCP Bearer access tokens are never placed into browser URLs, query parameters, HTML, or responses.
- Host Header Validation: Strict host verification enforces communication through
mcp-v2.digitonsdevelopment.com.
6. Audit Logging & Token Redaction
The Service records structured audit logs to ensure system reliability and investigate operational issues. Logs record timestamps, user subjects, tool action names, and status codes.
[REDACTED]) prior to logging.
7. Third-Party Services Used
The Service interfaces with:
- Google APIs: Google Drive, Docs, Sheets, and Slides APIs to execute requested operations.
- OpenAI / ChatGPT: Receives Model Context Protocol (MCP) requests initiated by the user.
8. Data Retention & Account Disconnection
Google tokens are retained only as long as you maintain your connection with the Service. You can disconnect and revoke access at any time:
- Via MCP: Issue a disconnect request in ChatGPT (executes
POST /auth/google/disconnect), which immediately revokes tokens with Google and permanently purges local records. - Via Google Account Settings: Revoke access directly under Google Third-Party Apps & Services.
9. Contact & Inquiries
For questions or requests concerning your privacy, please contact our team:
Email: support@digitonsdevelopment.com
Publisher: Digitons Development