Privacy policy

1. Who operates the integration

LifeOS Calendar Sync is a personal-use integration operated by Chris for a privately managed LifeOS and Hermes installation. Contact: criashi@gmail.com. This policy covers the integration and these public information pages.

2. Google data accessed

With the account owner’s Google authorization, the integration can access calendar-list information, including calendar names, identifiers, and access roles, and Calendar event information, including event names, times, descriptions, locations, and attendee information where available.

Google’s event permission can allow creating, updating, and deleting events on calendars the account can access. Actual operations depend on the selected calendar, its access permissions, and the owner’s instructions or configured workflow.

3. How information is used

• Read schedules and answer the owner’s calendar or planning requests.
• Create or update events from explicitly marked LifeOS plans.
• Perform calendar operations requested by the owner through Hermes.
• Keep event identifiers, scheduling fields, and synchronization metadata needed to reconcile managed plans and avoid duplicate events.
• Diagnose authorization and synchronization failures.

The automatic LifeOS synchronization process is deterministic and does not call an AI model.

4. Storage and protection

Google maintains calendar and event data in the authorized Google account. The owner’s private LifeOS/Hermes installation stores the OAuth credential and the local information needed to operate the integration. Credentials are kept outside the notes vault and are restricted with filesystem permissions.

Calendar-related information may also be retained in the owner’s notes, assistant conversations, logs, synchronization state, and backups according to the owner’s configuration. These public information pages contain no live calendar data, OAuth tokens, or Google client secrets.

5. Sharing and AI processing

The integration communicates with Google to provide Calendar features. When the owner asks Hermes to process calendar information, relevant event details may be included in requests to the assistant or AI service providers configured by the owner. Those providers process requests according to their applicable service terms and configured privacy and retention settings.

Google data is not sold, supplied to advertising platforms, or used by this integration for targeted advertising. The integration itself does not train AI models. Calendar data is not published on this website.

Google API information is used for the calendar and planning features described here, subject to the Google API Services User Data Policy and its Limited Use requirements. Information may also be disclosed where necessary to protect the integration or comply with applicable law.

6. Retention, revocation, and deletion

The owner controls the retention of local integration data and backups. Information stored in Google, assistant conversations, or service-provider systems is also subject to those services’ retention settings and policies.

To stop future Google access, remove the integration from Google Account connections and stop the local Calendar integration. The operator can remove local credentials and synchronization state. Contact criashi@gmail.com for assistance with the installation’s stored data.

Revoking access does not automatically delete existing Google Calendar events or erase information already saved in notes, conversations, logs, or backups.

7. Public website requests

These information pages have no sign-in form, calendar connection, advertising scripts, or custom analytics. The website’s hosting and network providers may process request metadata, such as IP addresses and browser information, to deliver and secure the site.

8. Changes and contact

Changes to this policy will appear here with an updated date. A material change to Google data access or use requires an updated disclosure and any consent Google requires. Questions can be sent to criashi@gmail.com.