Google integration privacy

Effective November 10, 2026

This policy describes how we at Hyde Haus handle information through the Hyde Haus Workspace Assistant, our private Hermes-powered Google Workspace integration. It applies to the Google integration, rather than every service we may provide as an agency and consultancy.

Information we access

Access depends on the permissions granted by each connected account. Supported permissions cover Gmail message content, attachments, sender and recipient details, message metadata and labels; calendar details and events; and files and content in Google Drive, Docs and Sheets. We also store the OAuth credentials needed to maintain the connection. We do not receive your Google password through OAuth.

How we use it

We use Google information to perform requested assistant tasks, such as finding and summarizing messages, organizing email, preparing or sending communications, managing calendar events, and reading, editing, organizing or deleting files. Some permissions allow changes or sending as well as reading. The permission screen and the applicable workflow determine what an account authorizes.

AI processing and sharing

Relevant content can be included in assistant prompts and tool results. Our current runtime is configured to use OpenAI, with fallback models accessed through OpenRouter, including DeepSeek and Z.ai models. When a provider processes a request, it may receive the Google content included in that request. Provider logging, retention and data-use settings vary; we do not represent this integration as device-only or as providing zero-retention processing.

Requested workflows may also send information to destinations specified by the account owner, such as message recipients or documents. We do not sell Google user data or use it for advertising. We do not use Google user data to train models of our own. External provider handling is subject to the provider’s applicable terms and account settings.

Storage and retention

OAuth credentials are stored in per-account files on our managed assistant runtime. Conversation history, tool results, generated files and operational records may contain Google information. Copies may also exist in backups and in systems used to carry out a requested workflow. Records do not all share a single automatic deletion period and may remain until manually removed. We do not promise that a conversation ending automatically deletes its information.

Access and security

Access to the assistant runtime and connected accounts is limited to authorized operators. We use Google OAuth rather than asking users to disclose their Google passwords to the integration. No internet service or storage system can be guaranteed completely secure.

Revocation and deletion

You can stop future Google access by removing the integration from your Google Account connections. Revocation does not automatically delete information already stored in conversations, files, backups, external-provider systems or recipient accounts.

For a deletion request, email jonathan@thehydehaus.co identifying the connected account and information concerned. Do not send a password or access token. We will verify the request and explain the deletion we can perform, any records that must be retained and any provider or recipient limitations. We will not promise deletion from systems we do not control.

Changes and contact

We will update this page when the integration’s practices change. New uses requiring additional permission will require the appropriate authorization. Contact us at jonathan@thehydehaus.co.