Private context.
Clear boundaries.

LifeOps is a private, single-user personal productivity and automation system. This policy explains how it handles Google user data for its sole owner.

Effective September 13, 2026

Information LifeOps accesses

With the owner’s authorization, LifeOps can read:

Basic Google identity information, such as the account email address and basic profile information, to identify the authorized owner.
Gmail information, including message and thread identifiers, headers, labels, message bodies, and attachments when needed to understand a source completely.
Google Calendar information, including calendars and event details visible to the authorized account, such as titles, descriptions, times, locations, attendees, and recurrence information.

Current operating mode. LifeOps currently uses Gmail and Google Calendar data on a read-only basis. The running system does not send, modify, or delete Gmail messages and does not create, modify, or delete Calendar events.

Intended owner-directed features. The OAuth configuration also includes permissions intended for future features that can prepare or manage Gmail drafts, compose email, manage labels, and create or update Google Calendar events. Those features are not active in the current system. If enabled, they will run only through owner-configured, purpose-limited automation. LifeOps is not designed to send email or delete Gmail messages or Calendar events autonomously.

Why this information is used

LifeOps uses Google information only to provide personal productivity features to its owner. These include identifying evidence, reminders, bills, tasks, deadlines, commitments, and questions that may require attention; relating new information to existing personal work; and preparing concise planning or attention summaries.

Gmail content is read when the content is needed to understand the source, not merely to collect it. Calendar information provides time context, helps avoid duplicate reminders, and supports daily planning.

Intended Gmail write features are limited to owner-directed draft preparation, composition workflows, and label management. Intended Calendar write features are limited to owner-directed creation or updating of events, with duplicate checks and verification. These features are currently inactive and are not used for background sending or deletion.

Processing, service providers, and sharing

LifeOps runs through owner-controlled local automation. Relevant Gmail content, attachments, Calendar context, and derived source bundles may also be processed by the owner’s configured AI and automation service—currently OpenAI Codex—when semantic interpretation is needed for a LifeOps feature.

Information is provided to that service only to deliver the owner-facing LifeOps feature. LifeOps does not use Google user data to train or improve a generalized artificial intelligence or machine-learning model. The configured provider’s handling of data is also subject to the owner’s account terms and data controls.

When the owner configures them, LifeOps may send limited derived information—such as a task title, reminder, short summary, or focused question—to personal execution and messaging services such as Todoist or Telegram. Encrypted copies may be synchronized through Microsoft OneDrive or a configured Git hosting service. These transfers are limited to providing the requested LifeOps feature, storage, synchronization, backup, or recovery.

Google user data is not sold, rented, shared with data brokers, or used for advertising, retargeting, credit decisions, or surveillance. LifeOps has no staff and does not provide routine human review of the owner’s Google data.

How information is stored and protected

LifeOps may store source copies, extracted content, derived task and reminder records, identifiers, hashes, processing state, and audit history. Plaintext working data is kept in private, owner-controlled local storage and is excluded from the public website and public source control.

Raw source evidence selected for archive is client-side encrypted before it is placed in the owner’s OneDrive sync location. Canonical LifeOps records placed in Git are also client-side encrypted with opaque filenames. Local search and scheduling indexes are rebuildable and are not treated as the authoritative source of personal data. Encryption keys and Google credentials are kept outside those archives and are never published on this website.

Retention and deletion

LifeOps currently has no automatic fixed retention period for Google-derived source evidence or audit records. Information may remain in owner-controlled local storage and encrypted archives so that decisions can be explained, corrected, replayed, and recovered. Completing a task or deleting the original item from Google does not automatically delete the corresponding LifeOps evidence.

LifeOps does not currently provide an automated user-facing deletion workflow. Deletion is performed manually by the owner and can require separate removal of local evidence, derived records and indexes, encrypted archive objects, version history, and backup copies. Backup or versioned copies may remain until their applicable history is intentionally retired or rendered unrecoverable.

Revoking Google authorization stops future access but does not, by itself, delete information that was previously stored by LifeOps.

Authorization and your choices

The owner controls whether LifeOps may access Google data and can revoke access at any time from the Google Account permissions page. After revocation, LifeOps cannot retrieve new Gmail or Calendar information unless the owner authorizes it again.

Because LifeOps is a single-user system, the owner directly controls its local data and service configuration. Questions about access, correction, or deletion can be sent using the contact information below.

Google API Services User Data Policy

LifeOps’s 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.

This public website

This informational website has no account system, forms, database, analytics, advertising, or tracking cookies. It does not collect Gmail, Calendar, or other LifeOps data.

Contact and policy updates

Privacy questions can be sent to the LifeOps owner at erick.thompson@gmail.com.

This policy will be updated if LifeOps materially changes how it accesses, uses, stores, or shares Google user data. The effective date above identifies the current version.