Scope and operator
This policy describes the maintainer's personal, owner-only deployment of ChatGPT Colab Plugin, whose Google OAuth application name is colab-compute-mcp. KaiQin04 operates that deployment for their own use. It is not a public hosted notebook service. Other people who deploy the open-source template operate separate installations and must provide information about their own data practices.
Google data and permissions
The application requests openid, https://www.googleapis.com/auth/userinfo.email, and https://www.googleapis.com/auth/colaboratory. It uses Google identity information to bind the authorization to the owner and uses the Colab permission to inspect compute availability, manage authorized runtimes, execute requested notebook code, and transfer requested inputs and results.
The base OAuth flow does not request Google Drive or cloud-platform permission. Notebook code may separately contact other services or request additional authorization; those actions are distinct from the base OAuth connection.
Storage and processing
The private backend stores the owner's platform identifier, Google account identifier, a masked email address, and an encrypted refresh token. Access tokens are obtained from Google as needed. The backend also stores notebook documents, code, execution records, outputs, and artifact metadata in its database, and saved artifact files in object storage. Code and inputs submitted for execution are processed in the owner's Google Colab runtime.
The deployment uses ChatGPT Sites and its underlying database and object-storage services. When the owner accesses the application through ChatGPT, their chosen client can receive requested tool results, notebook outputs, and download links. Google, OpenAI, and infrastructure providers process data according to their applicable terms and privacy policies. This application policy does not override those providers' practices.
Retention and controls
Notebook records and saved outputs remain until removed by the owner or the deployment operator. Ordinary artifacts have a configured 30-day retention period, while pinned artifacts remain until unpinned or deleted. Expiration and physical deletion are separate: maintenance availability can delay removal from storage. Provider logs and backups may follow separate retention schedules.
The owner can revoke the application's Google access through their Google Account connections settings. Revocation prevents future authorized Google access but does not by itself delete records already saved in the private backend, stop a running Colab runtime, or remove copies downloaded or shared elsewhere. Backend records and runtimes must be managed separately. The stored refresh grant can be replaced through a new authorization or removed by the operator from the deployment's storage.
Security and contact
The application uses HTTPS for supported network connections and encrypts stored refresh tokens. It intentionally avoids returning credential values in normal tool responses. No system can guarantee uninterrupted availability or protection against every incident.
The operator and sole user of this deployment are the same person. General questions about the open-source project can be raised through the repository's issue tracker. Do not include personal data, credentials, notebook contents, or private deployment details in public issues. Users of other installations should contact their own operator.