Privacy Policy
Effective September 12, 2026
Overview
LIFE OS Gmail is a personal-use automation operated by Jim Markunas. It is used only by the account owner and is not offered as a public multi-user service.
This policy explains how LIFE OS Gmail accesses, uses, stores, and protects Google account data when the account owner authorizes Gmail access.
Google data accessed
The Gmail acquisition process uses the Gmail API to enumerate messages within a bounded time window and retrieve message metadata. The current implementation requests the gmail.modify OAuth scope, but the acquisition workflow itself performs read/list requests only.
- Immutable Gmail message ID
- Thread ID, when available
- Sender / From header
- Subject
- Received timestamp
- Mailbox search/list results needed to establish a complete bounded census
What LIFE OS Gmail does not do
- It does not persist full Gmail message bodies as part of the Gmail acquisition process.
- It does not archive, delete, move, label, mark messages read or unread, or send mail through the Gmail acquisition workflow.
- It does not sell Google user data or use it for advertising.
- It does not make Google user data available to unrelated third parties.
How data is used
Authorized Gmail metadata is used only to operate the account owner's LIFE OS personal automation, including identifying, reconciling, and routing relevant inbound information for the account owner's own workflows.
Data may be processed by infrastructure providers required to operate LIFE OS, such as Google, GitHub Actions, and AI services deliberately selected by the account owner. It is not used for advertising, resale, credit decisions, or unrelated profiling.
Storage and retention
OAuth credentials are stored as encrypted GitHub Actions secrets and are not committed to the public source repository.
The current Gmail acquisition workflow writes metadata-only output to a GitHub Actions artifact configured with one-day retention. Raw Gmail message bodies are not persisted by this acquisition process.
Derived records may be retained when the account owner intentionally promotes information into another LIFE OS system of record. Those derived records are governed by the relevant destination system and are not a substitute copy of the Gmail mailbox.
Security and access
Access is limited to the account owner and the automation infrastructure required to run LIFE OS. Credentials and refresh tokens are treated as secrets and should be rotated or revoked if exposure is suspected.
The account owner can revoke the application's Google Account access at any time through Google Account security settings.
Google API Services User Data Policy
LIFE OS Gmail's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Changes to this policy
This policy may be updated when the application's data access or processing behavior materially changes. The effective date above will be updated when substantive changes are made.
Contact
Questions about this policy or LIFE OS Gmail may be sent to jim@jimmarkunas.com.