About Keeper.sh
Keeper.sh stops your calendars double-booking each other. Rida F'kih built it for his own four calendars, and still writes and maintains it.
Who builds Keeper.sh
Rida F'kih writes and maintains Keeper.sh, and holds the copyright on it.
He also writes the posts on the blog, where the comparisons and the provider guides live. You can find him on GitHub and at rida.dev.
Why Keeper.sh exists
It started with four calendars: two on Google, one on Fastmail and one on iCloud. Anyone trying to book time saw a different, incomplete week. Meetings kept landing on top of each other.
Keeper.sh blocks the same time on every calendar and hides the event details by default.
How Keeper.sh puts the same busy time on every calendar is set out in how to stop double-booking across calendars.
Where Keeper.sh is operated and how data is deleted
Keeper.sh is operated from Alberta, Canada.
Deleting your account deletes all of its data within 30 days, apart from what the law or a legitimate business purpose, such as fraud prevention, requires Keeper.sh to keep. The privacy policy has the full terms.
Where the code lives
The service at keeper.sh runs the code in its public repository, which is licensed under AGPL-3.0.
How to report a bug or ask a question
File bugs and feature requests as issues on GitHub. They are triaged in public. For anything else, email [email protected].
Ready to stop double-booking?
Free covers 2 calendar accounts and 3 connections. Pro is $5 a month or $45 a year for unlimited calendars.