Privacy & account control
Privacy policy
Effective 16 October 2026 · Operator: Joaquin Gonzalez
1. What this notice covers
OpenClaw gog is a personal Google Workspace integration used through a privately operated OpenClaw assistant. This notice describes its handling of Google data and the separate app-information website. It is not operated by or affiliated with Google.
2. Google data accessed
The Google connection is authorised for Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, Tasks, Chat, Classroom, Forms, Meet, Apps Script, Drive Activity, Drive Labels, Sites, Analytics, Search Console, Google Ads, YouTube, Photos and account profile information. Available operations also depend on enabled APIs, account type and service-specific restrictions. Exact access is governed by the permissions granted to the OAuth client, not just by a particular task.
| Service | Data and possible operations |
|---|---|
| Calendar | Calendar and event details, including titles, times, descriptions and attendees; event changes where authorised. |
| Drive | File names, metadata and file contents. Full Drive access can include creating, editing and deleting files. |
| Sheets | Spreadsheet metadata, cell values and formulas; spreadsheet changes where authorised. |
| Gmail | Email messages, attachments, labels and supported mailbox settings; reading, composing, sending and organising mail only for authorised tasks. |
| Other authorised services | Documents and presentations; contacts and tasks; chat and classroom data; forms and responses; meeting spaces; Apps Script projects and deployments; Drive activity and label schemas; Sites files; analytics and search performance; advertising account data; YouTube read access; app-created Photos media; and account profile data, as permitted by each granted scope. An OAuth grant alone does not enable every API or approve spending, messaging, publication or deletion. |
| Authentication | Account email, permission information and OAuth tokens required to make authorised Google API requests. |
3. Purpose and use
Google data is used only to fulfil the owner’s requests and explicitly configured automations, such as retrieving information, organising calendar events and updating spreadsheets. Background tasks may access Google services while the owner is offline. Authorisation does not make every possible action an approved task.
4. Processing and sharing
The integration runs on a Hostinger-hosted VPS. Google processes authentication and API requests. When an assistant task uses an AI model or returns a result through a messaging channel, relevant task data may also be sent to the AI provider and messaging service configured by the owner. This can include file contents, calendar details or spreadsheet data needed for that task.
The current assistant configuration selects OpenAI models and Telegram messaging, and also contains optional Nexos provider routes. Providers used for a particular task depend on the selected model and channel. Their relevant policies are available from OpenAI, Nexos, Telegram and Hostinger. Provider processing and retention depend on the account, product and settings in use. The operator must use Google data only through configurations consistent with the Limited Use commitment below.
5. Storage and security
OAuth refresh credentials are held in a password-protected file keyring in persistent VPS storage so the integration can renew access without interactive sign-in. Task results may also persist in assistant conversations, logs, saved files and backups. Tokens must not be placed in public pages, source repositories or chat messages. Access to the VPS and stored credentials must be restricted to authorised operators.
6. Retention and deletion
Revoking Google access prevents further use of the revoked credentials. It does not by itself delete data already copied into the assistant or its service providers. The operator must separately remove stored credentials, relevant conversations, logs, task output and retained backups as appropriate.
No fixed automatic deletion period is promised. Stored credentials are kept while the connection is in use; saved conversations, logs and task outputs may remain until removed by the operator or the applicable service’s retention process. VPS backups are currently scheduled weekly and can retain earlier copies until those backups expire or are removed. Contact the operator to request deletion and confirmation of any copies that remain subject to provider or backup retention.
7. Your choices
- Review or revoke access at Google Account connections.
- Disable configured OpenClaw automations to stop their scheduled work.
- Contact the operator to request access to or deletion of stored integration data.
8. Google Limited Use commitment
The integration’s use and transfer of information received from Google APIs must comply with the Google API Services User Data Policy, including its Limited Use requirements. Google data must not be sold, used for advertising or used to train general-purpose AI models. Any human access must be limited to what Google’s policy permits.
The operator does not authorise the sale of Google data, advertising use, or training of general-purpose AI models with Google data. Changes to model providers or processing settings must preserve these restrictions.
9. Information website
The supplied website code contains no analytics scripts, advertising trackers, Google sign-in flow or data-entry forms. Its hosting provider may process request information to deliver and secure the site, and operational cookies may be used by the hosting service. Email links use the visitor’s chosen email application.
10. Contact and updates
Operator and privacy contact: Joaquin Gonzalez, gonzalezgomez.joaquin@gmail.com. Material changes to uses, recipients or permissions will be reflected in this notice with a revised effective date.