Calendar Availability Sync
Privacy Policy
Effective October 29, 2026 (Pacific Time)
Calendar Availability Sync is a personal-use Windows companion operated by its installation owner. This policy describes the companion and this informational website. The website does not operate a hosted or multi-tenant calendar synchronization service.
Information the companion accesses
For setup, the companion lists calendars accessible to the authorized Google account, including their names, identifiers and access roles. It uses configured calendar identifiers, event identifiers, dates, start/end times, time zones, availability, relevant attendance or declined status, synchronization markers and provider version metadata to reconcile busy time.
The Google authorization requests these scopes:
https://www.googleapis.com/auth/calendar.events: read calendar availability and create, update or remove the application's own blocks.https://www.googleapis.com/auth/calendar.calendarlist.readonly: list accessible calendars so the owner can select sources and a destination.
Google's event permission is broader than an application-only event permission. The companion enforces the restriction to its own marked blocks in its application logic; the Google permission itself is not restricted to those blocks.
How information is used and transferred
Selected personal Google busy intervals are represented on the configured Outlook calendar as private busy appointments named Personal commitment. Original work busy intervals are represented on one selected Google calendar as private busy events named Work.
Source event subjects, descriptions, locations, participants, attachments and meeting links are not copied between providers. No invitations are sent and reminders are disabled on generated blocks. Original source events are not modified.
Calendar processing runs on the owner's Windows device. Requests go to Google Calendar and to the mailbox services used by the already signed-in Outlook application. Google and the mailbox provider process the data stored in their respective calendars under their own policies and the owner's sharing and account settings.
The application does not sell calendar information, use it for advertising, or use Google user data to train generalized AI or machine-learning models. Calendar Availability Sync's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Local storage and safeguards
The companion's saved Google OAuth client credentials and tokens are encrypted using Windows current-user Data Protection API (DPAPI), tied to the Windows account and machine. Other local configuration and operational state can include selected calendar identifiers, the Outlook store pin, ownership markers, pending-deletion state, health timestamps, counts and safe error codes. Source event contents are not intentionally written to operational logs.
Complete bounded provider snapshots are required before applying changes. The companion checks ownership and provider versions, confirms removals across successful cycles, and stops for unexpected or excessive deletions rather than treating a failed read as an empty calendar. These safeguards cannot guarantee uninterrupted or error-free service.
Retention and your controls
Google authorization and local credentials remain until revoked or removed. Configuration and health/state files remain on the device until removed by its owner. The application does not keep a central server-side copy of calendar records.
Generated blocks are events stored in the destination calendars. They remain until removed there; stopping, uninstalling or revoking authorization does not automatically erase previously created blocks. The rolling synchronization window does not sweep old historical blocks outside that window.
Stop the companion before changing calendars or authorization. The owner can review a dry-run, change configuration, manage the application's own blocks, and revoke access in Google Account connections. Revoking access prevents further Google synchronization but does not remove existing destination events. Clean up only the application's blocks, never unrelated originals.
Private flags are not encryption against account administrators or delegates who have permission to view private items. Neutral event names reduce the information exposed.
This website
The informational pages are delivered by Cloudflare Pages. Cloudflare may process ordinary HTTP request information, such as IP addresses and browser headers, for delivery, security and operations under its Privacy Policy. Calendar data, Google authorization tokens and Outlook credentials are not sent to this website.
These pages do not contain application signup forms, advertising, third-party analytics or externally loaded fonts. The pages do not set application cookies or use browser storage; a small local script selects a light or dark display theme. The hosting provider may apply its own security mechanisms.
Questions and changes
For questions about an installation or data removal, contact the installation owner using the support email shown on that application's Google consent screen. No calendar data or credentials should be sent to this website. Material changes to this policy will be reflected here with an updated effective date.