Privacy policy
Effective November 18, 2026
cal-sync (https://cal.trackinfleet.com) copies events from one Google Calendar into another as “busy” blocks, so people who can only see the second calendar know when you are unavailable. This policy explains what information cal-sync accesses, how it is used, and how to remove it.
Information we access
- Your Google sign-in profile (name, email address, profile picture), used only to sign you in. Sign-in is limited to an allow-list of email addresses.
- Source calendars, with read-only access (
calendar.readonlyandcalendar.calendarlist.readonly): the list of your calendars so you can choose one, and the events on the calendar you choose. - Destination calendar, with read and write access (
calendar): to list your calendars, optionally create a calendar for the copies, and create, update and delete the copied events.
How we use it
For each upcoming event on a source calendar, cal-sync creates a matching event on the destination calendar containing only the event title (with a prefix you choose), its start and end time, and its recurrence rule, marked as busy. Descriptions, attendees, locations, attachments and conference links are never copied. All-day events, events you declined and events marked private are skipped. When a source event changes or is deleted, its copy is updated or deleted to match.
Google data is used only to provide this feature. It is not used for advertising, not sold, not used to train AI or machine-learning models, and not read by people except when you ask for help with a problem or when required by law.
Google API Services User Data Policy
cal-sync's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What we store
- Your account record: name, email address and profile picture URL.
- For each connected Google account: its email address and the OAuth tokens that let cal-sync act on your behalf. Tokens are encrypted (AES-256-GCM) before they are stored.
- Your sync settings: which calendars are paired, the title prefix, and sync status.
- Identifiers linking each source event to its copy, and Google notification channel details. Event titles, times and other event content are not stored; they pass through memory while a copy is written.
Where it is stored and who can see it
Data is stored in a database on a server rented from Vultr and is not reachable from the internet. Encrypted database backups are kept in Cloudflare R2. Both providers store the data only on our behalf. The data is not shared with or transferred to anyone else, except where required by law.
Retention and deletion
- Deleting a sync pair in cal-sync removes its copied events from the destination calendar, then its settings and event links.
- You can revoke cal-sync's access at any time at myaccount.google.com/permissions. Syncing stops immediately.
- To have all of your data deleted, email fran.jlp26@gmail.com. It is deleted within 30 days. Backups expire on their own within 400 days.
Security
All traffic uses HTTPS. OAuth tokens are encrypted at rest, the database is reachable only from the application, and backups are encrypted before they leave the server.
Changes
If this policy changes, the new version is posted here with a new effective date.
Contact
Questions or requests: fran.jlp26@gmail.com.