Privacy Policy

Last updated: 13 November 2026.

This policy describes how CLab Context Bridge uses Google user data to coordinate private software development work across multiple projects.

Data accessed

With the Google account owner's authorization, the bridge accesses Google Drive file contents and metadata, such as file names, identifiers, folder locations and modification information. The intended documents are project contexts, task instructions, technical status files and reports. The bridge also uses OAuth access and refresh tokens to authenticate authorized API requests.

How data is used

Google Drive data is used to retrieve project instructions, coordinate approved tasks, maintain project context, and create, update and verify technical reports. The bridge is not intended to collect customer records or unrelated personal files, and is not designed for advertising or data brokerage.

Storage and retention

Project files are stored in the operator's Google Drive. Files needed for development work may also be retained in the operator-controlled Lab environment as working copies, technical checkpoints and reports. OAuth credentials are retained in the authorized client configuration for API access. Project records are retained as needed for project continuity and review; the operator can remove records that are no longer needed.

Sharing and processing

Project information is made available to the authorized operator and development agents for the tasks the operator approves. Relevant project material may be processed using OpenAI ChatGPT or Codex to perform those tasks and prepare technical reports. The bridge does not provide public access to project documents. Separate service providers operate under their own applicable terms and privacy policies.

The bridge does not sell Google user data or use it for targeted advertising. Its intended use of Google API data is limited to the project coordination functions described here.

Security

Access to the bridge is restricted to authorized project workflows. Google API access uses OAuth credentials. Credentials and private project documents must not be published on this website.

Revoking access and deleting data

The Google account owner can revoke the application's authorization from Google Account connections. Revoking access stops further authorized API access; it does not automatically delete existing files or local copies.

For access, correction or deletion of stored project information, or to request removal of retained copies and credentials, contact the operator using the support email displayed on the application's Google OAuth consent screen.

This informational website

These pages do not contain a login form, analytics scripts, tracking cookies or an interface for accessing Google Drive. The web server may retain ordinary access and security logs.

Policy updates

Changes to the bridge's data practices will be reflected in this policy. Google API use is subject to the Google API Services User Data Policy.