Wren Complex · AgentOS Workspace

Privacy Policy

Effective: October 27, 2026

This policy describes the use of Google Calendar data by AgentOS Workspace, a personally operated integration within Wren Complex at wrencomplex.com. The integration is currently intended for the project owner's personal use, not for public account registration.

Google information accessed

With the account owner's explicit Google authorization, AgentOS Workspace may access Google Calendar information, including calendar names, events, dates, times, descriptions, locations, attendees, and calendar configuration or sharing information as permitted by the granted scopes.

Its requested full Calendar permission can also permit creating, editing, sharing, or deleting events and calendars. Those capabilities are used only when the account owner enables or requests corresponding actions.

Why the data is used

Calendar information is used to answer the owner's scheduling questions, provide agenda summaries, identify conflicts and upcoming commitments, and carry out calendar changes authorized by the owner. It is not used for advertising or sold to third parties.

Processing, storage, and sharing

Authorization is handled through Google's OAuth flow. OAuth credentials and related configuration are stored by the locally operated Hermes/AgentOS software on the owner's Mac according to its configuration. Calendar information may also appear in local session histories, generated notes, reports, or task records when needed for the owner's workflows.

When an AI-assisted answer or task requires it, relevant calendar details may be transmitted to the model provider configured by the owner for processing. Google user data is not used by this personal integration to train generalized AI models. The configured provider's own privacy and data-processing terms also apply.

This public informational website does not expose private Calendar data, collect Google passwords, or run third-party marketing analytics. Its hosting provider may process ordinary web requests to serve the pages.

Retention and control

The owner controls their connected account and local AgentOS files. Google data may persist in the owner's local history or generated artifacts until deleted. OAuth credentials remain until removed or revoked, subject to Google token expiration and security controls.

The owner can revoke Google account access in Google Account connections and remove any locally stored authorization and related records from the Hermes/AgentOS environment.

Security and updates

The integration is intended to operate in the owner's private environment rather than expose Calendar content publicly. No online system can guarantee perfect security. This policy will be updated if the integration's access, data handling, or use materially changes.

Questions

For privacy questions, contact the project owner using the support email provided on the Google OAuth consent screen for AgentOS Workspace.