Privacy Policy

This policy explains how Knowledge Hub handles information made available through connected sources, including Google Drive.

Last updated: September 14, 2026

1. What we access

After you authorize Google OAuth, Knowledge Hub may receive metadata and content from files that are available to the application within the permissions you grant. The intended Google Drive scope is read-only. The final OAuth scope list must match the application's actual configuration.

Knowledge Hub does not need permissions to create, modify, delete, publish, or change access to Google Drive files. Standard identity scopes such as openid, email, and profile may also be used if present in the actual OAuth configuration.

2. How information is used

Google Drive data is used only to provide Knowledge Hub functions: reading, indexing, incremental change detection, semantic search, and generating relevant context or answers. It is not used for advertising or sale of data.

3. Indexing and processing

Knowledge Hub processes accessible documents on its own infrastructure. It does not create a complete permanent local mirror of Google Drive. Supported documents may be converted into text, divided into chunks, and represented by embeddings. Embeddings and related metadata are stored in the Knowledge Hub search index, including Chroma. A local service registry may store file metadata and hashes for incremental indexing.

Knowledge Hub uses a locally managed model through Ollama for relevant processing. The application does not require sending data to a public cloud LLM for basic indexing and search.

4. Storage and retention

Chunks, embeddings, vector records, file metadata, hashes, logs, and any related service state may be retained as needed for the operation of the application. Specific retention periods have not yet been established and are not stated in this policy. Search queries and generated answers are not stored as separate user data unless the application's actual logging configuration records them.

5. Security

We use operational safeguards appropriate to the service. This policy does not make claims about particular encryption algorithms or other technical controls that have not been confirmed for the deployed configuration.

6. Revoking access and deletion

You can revoke Knowledge Hub's Google access through your Google Account permissions. After revocation, API access stops, new data is no longer loaded, and existing indexed data is not automatically removed because an automatic revocation deletion mechanism is not currently implemented.

To request deletion of Knowledge Hub data related to your Google Drive, email support@strat-tools.ru. The request may cover chunks, embeddings, Chroma records, file metadata, hashes, and incremental-indexing state related to your Google Drive. Data from other sources, such as a local Obsidian vault, is not automatically deleted because Google access was revoked and requires a separate explicit request. A specific completion period is not stated because one has not yet been established. Backup deletion procedures are not represented as implemented.

7. Google API Services

Knowledge Hub's use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including Limited Use requirements where applicable.

8. Contact

For privacy questions or deletion requests, contact support@strat-tools.ru.