Privacy Policy
Get Busy marks you Busy on your other calendars so you are not offered the same time twice. Target events are private Busy blocks. Titles, guests, and locations stay on the source. This version connects Google Calendar. This policy describes what we store and why.
Data we store
We store your Google account profile (name, email, and account identifiers) for sign-in; OAuth access and refresh tokens, encrypted at rest, so we can read source calendars and write Busy blocks; calendar metadata you connect; the source-to-target sync rules you create; and event mappings (source event id, target Busy event id, and times) needed to update or delete mirrored availability.
Data we do not copy
Get Busy does not copy event titles, descriptions, attendees, locations, or conference details onto target calendars. Target events are created as private Busy blocks.
How we use Google Calendar access
We use Google Calendar scopes only to list calendars, watch for changes, read event times on source calendars, and create, update, or delete Busy blocks we created on target calendars.
Retention and deletion
Disconnecting a Google account revokes tokens when possible and deletes stored calendars, sync rules, mappings, and tokens for that account. You can also sign out at any time.
Contact
Questions about this policy: support@treeheat.net.