Calendar Sync privacy policy
How this personal calendar synchronization utility handles data.
Last updated: 10 October 2026.
Calendar Sync is a personal utility maintained by Alexander Reeves. It runs locally on his Mac using vdirsyncer to synchronize a configured iCloud calendar and Google Calendar. This policy applies to that utility.
Data accessed and its purpose
The utility accesses calendar identifiers and names to discover and select calendars. For the selected calendars, it processes event data such as titles, descriptions, locations, start and end times, time zones, recurrence rules, reminders, and organizer or attendee details when included in an event.
Google’s calendar permission is broader than access to a single calendar. The utility’s configuration limits synchronization to the selected calendar pair. It reads, creates, updates and deletes events to keep that pair in sync. Calendar data is not used for advertising, profiling, sale, or training AI models.
Transfers and sharing
Synchronization transfers event data from Google Calendar to Apple iCloud and from iCloud to Google Calendar over HTTPS. People who already have access to either selected calendar may see synchronized events according to that calendar’s sharing settings. The utility does not change those settings.
Calendar data is not sent to this website, GitHub Pages, or a separate hosted synchronization service. Google and Apple process the data stored in their services under their own privacy policies.
Local storage and security
Google authorization tokens and client configuration are stored locally in files restricted to the operating-system user. The Apple app-specific password is stored in macOS Keychain. Local synchronization state, operational logs and any calendar backups may contain calendar identifiers or event information. These files are kept in a private local directory and are not published to the website or its source repository.
Retention, stopping access and deletion
Data in Google Calendar and iCloud remains until it is deleted from those services. While synchronization is enabled, deleting an event from one paired calendar can also delete its counterpart. Local synchronization state and backups remain until the owner removes them; operational logs rotate with configured size limits.
To stop synchronization, disable the local background job. Google access can be revoked through Google Account connections, and the Apple app-specific password can be revoked through Apple Account settings. Revoking access does not delete events already copied to either calendar. Local credentials, state, logs and backups can be removed after stopping the job.
Google API user data
Calendar Sync’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.
This informational website
These pages are hosted on GitHub Pages and inherit the personal website’s Google Analytics integration. Visiting a page can involve processing browser, network and page-usage information by those providers. No calendar contents or sync credentials are supplied to the website or its analytics integration by the utility.
Contact and changes
For questions about data handling or deletion, contact alexcharlesreeves@gmail.com. Changes to this policy will be posted here with an updated date.