Lifestream Calendar Capture

Privacy policy

Last updated 15 September 2026

Lifestream is a personal record operated for its owner. This policy explains the Google Calendar connection and this public information website.

What Calendar Capture accesses

After authorization, Calendar Capture uses Google's read-only Calendar permission to retrieve events from calendars selected in the owner's configuration. The permission can cover calendars the connected account has access to, including shared calendars.

Retrieved event data can include titles, descriptions, dates and times, locations, attendee and organizer details, recurrence rules, reminders, attachments' metadata or links, and event status. API responses may contain additional metadata supplied by Google. Capturing an attachment link does not download its file contents.

The app also holds the account identifier, calendar identifiers, synchronization tokens, and OAuth credentials needed to maintain the connection. It does not receive the Google account password.

How the data is used

Calendar records are preserved in the private Lifestream and used to assemble timelines and daily views. The owner can compare plans with other observations, revisit past events, and ask questions about their own record. Calendar Capture does not create, modify, or delete events in Google Calendar.

AI features and other processing

When the owner enables AI features, selected calendar information and related context may be sent to the AI providers configured by the owner to generate personal summaries or answers. Those providers receive the information included in the selected task and process it under their applicable service terms. Capture and local record storage do not themselves require an AI call.

Lifestream does not sell Google user data, use it for advertising, or use it to train general-purpose AI or machine-learning models. Google data is used for the personal features described here. Human access is limited to the owner or people the owner explicitly authorizes, except where needed for security or required by law.

Lifestream's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Where data is stored

Calendar responses, records, and derived interpretations are stored on infrastructure controlled by the owner. The current setup uses local files and databases. The owner may retain backups and explicitly export records. Google OAuth credentials are stored separately from observations, using the system credential store in the current Mac setup.

Connections to Google use HTTPS. Access to retained files depends on the protections applied to the owner's devices, storage, and backups. Calendar records are not published by this website.

Retention and deletion

Lifestream is designed as a lasting record. Captured observations and their history are retained until the owner explicitly removes them; there is no automatic expiration period. Updating or deleting an event in Google Calendar does not necessarily remove an earlier captured copy.

To stop future access, remove Lifestream Calendar Capture from your Google account's third-party connections and disable its capture configuration. Revoking access does not delete records already captured. To remove those records, the owner must remove the relevant stored data, derived outputs, exports, and retained backup copies.

This public website

This website contains information about the project. It has no account system, forms, advertising, or application analytics scripts. Cloudflare hosts and serves these pages and may process standard request information, such as IP addresses, browser information, and requested URLs, to deliver and protect the website. See Cloudflare's privacy policy.

Contact and changes

For questions about Calendar Capture or a retained record, contact the operator using the user-support email shown on the Google authorization screen. This installation is operated for its owner and does not offer public sign-ups.

Changes to these practices will be reflected on this page. A new purpose or broader access to Google data will require an updated disclosure and consent before it is used.