Privacy Policy
Last updated: 4 November 2026.
This policy describes how Weeves handles Google user data for its private, owner-operated assistant functions. The integration is for its account owner only; there is no public registration or shared-user onboarding.
Google data accessed and purpose
On a direct owner request or under an agreed standing instruction, the integration may read Gmail message content and metadata, Google Calendar event details, Drive file metadata, and selected Google Docs and Sheets. The current Gmail authorisation is technically broader than simple reading: it permits full-mailbox access and composing, sending, modifying and deleting messages. An OAuth grant is technical capability, not authority to take an arbitrary action. A direct request or applicable standing instruction must cover the action; anything outside that scope is not performed. Calendar, Drive, Docs and Sheets are configured for read-only use.
Google data is used only to provide requested assistant functions, such as finding correspondence, summarising information, identifying dates or action items, and answering questions about selected files. The operator does not sell Google data, use it for advertising, or train its own model on it.
How data is processed and shared
The self-hosted n8n service holds the Google OAuth credentials and makes the Google API connection. Its credential store encrypts credential data using the instance’s local encryption key. The instance is configured not to retain successful or failed workflow execution payloads.
When a requested task uses AI, task-relevant context is sent to OpenAI Codex to produce the response. The assistant does not apply an automatic personal-data redaction step before model processing. OpenAI says ChatGPT Data Controls govern whether eligible interactions may be used to improve models, and Codex has a separate “Include environments” control for environment context. Whether any specific interaction is used for model improvement depends on the applicable account plan and data-control settings; this notice does not claim that such use is disabled. OpenAI’s terms and privacy notice apply to data shared between Codex and ChatGPT. The provider-side retention period for this Hermes route has not been confirmed, so no fixed provider deletion period is promised. See OpenAI Data Controls and Codex account terms.
These static pages are hosted through Cloudflare Pages. Cloudflare may process visitor IP addresses and request metadata to deliver and protect the site under its own Privacy Policy. The site contains no forms, user accounts or analytics scripts and does not host n8n, Google credentials or the screen viewer. The exact retention of Cloudflare request metadata for this deployment has not been established.
When the owner uses Telegram, the response, including any Google-derived summary the owner requested, is delivered in that Telegram conversation. Telegram therefore receives the content of those messages under its own service and account settings. The existing Microsoft Outlook integration is separate from Google Calendar and is not part of the Google OAuth connection.
Storage and retention
OAuth credentials are stored in n8n’s encrypted credential store. n8n is configured not to save successful or failed workflow execution payloads. Local assistant conversation records may contain requests and responses. Automatic session pruning is currently disabled; the configured 90-day age is only a threshold if pruning is enabled, so no automatic deletion deadline is promised.
Routine system backups retain the last three copies per configured system. Additional recovery copies are retained separately and currently have no scheduled expiry. Recovery backups may include application data, configuration and encrypted credentials. Revoking Google access does not by itself remove existing local conversation records or backups.
Security and user control
Access is restricted to the privately operated assistant environment. The operator uses Google data only for the requested feature. Direct owner requests and agreed standing instructions can authorise actions within their scope; OAuth permissions alone do not authorise arbitrary sends, deletions or changes. The owner can revoke Google access in Google Account security settings and can request removal of the local n8n credential. Neither action automatically removes conversation records or backups.
Changes and contact
This notice will be updated if the data accessed, processors, security controls or retention practices change.
Contact: privacy@stosh.uk.