Jerry IT Dev · Personal tools

Privacy Policy

Effective date: 9 October 2026 · Application: Personal OpenClaw Assistant · Operator: Jerry IT Dev

This policy explains how the Personal OpenClaw Assistant (the “Assistant”), a personal, self-hosted automation system operated by Jerry IT Dev, accesses, uses, stores and shares Google user data. The Assistant is intended for the operator's personal use and is not offered as a public service.

1. Information accessed

Gmail (read-only): selected email message metadata, such as sender, subject and date, and message content needed to classify messages and create summaries or alerts.
Google Calendar (read-only): calendar names, event titles, dates and times, and other event details needed for daily agendas and appointment reminders.
Authentication information: Google OAuth tokens needed to maintain authorised account access.
Operational data: limited application configuration, diagnostic records, and outputs required to run and maintain personal automations.

2. How the information is used

Identify potentially important email and summarise it for the authorised account owner.
Retrieve calendar events to create a daily brief and send upcoming-event reminders.
Produce notifications through the owner's chosen Telegram bots.
Authenticate API requests and maintain the reliability and security of the self-hosted Assistant.

These integrations use read-only access. The Assistant does not use these permissions to send or delete emails, or to create, edit, or delete calendar events.

3. Processing and third-party services

The Assistant is hosted on a device controlled by the operator. Where a workflow needs language analysis or summarisation, relevant portions of Google user data may be sent to OpenRouter and the selected downstream AI model provider to generate the requested result. Those services process data outside the local device and may have their own handling and retention practices.

Selected summaries or reminders may be sent through the Telegram messaging platform to the operator's configured chat. Google APIs, Google Cloud services and Cloudflare-based webhook/network components may also be involved in authorisation and notification delivery.

The operator should configure third-party providers consistently with Google's applicable data-use restrictions. Google user data is not intentionally used by the operator to train general-purpose AI models, for advertising or for sale. This notice does not claim that every external provider offers zero retention or no training; the provider settings and applicable terms must be reviewed before enabling a workflow that transmits Google user data.

4. Storage, protection and retention

OAuth credentials and operational configuration are maintained on the self-hosted device, with access restricted to the operator. Operational records and backups may contain personal information from connected workflows. Backups may be copied to another device under the operator's control, with encrypted off-site backup practices used in the current setup.

Data is kept for as long as it is needed to run, troubleshoot and back up the owner's personal automations, subject to configured backup rotation and manual deletion. Removal from active storage may not immediately remove the same data from existing rotating backups or third-party provider systems.

5. Choices, revocation and deletion

The Google account owner can revoke the Assistant's OAuth access at any time in Google Account — Third-party connections. The operator can also disable the integrations, remove locally stored credentials, and delete stored workflow records and backup copies according to the system's retention procedures. To request clarification or deletion of data controlled by the operator, use the contact details below.

6. Limited use and disclosure

Google user data is accessed only for the personal features described here. The operator does not sell personal information or share it with advertisers. Transfers to service providers are limited to those needed to supply the requested automation features. Access to Google user data is not used for unrelated profiling or surveillance.

7. Changes

This policy may be updated when the Assistant's permissions, workflows or providers change. Material changes affecting Google user data will be reflected on this page before the relevant new processing is enabled.

8. Contact

Operator: Jerry IT Dev
Privacy contact: REPLACE_WITH_YOUR_CONTACT_EMAIL

Before publishing this policy: replace the contact placeholder with a real working email address, and confirm that all statements accurately describe the deployed OpenClaw configuration and its selected AI providers.