Calendar Busy Sync

Privacy policy

Effective September 21, 2026

This policy explains how Calendar Busy Sync developers (“the operator”) handles information when you use Calendar Busy Sync and this website.

Information accessed

When you connect Google Calendar, the app accesses events on configured calendars, including identifiers, start and end times, time zones, recurrence information, availability status, and attendance responses. Event records can also include titles, descriptions, locations, attendees, organizers, and links. The app uses attendance responses to exclude declined invitations. If you enable viewing feeds, titles, descriptions, locations, times, and event links are included in those feeds.

The app stores OAuth credentials, including refresh tokens, to continue syncing without repeated sign-in. It does not collect your Google password. An optional iCloud connection uses an Apple app-specific password and reads events from the calendar you select.

How information is used

Calendar information is used only to synchronize availability, maintain app-created busy blocks, provide your optional originals-only viewing feeds, and operate or troubleshoot these features. Event timing is copied to your selected destination Google calendars. Original titles, descriptions, locations, attendees, and meeting links are not copied into busy blocks.

Google user data is not sold, used for advertising, used to build advertising profiles, or used to train generalized artificial intelligence or machine-learning models.

Storage and security

The utility processes calendar data on the computer or server where it runs. OAuth tokens, optional iCloud credentials, generated feed files, and operational sync state may be stored there. Busy-block identifiers and ownership metadata are also stored with generated Google events. Credentials and private feeds are not part of this public website.

Access to the sync host and credential files is restricted. Connections to Google and iCloud use HTTPS. Operational logs are intended to record sync counts and errors rather than event contents. No method of storage or transmission can guarantee absolute security.

Sharing and service providers

The app sends data to Google Calendar and, when configured, reads from Apple iCloud to provide the requested functionality. Your calendar sharing settings determine who can see destination busy blocks. Anyone you give access to a private viewing feed may see its included event details.

Hosting providers process data needed to operate the sync host or serve the website. Cloudflare hosts this public website and may process ordinary request metadata such as IP address, browser information, and request time for delivery and security. This website has no advertising, analytics scripts, sign-in forms, or calendar-data collection.

Human access to Google user data is limited to access you expressly authorize for specific data, necessary security or abuse investigations, or compliance with applicable law. Data is not otherwise shared with unrelated third parties.

Retention and deletion

Credentials are retained while the connection is configured. Generated feeds are replaced as synchronization runs and contain only the configured coverage window. Sync metadata and operational records may remain until the operator removes them. Existing calendar originals remain with their calendar provider.

You can revoke Google access at Google Account connections and revoke an Apple app-specific password in your Apple Account. Revocation stops future authorized access; it does not automatically erase stored files or existing busy blocks. Contact calendar-busy-sync@nw9a.slmail.me to request removal of credentials, feed files, sync records, and app-created blocks. After access is revoked, you may need to remove remaining blocks in Google Calendar yourself.

Google API Limited Use

The app’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Changes and contact

Updates will be posted here with a revised effective date. New uses of Google user data will be disclosed and consent obtained when required before those uses begin. For questions or privacy requests, contact Calendar Busy Sync developers at calendar-busy-sync@nw9a.slmail.me.