Sudo Assistant

Privacy

Effective date: 20 October 2026. This page describes the private Sudo Assistant integration operated by Daniel Graetzer.

Data accessed

With the account owner's Google authorization, Sudo Assistant can access email messages, headers, labels, and attachments needed for requested tasks. Authorized accounts can also send mail on the owner's instruction. Each account has its own Google authorization.

How data is used

Google data is used to search and summarize mail, answer the owner's questions, and prepare or send requested messages. Sudo Assistant does not sell Google data or use it for advertising. Google Workspace data is not used by Sudo Assistant to develop or train generalized AI models.

Storage and processing

The integration runs on the owner's computer. OAuth credentials are stored in the macOS keychain. Task data and outputs may be retained in local assistant history and logs.

When needed for a requested task, selected email content may be processed by the configured AI provider or included in the owner's configured chat interface. The current setup uses OpenAI Codex and Telegram. Those services have their own privacy, retention, and account settings.

Control and revocation

The owner chooses which accounts to connect and can revoke access in Google Account connections. Revocation prevents future API access; it does not automatically erase previously saved local history or copies in other services. Local task history and downloaded files can be removed separately.

Limited use

Sudo Assistant's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.