chris_bot

Data & privacy

Privacy policy

Effective October 28, 2026

This policy describes how chris_bot, a private personal integration operated by Chris Valleau, handles information obtained through Google APIs. It connects the owner’s Google accounts with Claude, Codex, and personal automation workflows. It is not offered as a public or commercial application.

1. Information accessed

Access depends on the Google OAuth permissions granted by the account owner. Authorized information may include:

The permissions granted through Google’s consent flow determine what the application can access. Describing a service here does not grant access to it.

2. How information is used

Google data is used to perform tasks initiated or configured by the owner, such as searching and summarizing information, organizing files and messages, editing documents and spreadsheets, managing events, and preparing or sending authorized communications.

chris_bot does not sell Google user data or use it for advertising or marketing.

3. AI and cloud processing

Workflows run on the owner’s computer and in cloud sessions. Relevant Google data may be sent to Anthropic for Claude processing, to OpenAI for Codex processing, and to infrastructure providers used to run those sessions. Depending on the task, this can include document or message contents, metadata, and generated results.

Processing and retention by these providers depend on the specific product, account terms, and data-control settings used for each session. The owner controls which workflows run and what information is submitted. This policy does not promise that every provider or session has zero retention.

4. Storage and security

OAuth tokens, task inputs, generated results, local files, caches, session histories, and logs may be stored in the local or cloud environments used by the integration. Tokens enable continued access until they expire or are revoked. Credentials must be kept separate from this public website and its source files.

Protection of information also depends on the access controls, credential storage, network connections, and security settings of those environments and providers.

5. Retention and deletion

Retention varies by workflow and provider. Files and results intentionally saved by the owner remain until deleted. Local caches, logs, and cloud session records follow the settings and retention practices of the relevant environment or service; there is no single fixed deletion period across all sessions.

The owner can delete stored application files and use each provider’s available controls to manage session records and request deletion. Questions or deletion requests can be sent to the contact address below. Revoking Google access does not automatically delete copies or outputs already stored elsewhere.

6. Sharing and Google Limited Use

Google data may be shared with the processing and infrastructure providers described above when needed for authorized tasks, or disclosed when required by law. It is not sold or shared for advertising.

chris_bot’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google API data must not be used to develop, improve, or train generalized AI or machine-learning models. AI services used for these workflows must be configured and governed by terms consistent with that restriction.

7. Your control

The account owner can review or revoke access at Google Account connections. Revoking permission stops access through the revoked authorization and may prevent dependent workflows from running. The public pages do not grant anyone access to the owner’s Google account.

8. Policy updates

Updates will be published here with a revised effective date when the integration or its data practices change.

9. Contact

Operator: Chris Valleau
Email: christopher.valleau@gmail.com