← Back

Privacy Policy

Last updated: June 16, 2026

Overview

Calendar OS is a private personal tool used by a single operator to aggregate multiple Google Calendar accounts in one view, detect scheduling conflicts, and create private “Busy” blocker events across connected calendars to avoid double booking.

Data we access

When a user connects a Google account, the app uses the Google Calendar API to read calendar metadata and event time ranges, and to create, update, and delete its own “Busy” blocker events. The app stores the minimum data required for sync (account identifiers, calendar IDs, event IDs, start/end times, sync tokens, and OAuth refresh tokens) in a secured backend.

How we use data

  • Display events from connected calendars in a unified view.
  • Detect overlapping events across calendars.
  • Create, update, and delete private “Busy” blocker events on selected target calendars. Blockers contain only the title “Busy” — event titles, descriptions, attendees, and locations are never copied.

What we do not do

  • We do not sell, share, or transfer Google user data to third parties.
  • We do not use Google user data for advertising.
  • We do not use Google user data to train AI or ML models.
  • We do not copy event descriptions, attendees, or locations into Busy blockers.

Storage and security

Data is stored in a managed Postgres database with row-level security so that each user can only access their own records. OAuth tokens are stored server-side and used only to call the Google Calendar API on the user's behalf. Access is restricted to the account owner.

Revoking access and deletion

Users can revoke the app's access at any time from their Google Account permissions page. Disconnecting an account from within the app removes its tokens and cached events. Account deletion removes all associated data.

Google API Services User Data Policy

Calendar OS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

For any privacy question, contact the account owner through the email address associated with this deployment.