Data practices

Privacy policy

Last updated September 26, 2026

CalendarAgent is a personal calendar synchronization and planning tool operated by Jake Metz. This policy covers the application and its informational website at apps.jakemetz.com.

Information accessed

With account authorization, CalendarAgent reads calendar information from Google Calendar or Microsoft Outlook. This can include calendar identifiers and time zones; event titles, descriptions, start and end times, locations, organizers, attendees and their email addresses, RSVP and availability status, recurrence information, meeting links, and other event fields returned by the provider. The application stores normalized fields and the raw event response.

Google authorization requests read-only calendar access and basic account identity through OpenID Connect, email, and profile permissions. The application uses the provider's account identifier to associate events with the correct account. It processes OAuth access and refresh tokens to retrieve updates without requiring a login for every sync. It does not collect your Google or Microsoft password.

How information is used

Information is used to maintain a private schedule collection, show event timing and availability, distinguish calendar sources, and produce structured exports for personal planning. CalendarAgent does not modify events in the source calendars. It does not request Gmail, Google Drive, or calendar-write access for these functions.

Storage and protection

Calendar data is stored in an operator-controlled database, with local SQLite as the default. A separately configured PostgreSQL database, exports, or backups may hold additional copies. OAuth tokens are stored separately in local files with restricted filesystem permissions and atomic replacement. These measures are not a claim that every database, export, or backup is encrypted at rest.

The public website is separate from the collector and its private calendar viewer. Calendar databases, event exports, account credentials, and OAuth tokens are not published to this website.

Sharing and connected services

CalendarAgent does not sell personal data or use it for advertising, profiling for advertising, or training generalized AI or machine-learning models. It does not automatically publish calendar data or send it to the website host.

The operator may explicitly run an export or configure an optional Notion integration to copy selected event information into a chosen Notion database for schedule display and planning. Such copies are governed by that service's privacy practices and the operator's sharing settings. These actions are separate from routine calendar synchronization; recipients and destinations should be reviewed before use. Other downstream sharing is not enabled by this informational website.

Use and transfer of information received from Google APIs must follow the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used only for the personal calendar and planning purposes disclosed here.

Retention and deletion

Imported records are retained until the operator removes them. Events removed from a source calendar may be marked deleted locally rather than physically erased. There is no automatic retention deadline. Exports, backups, and optional Notion copies may persist separately.

You can revoke Google access in your Google Account connections, or revoke Microsoft access through the applicable account or organization controls. Revocation prevents further authorized access once existing access tokens cease to be valid; it does not erase existing copies.

To request removal of imported information or ask about data handling, contact jake.metz@gmail.com. Removal requires addressing the database, token files when disconnecting an account, exports, backups, and any configured external copies. A backup must not be restored in a way that reintroduces data requested for deletion.

Website visitors

This informational site has no sign-in, forms, advertising, embedded third-party media, or application analytics scripts. Its hosting provider, Cloudflare, may process technical request information such as IP addresses and browser details to deliver and protect the site, under Cloudflare's privacy policy. Provider-level security features may also apply.

Changes and contact

This page will be updated when data practices change. New uses of account data require appropriate notice and authorization before they begin. Questions can be sent to Jake Metz at jake.metz@gmail.com.