Privacy Policy
1. Operator and scope
Cosmic Assistant is operated by Artyom Fartygin. For privacy questions, contact temik0112@gmail.com.
This policy describes the public informational website and the private assistant integration used by the operator to access the operator's connected Google accounts.
The integration is intended for the operator's personal use. It is not offered as a public service, and the assistant is not used by other people.
2. Google data accessed
Depending on the permissions granted and the task requested, the integration may access:
- Google Drive file and folder identifiers, names, metadata, and file contents.
- Google Docs content.
- Google Sheets spreadsheet structure, cell values, and other information required for requested operations.
- Google Forms structure and settings.
- Form responses, which may include information submitted by other people.
- Information identifying the connected Google account when required to select or manage the correct account.
When requested by the operator, the integration may create or modify Google Docs, Google Sheets spreadsheets, and Google Forms.
OAuth permissions may technically permit access to more data than is retrieved for an individual request. The integration is configured to use that access only for the features and purposes described in this policy.
Form responses may contain personal information submitted by other people. Such responses are processed only to carry out the operator's requests about the related form, and are handled under the same storage, retention, and disclosure rules described in this policy.
3. Purposes of processing
Google user data is used to carry out the operator's requests, such as locating files, answering questions about documents, summarizing content, editing documents and spreadsheets, and working with forms and their responses.
Requested background tasks or reminders may process relevant data when explicitly configured by the operator.
Data is not sold or used for advertising, advertising profiles, creditworthiness assessment, or unrelated commercial purposes.
4. AI processing and hosting
AI processing is performed by language models that run locally on the operator's own hardware, the same hardware that runs the assistant. The assistant is not configured to use external AI model providers or cloud fallback models.
Relevant file content, excerpts, metadata, prompts, and operation results are processed by these local models to generate a response or carry out a requested task. They are not sent to third-party AI providers.
If an external AI provider is added in the future, this policy will be updated to name it and link its policies before it is used with Google user data.
Google user data is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models.
Messaging channel
The operator sends requests to the assistant and receives its responses through Telegram. Responses may include excerpts, summaries, or other information derived from Google user data, so that information is transmitted through and stored by Telegram as part of the operator's private chat history, under the Telegram Privacy Policy.
The assistant responds only to the operator's account and is not used in group chats.
Assistant hosting
The assistant runs on personal computing hardware owned and controlled by the operator. It is not hosted on a third-party cloud or hosting service, and data stored by the assistant is stored on that hardware. Requests to Google APIs are sent over encrypted (HTTPS) connections; network and internet service providers carry this traffic as needed to provide their services.
The assistant is not exposed to the public internet. For security reasons, this policy does not publish further details about the operator's infrastructure.
5. Storage and security
OAuth credentials, including refresh tokens, are stored in the credential store of the gog command-line tool on the operator's computer that runs the assistant. They are not stored on this public website or in its source code. This website does not take part in the OAuth flow.
Retrieved content and generated responses may be stored on that computer in conversation history, assistant memory, logs, cached or downloaded files, and backups.
Access to that computer and to the stored credentials is restricted to the operator.
No system can be guaranteed to be completely secure.
6. Retention
The operator applies the following retention rules. Automatic deletion is performed by scheduled cleanup on the assistant's computer.
| Data | Retention |
|---|---|
| OAuth credentials | Kept in the credential store while access is needed, until the operator removes them. Revoking access in the Google account stops the stored authorization from working; the operator then deletes the local copy. |
| Conversation history | Deleted automatically after 90 days. |
| Assistant memory | Kept until the operator deletes it. Memory is used for short notes and preferences, not for storing copies of documents or form responses. |
| Logs | Deleted automatically after 30 days. |
| Messages in the operator's Telegram chat | Kept by Telegram until the operator deletes them from the chat. |
| Cached or downloaded files and temporary copies | Deleted automatically within 7 days. |
| Backups | The assistant's history, memory, logs, and cached files are excluded from device backups, so no backup copies of them are kept. |
The operator can delete any of this data earlier. Because AI models run locally, no external AI provider receives or retains request content.
7. Disclosure and access
Google user data is disclosed only as needed to provide the features described in this policy, to the service providers identified in this policy, when the operator explicitly requests a disclosure, or where required by applicable law.
The integration is not intended to expose the operator's Google data to other users of the assistant.
The assistant is used only by the operator. Human access to Google user data is limited to the operator, access explicitly authorized by the operator, and circumstances permitted by the Google API Services User Data Policy.
8. Revocation and deletion
The operator can revoke the application's access at https://myaccount.google.com/connections.
Revocation prevents continued use of the revoked authorization. It does not automatically delete previously downloaded data, conversation history, stored memory, logs, or backups.
To remove retained data, the operator removes the relevant local credentials and stored assistant data, and deletes any affected backups.
For questions or deletion requests concerning information processed by this integration, contact temik0112@gmail.com.
Revoking this application's access does not itself delete documents stored in Google Drive.
9. Google API Services User Data Policy
Cosmic Assistant'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.
10. Public website
This informational website does not request Google account authorization or intentionally collect file contents or OAuth credentials.
It does not use analytics, advertising trackers, cookies, or browser storage, and it contains no scripts or forms.
This website is served by a web server on a rented virtual server administered by the operator. The provider of that virtual server may process network traffic, such as IP addresses, as needed to provide and secure its services. The assistant's data and OAuth credentials are not stored on that virtual server. The web server is not configured to keep access logs for this website. Technical request information, such as the IP address and user-agent, is processed transiently to deliver the requested page and is not used for analytics, tracking, or advertising.
11. Changes and contact
This policy may be updated when the integration or its data practices change. The current version and its last-updated date are published on this page.
Contact: temik0112@gmail.com