Last updated: September 22, 2026

Privacy Policy

LifeOps is a personal and household scheduling application. This policy explains the information LifeOps may process, why it is used, and how Google account information is handled when a user connects Google Calendar.

1. Information LifeOps may process

Depending on the features a user chooses to use, LifeOps may store or process:

LifeOps account information, such as name, email address, account role, and password hash.
Tasks, routines, scheduling preferences, assignments, notes, links, and completion information.
Locations or addresses supplied for appointments, recurring destinations, route planning, or weather-aware scheduling.
Calendar information authorized through a connected Google account.
Technical information needed to operate the service, such as login sessions, sync status, remembered-device data, and error information.

2. Google Calendar data

When a user chooses to connect Google Calendar, LifeOps requests Google permissions needed for its calendar features. The application currently requests access to manage calendar events and read the user's calendar list.

LifeOps may process calendar names, event titles, event dates and times, event locations, event identifiers, event colors, availability, and other calendar metadata needed to display commitments and build a schedule.

LifeOps can create, update, or remove LifeOps-generated events on a calendar that the user explicitly configures as the LifeOps write-target/planning calendar. The LifeOps application is designed so other mapped calendars are treated as read-only sources unless the user configures otherwise.

Google API Limited Use: LifeOps' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3. Why information is used

To display and coordinate fixed appointments and calendar commitments.
To build and rebuild personal or household schedules.
To find common availability for shared tasks and routines.
To calculate travel, setup, teardown, and transition time when enabled.
To use weather information when a user enables weather-aware scheduling.
To synchronize LifeOps-generated planning blocks with the selected Google Calendar.
To show reminders, current and next activities, and completion status.
To maintain security, diagnose errors, and prevent duplicate synchronization.

4. Sharing, sale, and advertising

LifeOps does not sell Google user data or LifeOps user data. LifeOps does not use Google Calendar data for advertising, ad targeting, or building advertising profiles.

Information may be processed by service providers only when necessary to operate a feature the user chooses. Examples can include Google services used for Calendar synchronization, routes, geocoding, or weather information, and the hosting provider used to operate the LifeOps application.

Information may also be disclosed when required by law, needed to protect the application or its users, or directed by the user.

5. Storage and security

LifeOps uses technical safeguards intended to protect account and scheduling information. Passwords are stored as password hashes rather than readable passwords. Google OAuth tokens used by the application are stored in protected/encrypted form. The application is intended to be accessed over HTTPS.

6. Cookies and sessions

LifeOps may use session cookies and remembered-device information to keep users signed in and maintain application state. These are used for operation and security, not advertising.

7. Retention, disconnection, and deletion

LifeOps keeps information for as long as it is needed to provide the application or until it is deleted by the user or application administrator, subject to temporary backups and records that may be retained for security or legal reasons.

Disconnecting Google Calendar stops future Google Calendar synchronization through LifeOps. A user may also revoke LifeOps access from their Google Account permissions.

A user who wants their LifeOps account or stored personal information deleted may contact the LifeOps administrator using the contact method provided when access to LifeOps was granted.

8. Third-party services

LifeOps may interact with third-party services, including Google APIs. Those services have their own privacy policies and terms. LifeOps requests access intended to support features visible to the user.

9. Changes to this policy

This policy may be updated when LifeOps features or data practices change. The date at the top of this page will be updated when material changes are made.

10. Contact

Privacy questions and deletion requests may be directed to the LifeOps application administrator using the contact information supplied with the user's LifeOps account or invitation.