Terms of use

1. Purpose and operator

LifeOS Calendar Sync is operated by Chris for a personal LifeOS and Hermes installation. It supports reading Calendar information and performing calendar operations authorized by the owner. These public pages describe the integration; they do not offer public account registration, a paid subscription, or a public Calendar service.

2. Authorized use

Use is limited to the operator and accounts the operator expressly authorizes. Connect only Google accounts and calendars you have permission to access. Use the integration in accordance with applicable law, Google’s requirements, and the terms of any assistant or AI service you configure.

3. Calendar operations

Google authorization determines the Calendar permissions available to the integration. LifeOS sync uses explicitly marked plans to create or update managed events. Hermes may perform calendar operations in response to the owner’s requests. The owner is responsible for the plans, instructions, calendar selection, and automation configuration supplied to the integration.

Check important event details and scheduling changes. The integration’s automatic sync does not delete stale events or reopen completed tasks.

4. Availability and limitations

Operation depends on the owner’s installation, network connectivity, Google APIs, and any configured assistant providers. Availability, uninterrupted synchronization, and error-free scheduling are not guaranteed. Google access can expire or be revoked, and API limits or service changes can interrupt operation. Keep independent reminders for time-critical commitments.

5. Privacy and third-party services

The privacy policy explains the Google information accessed, how it is used and stored, and when assistant providers may process it. Google and configured service providers also have their own terms and policies. LifeOS Calendar Sync is an independent personal integration and is not endorsed by Google.

6. Stopping use

You can stop using the integration by disabling its local workflows and removing its access in Google Account connections. Existing events and previously stored information remain until separately removed from their respective locations.

7. Updates and contact

These terms may be updated as the integration changes; the current version and date will appear on this page. For questions, contact criashi@gmail.com.