bubs.

Google data handling and privacy

Effective September 15, 2026. This page describes the current private development version.

Information accessed

With the account owner's authorization, Bubs accesses account identity and the approved Google services: Mail searches and message contents, Calendar lists and events, and Drive file names and metadata. Drive file contents and email attachments are not downloaded by this integration.

Purpose and storage

Information supports the requested assistant tasks and a local review queue. Bubs stores limited headers, snippets, event details, file metadata, synchronization progress and local review decisions on the owner's computer. Authentication tokens are encrypted for the owning Windows account. Other workspace data is not separately encrypted by this feature.

Models and other processors

Routine synchronization makes no AI-model requests. When the owner asks an assistant to analyze information, retrieved content can be sent to the assistant's configured cloud model provider, or processed by its configured local model. Tool records and replies can become part of local conversation history and memory. The selected provider's terms and data practices also apply.

Access and removal

The owner can pause synchronization, disable a connection, revoke an assistant's access, or remove the Google connection. Removing a connection deletes its current tokens, working cache and review progress from Bubs. It does not delete Google data, previously discussed conversation content or earlier backups. These require separate management. The account owner may also revoke authorization in their Google account settings.

Current scope

This version does not send or change Google data. Telephone integration is not active. This page will be updated when features, processors, retention or distribution change.

Support and data-handling questions: relaxanator@gmail.com

About Bubs