Get Busy

Privacy Policy

Last updated September 16, 2026

Get Busy marks you Busy on your other calendars so you stop getting double-booked. This version connects Google Calendar. Busy blocks we write are private. This policy states what Google user data we access, with whom it is shared, transferred, or disclosed, and how we protect it.

Google user data we access

Get Busy accesses the following Google user data. We do not collect your Google name or profile photo.

  • Email and Google account id, used to sign you in.
  • Your calendar list and calendar names, so you can pick source calendars and a Busy destination.
  • On source calendars, event start and end times (Busy/free). We do not use, store, or copy event titles, descriptions, attendees, or locations.
  • On the Busy calendar, we create, update, and delete only Busy blocks Get Busy created. We do not change your other events.

We store your email and Google account ids for sign-in; encrypted OAuth tokens; calendars you connect; source and target sync rules; and Busy event mappings (ids and times).

How we use Google user data

We use email and Google account id for sign-in. We use calendar names so you can choose sources and a Busy destination. We use source event start and end times to write matching Busy blocks on the destination calendar. Google user data is not used for advertising and is not used to train AI or machine-learning models.

Sharing, transfer, and disclosure of Google user data

We do not sell Google user data. We do not share, transfer, or disclose Google user data to other companies except infrastructure processors that host the app (for example Railway and the database). Calendar contents are not sent to anyone else.

How we protect Google user data

Calendar data is sensitive. We protect Google user data as follows:

  • HTTPS in transit.
  • OAuth tokens encrypted at rest.
  • Only the sync worker uses Calendar access to read times and write Busy blocks.
  • Busy blocks are private and do not copy event details from source calendars.
  • Disconnect or sign-out deletes stored calendars, rules, mappings, and tokens.

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. You can revoke Get Busy in your Google account permissions.

Contact

Questions about this policy: support@treeheat.net.