Gobo Privacy Policy
Effective August 30, 2026
The short version
Gobo collects no data. It has no servers, no accounts, no analytics, and no network code of any kind. Nothing you do in Gobo leaves your Mac.
Calendar data
Gobo requests full calendar access because its sole function is to read events from the calendars you choose and to create, update, and remove its own “Busy” placeholder blocks on a target calendar you choose. All of this happens locally, through Apple's EventKit framework, on your device. The placeholder blocks contain no title, location, notes, or attendee information from your source events — only an anonymous identifier that lets Gobo recognize its own blocks.
Your calendar accounts sync through the providers you have configured in macOS (iCloud, Google, Microsoft Exchange, and so on) under those providers' own policies, exactly as they do with Apple's Calendar app. Gobo adds no service of its own to that path.
What Gobo stores
Your rules and a local activity log are stored inside the app's own sandbox container on your Mac. They are never transmitted anywhere.
Verifiability
Gobo's sync engine is open source under the MPL-2.0 license. You can read it and confirm the absence of any network call at github.com/mfbergmann/gobo-core.
Changes and contact
If this policy ever changes, the change will appear on this page with a new effective date. Questions: gobo@bergmann.ai.