Telerad Calendar Sync

Policy

Privacy Policy

Effective April 20, 2026. This policy explains what Telerad Calendar Sync accesses, why it accesses that data, and how the app handles local storage 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 and sale of data

The app is not designed to sell user data. Google Calendar operations are intended to happen directly between the desktop app and Google APIs.

If the project introduces hosted services in the future, this policy should be updated before those production data flows are used.

07

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 stop using the app at any time.