Your tasks, used to
carry out your requests.

Last updated October 18, 2026 · Operated by Bryan Davis

Information accessed

The connection verifies the authorized Google account’s email address and accesses Google Tasks information: task identifiers, titles, notes, completion/deletion state, and date-only due fields. The read-only Tasks permission technically covers all lists; normal polling reads the default list.

Existing task identifiers are retained to prevent old work from being executed. New captured requests, processing state, and delivery receipts are kept in private operational storage. OAuth credentials are stored privately on the owner’s Raspberry Pi, with an authorization copy on the owner’s computer.

How information is used and shared

Information is used to verify the account, capture the owner’s instructions, prevent duplicate execution, carry out authorized work, and return results or clarification.

Captured text is processed by Chief’s configured AI and automation services, including Anthropic or OpenAI and Hermes/n8n. Telegram carries responses. Depending on the requested action, instructions or resulting work can be processed or stored through configured specialist research services such as Gumloop, Supabase operational storage, Notion documents, or the separately connected Google Drive-backed Obsidian vault. Those connections are separate from the Tasks-only Google permission.

The bridge does not sell Google Tasks data or use it for advertising. It does not itself train AI models. Downstream providers’ handling of service data also depends on their policies and the owner’s account settings; this page does not promise that every provider has identical retention or training settings.

Retention and backups

There is currently no automatic deletion period for captured requests and assistant transcripts. Operational records remain until the owner removes them. Encrypted operational recovery copies can be retained on the owner’s devices. Copies in connected services follow their configured account settings and policies.

Control and deletion

The owner can revoke the connection through Google Account connections and stop the scheduled bridge. Revoking access stops future authorized retrieval but does not delete existing local, backup, or downstream records. Deletion or export requests require owner-directed review of the affected systems; automated cross-service erasure is not implemented.

Contact

Questions about this connection or its data handling: chief@bryandavis.media.