Overview
Calendarr is a Windows application from TnUC Creations that syncs upcoming movie and TV release dates from your Radarr and Sonarr instances into your Google Calendar. This policy explains how Calendarr accesses, uses, stores, protects, shares, retains, and deletes Google user data.
Google OAuth Scope Requested
Calendarr connects to Google Calendar using OAuth 2.0. Calendarr requests the Google Calendar events permission, https://www.googleapis.com/auth/calendar.events, so it can create and update calendar events on your behalf.
This scope may allow access to Google Calendar event data needed to create, view, edit, or delete events. Calendarr uses this access only for the calendar sync features described in this policy.
Data Accessed
Calendarr accesses only the data needed to sync Radarr and Sonarr release dates with Google Calendar:
- Google OAuth tokens that allow Calendarr to keep syncing calendar events after you authorize the app.
- Google Calendar event data required to create, update, match, or remove Calendarr-managed release-date events.
- Event fields such as event title, description, start date, end date, and metadata needed to identify events created by Calendarr.
- Release-date information from your Radarr and Sonarr instances, including movie or series titles and release dates you choose to sync.
Calendarr does not request access to your Google profile, Gmail, Drive, Contacts, or any Google service other than Google Calendar events. Calendarr does not collect your Google account name, email address, or profile information for TnUC Creations.
Data Usage
Calendarr uses Google user data only to provide the user-facing calendar sync feature:
- To create Google Calendar events for upcoming movie and TV release dates from your configured Radarr and Sonarr instances.
- To update Calendarr-created events when release dates, titles, or related sync details change.
- To identify events previously created by Calendarr so duplicate events are avoided and stale Calendarr-managed events can be updated or removed.
- To maintain authorized access to Google Calendar until you revoke access or delete the local token.
Calendarr does not use Google user data for advertising, analytics, profiling, credit decisions, training AI models, or any unrelated purpose.
Data Sharing
Calendarr does not sell, rent, transfer, or share Google user data with advertising platforms, data brokers, information resellers, or other third parties.
Calendarr communicates only with the services needed to operate the app:
- Your Radarr and Sonarr instances, which you configure.
- Google Calendar API, to create and update calendar events after you grant permission.
- GitHub Releases API, to check for application updates. Google user data is not sent to GitHub for update checks.
TnUC Creations does not receive copies of your Google Calendar events or OAuth tokens from Calendarr. Human access to Google user data by TnUC Creations is not part of Calendarr's normal operation.
Data Storage & Protection
Calendarr stores its configuration on your own Windows machine. The OAuth refresh token issued by Google is stored locally in the Calendarr configuration file, such as config.json. This token is used by Calendarr to continue syncing events after you authorize the app.
Calendarr does not transmit OAuth tokens, Google Calendar event data, Radarr data, or Sonarr data to TnUC Creations servers. Data remains on your machine except for requests sent directly between your machine and the services you configure, including Google Calendar API, Radarr, Sonarr, and GitHub Releases API.
You are responsible for securing the Windows account, device, and files where Calendarr is installed. We recommend using operating system account protections, disk encryption where available, and limiting file access to trusted users.
Data Retention & Deletion
Google OAuth tokens and Calendarr configuration data are retained locally on your machine until you remove them. Calendarr-managed Google Calendar events remain in your Google Calendar until Calendarr removes them, you delete them, or you revoke access and manage them directly in Google Calendar.
You can delete or revoke Calendarr's access to Google user data at any time by:
- Revoking Calendarr's access in your Google Account third-party access settings.
- Deleting Calendarr's local configuration file, such as
config.json, from your machine to remove locally stored OAuth tokens and app settings. - Deleting Calendarr-created events directly from Google Calendar if you no longer want those events.
Because Calendarr stores Google user data locally on your machine and does not send it to TnUC Creations servers, TnUC Creations does not maintain a separate server-side copy to delete. If you need help locating local Calendarr configuration data, contact us using the information below.
Limited Use Disclosure
Calendarr's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
No Tracking or Analytics
Calendarr does not collect usage data, crash reports, analytics, telemetry, or advertising identifiers. There are no third-party tracking libraries included in the application.
Contact
Questions about this policy or requests for help deleting local Calendarr data can be raised via GitHub Issues.