colasonic_bot

Privacy policy

Scope

This policy describes the private personal assistant colasonic_bot and this informational website. Last updated: 2 October 2026.

Google information accessed

Access depends on permissions previously granted and the requested task. It can include account identity, email and attachments, calendars, tasks, contacts, Drive files and document content, spreadsheets, presentations, forms and responses, chat information, Apps Script project information, Classroom information, and YouTube channel or video information. The application does not collect a Google password; Google handles sign-in and consent.

Purpose and actions

The assistant uses relevant information to answer requests, summarize or organize information, and perform authorized personal-assistant workflows. Existing permissions may allow changes as well as reading. Actions remain subject to the owner’s instructions; school-account Classroom access is read-only. colasonic_bot’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not sold, used for advertising, or used to determine creditworthiness, and is transferred to service providers only as needed to provide the owner-requested features described here.

Storage and retention

OAuth credentials are stored in the operator-controlled environment for authorized API access. Existing integrations use a credential store and local credential files. Relevant content, generated outputs and operational records may be retained in local files, conversation history, assistant memory and backups. Data is not necessarily erased when a task ends or access is revoked. There is no automatic fixed retention period covering all of these stores; deletion requires reviewing the relevant records and backup copies.

AI and other service providers

Relevant Google information may be included in prompts sent to third-party AI services to fulfill requests; processing is not entirely local. Depending on the selected route, these may include OpenAI, Google, Anthropic, or OpenRouter and its selected model provider. Relevant answers may also be delivered through the owner’s configured messaging or assistant interface. Provider processing and retention depend on the particular service and its terms. Information received from Google APIs is not used to develop, improve or train generalized artificial-intelligence or machine-learning models, and is sent only through AI service routes whose terms or settings exclude submitted data from such training. Provider retention and human access must remain compatible with the applicable Google data-use requirements; this policy does not promise zero retention.

Website hosting

Cloudflare hosts and delivers these informational pages and may process network and request metadata such as IP address, browser information and request time under its own policies. The pages contain no sign-in form, embedded assistant, advertising scripts or added analytics. Google account content and OAuth credentials are not part of the website files.

Controls and requests

You can revoke application access in your Google Account’s third-party connections settings. Revocation prevents future authorized access but does not automatically delete information already retained in files, conversations or backups. Intended users can contact the operator through their existing private channel or the support contact shown during OAuth consent to request a review or deletion. Other service providers may retain records under their own policies.

Changes

These disclosures should be updated when the application’s use of Google information or its processing arrangements change. Google API access remains subject to Google’s applicable API Services User Data Policy and additional restrictions for the scopes used.