Privacy Policy

Effective September 22, 2026

TimeTug is a macOS app made by an individual developer, Scott O'Bryan, not a company. Your calendar data is processed entirely on your Mac: TimeTug reads it locally, shows it to you locally, and stores it locally. No server we operate ever receives, stores, or processes your calendar data. Where TimeTug reads a calendar, your Mac talks directly to that service (Apple's or Google's), not to us.

What TimeTug reads, and why

• Apple Calendar, via EventKit. If you grant Calendar access, TimeTug reads event titles, times, locations, notes, attendees and conferencing links from the calendars macOS already has configured (iCloud, Google, Exchange, or anything else added in System Settings). This happens locally, through Apple's own framework; TimeTug never sees your Apple ID or iCloud credentials.
• Google Calendar, if you connect an account. TimeTug uses Google's OAuth sign-in and requests two scopes:
  • calendar.events — view and edit events on your calendars, so TimeTug can show them in your agenda and trigger a takeover before they start. TimeTug's current release only reads events; it does not create, edit or delete them.
  • calendar.calendarlist.readonly — see the list of calendars you're subscribed to, so you can choose which ones TimeTug pays attention to.
  Your Mac calls Google's Calendar API directly with a token Google issues to you; the events it returns are shown in TimeTug and never relayed anywhere else. Google Calendar support is in beta while we complete Google's verification review, and access is limited to accounts we've listed as testers until that's done.
• An on-device Apple Intelligence model, only if you turn it on. Settings › Calendars has an opt-in, off-by-default, Beta feature that asks your Mac's own on-device model whether two ambiguous events are the same meeting, to avoid double-tugging you. It requires macOS 26 on a supported Mac, runs entirely on-device, and nothing about your calendar leaves your Mac for this either.

Where things are stored

• Google sign-in tokens are stored in the macOS Keychain, protected by your Mac's own security, and used only to talk to Google's Calendar API on your behalf.
• Local app state — which meetings TimeTug has already shown you, and its duplicate detection memory — lives in plain files under ~/Library/Application Support/TimeTug/ on your Mac. It is used only to decide what to show you next and is never uploaded anywhere.
• None of the above is backed up to, synced through, or readable by any server we run.

What TimeTug does not do

• No analytics, telemetry, or crash reporting of any kind.
• No advertising and no ad or tracking SDKs.
• We do not sell, rent, or share your calendar data with anyone, for any purpose.
• TimeTug does not require a TimeTug account to read or show your calendars.

Software updates

TimeTug checks a public update feed (hosted on GitHub Pages) to see whether a newer version exists. That request carries no calendar data or personal information — it's the same kind of request your browser makes loading any web page, logged the same way GitHub logs any visitor to its pages.

Your controls

• Disconnect Google anytime in TimeTug's Settings › Accounts, or revoke TimeTug's access directly at Google Account › Third-party access. Removing an account also deletes its stored token and cached calendar data from your Mac.
• Turn off Apple Intelligence matching anytime in Settings › Calendars; TimeTug falls back to rules-only matching.
• Remove local data entirely by deleting ~/Library/Application Support/TimeTug/ after quitting TimeTug, or by uninstalling the app, which leaves nothing running or stored anywhere else.

Google API Services User Data Policy

TimeTug's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Children's privacy

TimeTug is not directed at children, and we do not knowingly collect information from anyone under 13.

Changes to this policy

If this policy changes in a way that matters — a new data source, a new third party — the date at the top will change and, for anything material, we'll say what changed here.

Contact

Questions about this policy or your data: darkarena@gmail.com, or open an issue on GitHub.