Connect Google Calendar by signing in

· v1.11.5

Reading a Google calendar meant finding its secret iCal address and pasting it in — a link that is awkward to locate, easy to leak, and impossible to revoke without regenerating it. You can now connect the account itself and pick which of its calendars Keeper.sh reads.

Signing in also means Keeper.sh knows what it is looking at. It lists the calendars on the account by name, so choosing between a personal calendar and one shared with you is a matter of ticking the right box rather than working out which link belongs to which.

A calendar can now be both a source and a destination without feeding itself. Keeper.sh recognises the events it created and skips them on the way back in, so pointing two accounts at each other produces one copy in each direction instead of a loop that grows on every run.

Read more about everything Keeper.sh does.

New

  • When you add a Google source you can uncheck Focus Time, Out of Office and Working Location, so those blocks stay out of your other calendars.

  • Visitors in the EU, EEA and UK are asked whether Keeper.sh may use cookies for analytics, with a link to the privacy policy.

Improved

  • Adding a Google or Outlook calendar as a source starts a sync straight away, rather than waiting for the next scheduled run.

Fixed

  • A Google or Outlook account that stops accepting Keeper.sh is marked as needing to be reconnected, instead of failing quietly.

  • Events Keeper.sh left on a calendar that no longer match anything in your sources are removed, not just the ones in the past.

  • An event with no description no longer stops Outlook syncing in either direction.

  • A sync that runs into a problem ends the run, instead of showing progress that never finishes.

  • Deleting your account only asks for a password when your account actually has one.

Can Keeper.sh use cookies for analytics?