Telerad Calendar Sync

Policy

Privacy Policy

Effective April 23, 2026. This policy explains what Telerad Calendar Sync accesses, why it accesses that data, and how the app handles local storage, sharing, protection, retention, and deletion for schedule and calendar sync behavior.

01

Overview

Telerad Calendar Sync is a desktop application that reads schedule spreadsheets, generates a preview of proposed calendar updates, and syncs approved managed events to Google Calendar or Apple Calendar.

The app is designed to perform sync work locally on the user’s device. Google authorization occurs through Google’s browser-based desktop OAuth flow.

02

Data the app accesses

  • Schedule workbook data from files the user chooses locally.
  • Google Calendar metadata and events needed to preview and apply sync changes.
  • Basic Google account identity details associated with the selected calendar connection.
  • Local preferences such as selected calendar and color settings.

03

Google Calendar scopes

When a user chooses Google Calendar, the app requests these Google scopes:

  • https://www.googleapis.com/auth/calendar.events to create, update, and delete managed events generated by the app.
  • https://www.googleapis.com/auth/calendar.calendarlist to list writable calendars and update list-level calendar color settings.
  • https://www.googleapis.com/auth/calendar.calendars to create a destination calendar when the user explicitly requests it.

The app does not request broader Google account permissions unrelated to calendar sync.

04

How data is used

  • To parse the user’s schedule file and identify shifts for the selected doctor.
  • To preview the calendar diff before the user applies changes.
  • To create, update, and remove only the managed events required for the approved sync.
  • To remember local app state needed for subsequent runs.

05

Local storage

After Google authorization, OAuth token data is stored locally in the app’s data directory rather than inside the signed app bundle.

  • macOS: ~/Library/Application Support/TeleradCalSync
  • Windows: %APPDATA%\TeleradCalSync

The app may also store local configuration and provider-specific metadata needed for sync behavior.

06

Sharing, transfer, and disclosure

Telerad Calendar Sync does not sell, rent, or transfer Google user data. The app does not disclose Google user data to third parties for advertising, marketing, analytics resale, or AI/ML model training.

Google Calendar data is exchanged directly between the locally installed desktop app and Google APIs for the user-approved sync features described in this policy. The app may disclose data only when the user directs the app to write approved events to the selected calendar, when required by law, or when necessary to protect the security or integrity of the app.

07

Data protection

  • Google authorization uses Google's OAuth desktop-app flow.
  • Calendar API requests are sent over HTTPS to Google APIs.
  • OAuth token data is stored locally in the user's app-data directory, not in the signed app bundle.
  • The app can optionally talk to a hosted LAN sync service that stores per-user Google token data and publishes Apple ICS feeds when that deployment model is enabled.
  • Users should protect their local computer account because local schedule files and token data remain on that device.

08

Retention and deletion

Google OAuth token data is retained locally until the user disconnects, switches accounts, deletes the app's local data, or uninstalls the app. Local configuration and sync metadata are kept only as long as needed for the app to remember user preferences and reconcile managed calendar events.

Schedule spreadsheets remain in the location chosen by the user unless the user chooses an app workflow that archives a processed file locally. The app does not upload schedule spreadsheets to a project server.

Calendar events created in Google Calendar remain in the user's selected Google Calendar until the user deletes them or the app removes managed events as part of a later user-approved sync. Users may also revoke the app's Google access from their Google Account permissions page.

09

User control

  • Users choose whether to connect Google Calendar.
  • Users can review changes before the app writes them.
  • Users can disconnect by removing the locally stored token data.
  • Users can revoke Google OAuth access from their Google Account security settings.
  • Users can stop using the app at any time.