OpenClaw gog private · updated 14 September 2026 · home
Current status: this Gmail integration is not yet active. It currently collects no Gmail data and transfers no Gmail data to an AI provider. The sections below describe the planned first trial; access controls and provider settings must be verified before activation, and this page will be updated when the integration starts.
This application is operated privately by zsuzo7 for their own personal use. It is not a commercial product and is not offered to other people. The only Google Account that authorizes it is the operator's own.
After activation and the operator's consent, the application is intended to use the Gmail API to read message metadata from the operator's own mailbox — such as the sender, recipient, subject, date, and labels of a message. The planned scopes are:
gmail.metadata — message headers and labelsuserinfo.email and openid — to identify which account granted accessThe planned Google Cloud Pub/Sub connection notifies the application when the mailbox changes. Those notifications contain the account address and a change identifier only — never message content. The application then requests metadata for the changed messages through the Gmail API.
The Gmail permission covers metadata across the mailbox; it is not restricted by Google to particular senders. The trusted service must inspect message headers to apply the sender policy. The planned restriction is that denied metadata is not passed to the assistant or retained in ordinary processing logs. This restriction must be tested before activation.
OpenAI is the proposed AI provider, matching the operator's existing assistant configuration. In the planned trial, only admitted metadata, such as sender and subject, and the instructions needed for the task may be sent to that provider. No Gmail data is currently sent.
The provider's retention and data-use terms depend on the service, account and settings used. Those settings will be checked and described before activation. This page does not claim that zero retention or a provider-wide training exclusion has already been established.
No Gmail data is currently retained by this integration. For the planned trial, admitted metadata and assistant results may remain in local conversation or processing history until the operator deletes them. No automatic expiry period has been implemented or promised.
Credentials and the minimal state needed to resume processing will be kept separately until the integration is disconnected and that state is deleted. Deleting a conversation does not necessarily remove logs, backups, or provider-held copies; those require separate review and deletion under the applicable controls. The operator can be contacted below about stored data.
The operator does not sell or rent Google user data or use it for advertising or training models. Any future processing by Google and the selected AI provider must be limited to the disclosed personal-assistant workflow. Provider settings must be reviewed before any transfer.
Before activation, the application's use and transfer of Google user data must be checked against the Google API Services User Data Policy, including the Limited Use requirements.
Access can be revoked at any time at myaccount.google.com/permissions, which removing the application's authorization. The operator should also stop the watcher and remove stored credentials. Revocation does not delete data already obtained or provider-held copies.
If the application's access is extended — for example to read message bodies or to send mail — this policy will be updated before that change takes effect, and the date above will change.