Privacy policy

Prepared 3 October 2026. Operator: Sergei Savkin. This policy describes his personal OpenClaw Productivity installation, not other OpenClaw deployments.

Data accessed and purpose

With the owner's Google authorization, the application accesses account identity, read-only Gmail messages and metadata, calendar lists and owned calendar events, Google Tasks, and Drive files created by or explicitly selected for the app. These data support requested organization, task and event updates, document workflows, and daily or weekly briefings. Routine briefings include at most five bounded email snippets, not full message bodies; a specific mail-read request can retrieve a full message.

Processing and sharing

Separately from Google access, the owner authorizes on-demand document reads within his Mac Documents and Downloads folders, local document generation and OCR, read-only home/server diagnostics, public software-release research, and isolated coding tasks. Credential-like files are excluded from document discovery. These capabilities do not widen the Google OAuth scopes.

Personal organizer data are processed by the owner's Mac and private gateway, normally using a local language model. Owner-facing results may be delivered through Telegram and are then handled by Telegram. Google receives API requests needed to read or update the owner's data. Public-research cloud agents do not have organizer access. Any necessary premium cloud review must follow the owner's authorization and privacy settings; it is not the default briefing route.

Google user data are not sold, used for advertising, or used to train a general-purpose AI model. OpenClaw Productivity's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and retention

Google OAuth credentials are stored in the Google Workspace CLI's encrypted local credential store. Google originals remain in the owner's Google account. Retrieved content and generated results may remain in private assistant conversations, tool logs, local backups, and Telegram history until the owner removes them under the respective retention settings. This installation does not claim a fixed automatic deletion period.

With the owner's permission, private assistant memory and reusable procedure files can retain selected facts and lessons from work. This is retrieval and workflow learning, not training a general-purpose model. Automatically learned procedures cannot grant themselves new account or system permissions.

Control and deletion

The owner can revoke Google access at Google Account connections and stop the assistant or its scheduled briefings. Revocation stops future authorized API access but does not erase previously stored copies. The owner can separately remove Google records, assistant history and backups, Telegram messages, and local credentials using those systems' controls. Sending mail, inviting guests and deleting Google records are not exposed by the bounded organizer tool.

Contact and changes

For questions or data-removal requests, contact savkinsa92@gmail.com. This notice should be updated before materially changing the installation's data practices.