Privacy Policy

Scope

The integration is operated by Jacob Padgett for his own Google Account. It is not a public service and does not solicit Google authorization from other people.

Google data accessed

At the owner's direction, the integration may access:

• Gmail messages, metadata, labels, settings, drafts, and sending functions;
• Google Calendar calendars and events;
• Google Drive files and metadata;
• Google Docs and Google Sheets content;
• Google Contacts on a read-only basis.

How data is used

Google data is used only to perform tasks requested or configured by the owner, such as searching and summarizing email, preparing calendar briefings, organizing files, editing documents, or sending owner-approved messages.

When the owner asks Hermes to analyze Google Workspace content, the content necessary for that task may be sent to the AI model provider configured by the owner. Those providers process data under their own terms and privacy policies. The integration does not use Google data for advertising, credit decisions, or unrelated profiling.

Storage and retention

OAuth credentials are stored locally on the owner's Mac in the Hermes application data directory. Workspace content or task-derived summaries may appear in local Hermes session logs, task artifacts, or owner-approved memory. The owner controls the computer, configured providers, retention, and deletion of those local records.

Sharing

Google user data is not sold. It is not shared with advertisers or data brokers. Data may be processed by Google, the owner's configured AI provider, and infrastructure services strictly as needed to complete an owner-requested task.

Security and control

The integration uses Google OAuth rather than storing the owner's Google password. Access is limited by granted scopes and can be revoked at any time through the owner's Google Account security settings. No security system can guarantee absolute protection.

Contact

Questions about this private integration may be sent to jacobpad@gmail.com.