OpenClaw Jarvis · Gmail data transparency

Privacy Policy

How the personal M7 Gmail read-only integration accesses, processes, and may retain Google user data.

Last updated: 8 November 2026 · Independently maintained personal project

1. Scope, purpose, and permission

OpenClaw Jarvis is a privately maintained personal assistant. This policy covers its M7 Gmail OAuth integration through Composio, used by the account owner for email search, reading, summarization, relevant attachment review, and preparation of text-only reply suggestions. This website is informational and does not itself sign users in, collect Google passwords, or execute Google OAuth callbacks.

The integration was last verified with the Google OAuth permission https://www.googleapis.com/auth/gmail.readonly on 1 November 2026. This permission permits broad read access to Gmail messages and their metadata, potentially including attachments; it is not limited to a single email. In the M7 integration, the exposed tools are for retrieval and reading, not sending, modifying, or deleting messages.

The broader OpenClaw environment may have other, separately authorized Gmail connectors that expose different tools. Their permissions and data processing are not covered by this specific M7 OAuth grant; these statements must not be interpreted as a claim that every possible assistant integration is read-only.

2. Information processed and service recipients

Depending on the user's request, the integration may process an authorized account identifier; search terms; message or thread identifiers; labels and metadata; sender and recipient details; subjects, dates, snippets, message bodies, and relevant attachments. Generated summaries, action items, and draft reply suggestions may contain personal information derived from messages.

Google / Gmail

Google handles account sign-in and consent and responds to authorized Gmail API requests.

Composio

Composio manages the OAuth connection and Gmail tool execution, receives tool requests, and returns authorized results to OpenClaw. It processes connection details, tool payloads, and execution metadata. Its published privacy policy describes execution logging and retention; see Section 4.

OpenClaw (operator-managed installation)

OpenClaw receives tool results, manages conversation context, and produces or stores associated session history, task outputs, and summaries. Some stored data may remain on the operator's equipment or in associated backups.

Selected model service, including OpenAI

Message content, tool results, or relevant conversation context may be transmitted to a selected hosted model provider to answer user requests. OpenAI is currently among the model providers used by the assistant. The particular model and routing can vary by session or configuration. The exact fields transmitted for each request have not been independently audited; model-provider logging, training controls, and retention are governed by the applicable account settings and service policies.

Attachments may be retrieved and parsed as part of a user-requested task. Their processing is not guaranteed to remain local or confined to a particular machine or service. No representation is made that all Gmail data stays exclusively on the operator's devices.

3. Purposes, transfers, and Google's Limited Use rules

Gmail data is accessed to provide requested personal email productivity features: search, reading, summarization, relevant attachment understanding, and preparing suggested responses for the owner to review. Sending or modifying messages is not part of this M7 read-only OAuth integration.

This integration is not intended to sell Google user data, use it for advertising or profiling, disclose it to data brokers, or create, train, or improve general-purpose AI models. The operator commits that use of information received from Google Workspace scopes will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Access and transfers must be limited to providing the user-requested service and other purposes permitted by the applicable Google API Services User Data Policy and Google Workspace user data and developer policy, including their Limited Use requirements.

Use of a hosted model service does not by itself establish that every model provider's data controls meet those requirements. The operator must use provider settings and services consistent with Limited Use; any unverified or incompatible use must be addressed before production reliance on the integration. This policy is a description of intended and observed processing, not a certificate of Google verification or an independent security assessment.

4. Storage, retention, and security

Composio: Under its published Privacy Policy, stored tool execution payloads are generally kept in execution logs and automatically deleted one year after a call. If an organization is deleted, its payload data and execution logs are scheduled for deletion within 30 days. Composio may retain de-identified execution metadata indefinitely. These are provider-policy statements, not an independently verified audit of every record for this project; Zero Data Retention has not been confirmed as enabled.

OpenClaw: Conversations, summaries, and task outputs may be written to persistent session records or locally held report files. Cache, logs, memory, and backups may contain additional copies. No single verified automatic erasure period applies to all such data.

Model services: Model providers may process or retain submitted context under their applicable terms and account settings. A single universal provider retention period, training exclusion, or comprehensive deletion process has not been verified for all historical and possible routes.

Because these systems have distinct storage mechanisms, this policy does not promise zero logging, zero retention, a fixed deletion date for every copy, or automatic erasure after an email is deleted in Gmail. Access to credentials and stored content should be restricted to authorized operators, and transport and stored data should be protected by the applicable security controls. No independently audited security certification is claimed here.

5. Account access, revocation, and deletion requests

  1. Review and, if desired, revoke the relevant OAuth authorization through Google Account connections. Revocation stops new access under that grant after it takes effect.
  2. Disable or disconnect the Composio Gmail connection to stop further tasks from using that connection.
  3. For information about retained OpenClaw sessions, generated outputs, and copies under the operator's control, or to request review or deletion, contact reikoren1995@gmail.com.

Revoking access, disconnecting Composio, deleting a Gmail source message, and deleting already-processed records are different actions. Existing Composio logs, OpenClaw conversations, backups, and model-provider data may require separate deletion procedures subject to provider capabilities and legal requirements. No universal instant-deletion guarantee is offered.

6. This public information website

The website is hosted as static pages on Cloudflare Pages. The supplied pages do not include scripts for OAuth, Gmail API calls, account forms, advertising pixels, or third-party analytics tags. Visiting them does not authorize mailbox access.

Cloudflare may process website request data such as IP address, requested URL, browser information, and timestamps for hosting, security, and service operation, according to its Privacy Policy. Contact email messages are also handled by the relevant email services.

7. Maintainer, contact, and updates

OpenClaw Jarvis is a personal project maintained by its owner. Privacy questions and requests may be directed to reikoren1995@gmail.com.

Material changes to permissions, processing purposes, third-party recipients, or retention practices should be reflected in this policy and, where required, be subject to renewed user consent. Last updated on 8 November 2026. Google and Gmail are trademarks of Google LLC; this is not a claim of endorsement, verified status, or completed OAuth publication.