ReadyEddy Privacy

Where ReadyEddy reads your calendar — and where the data goes (it doesn’t).

TODO (Phase 2): finalize the privacy page once the v0.1 app behavior is locked. The short version below is the spine; expand each section with the engineering specifics (EventKit entitlement key, exact Sparkle URL, exact permission strings shown to the user) when those are settled in the app repo.

The short version

ReadyEddy reads your calendar locally through Apple’s EventKit. Nothing leaves your Mac.
No backend. ReadyEddy has no server to send anything to.
No analytics, no telemetry, no third-party SDKs.
No account. Nothing to sign up for, nothing to log out of.
The only network call in the default configuration is Sparkle’s daily check for app updates.

Calendar data

ReadyEddy uses Apple’s EventKit framework to read your calendar events. EventKit is the same API Calendar.app uses, so ReadyEddy sees the same events from the same sources you’ve added to your Mac (iCloud, Google, Exchange, Outlook, etc.) — no separate authentication, no separate sync.

What we read: event title, start time, end time, attached URL, location, notes, and a few flags (declined, all-day, focus-time) so ReadyEddy can decide whether to fetch you. What we transmit: nothing. The data is used in-memory on your Mac to render the takeover, then discarded.

Permissions ReadyEddy asks for

Calendars — required, requested via requestFullAccessToEvents. You can revoke at any time from System Settings → Privacy & Security.
Notifications — optional. Used to surface a small notification just before the takeover, in case you’ve already left the room.

What we don’t do

No analytics framework. Not Google, not Mixpanel, not anything.
No crash reporting. (Subject to change — if we add Sentry later, it’ll be opt-in and disclosed here first.)
No account system. Nothing to sign up for, nothing to log out of.
No ads, no tracking pixels, no third-party SDKs that phone home.

Updates

ReadyEddy checks for updates by fetching a small XML file from readyeddy.app once a day. The request includes your app version and macOS version (standard browser User-Agent stuff) and nothing else. Updates themselves are EdDSA-signed; the app verifies the signature before applying them. You can turn auto-update checks off in Preferences.

Changes to this page

If we add a feature that changes any of the above, we’ll update this page and call it out in the in-app release notes.

Questions about privacy or security? Email hello@bearandeddy.com.