MeetingNudge · Field manual · PRIV-01

Privacy
Policy

MeetingNudge does not send me your calendar or usage data. It reads events on your Mac through EventKit, stores preferences locally and opens meeting links only when you click Join.

shield

The Short Version

Calendar events and preferences stay on your Mac. The app has no account system, analytics service or backend.

calendar_month

Calendar Data

MeetingNudge requests read-only calendar access through macOS EventKit. It reads upcoming events when it needs to display them and does not make or upload a second copy.

notifications

Notifications

Meeting reminders are delivered as local notifications through macOS. There are no push notification servers involved — notifications are scheduled and triggered entirely on your Mac.

block

No Analytics

There is no analytics or telemetry service in the app. I do not receive usage data, behavioural data or automatic crash reports.

lan

No Third-Party Services

MeetingNudge connects only to your configured calendar accounts (via macOS EventKit) and conference URLs — Zoom, Google Meet, Microsoft Teams, and Webex — when you actively click to join a meeting. There are no SDKs, no ad networks, and no third-party services embedded in the app.

settings

UserDefaults

Your preferences (reminder times, overlay settings, sound choices) are stored locally on your Mac via UserDefaults. This data is never synced, uploaded, or shared with anyone.

person_off

No Account Required

MeetingNudge does not require sign-up or login. It works locally after installation and does not ask for profile information.

hard_drive

Data Storage

All data remains on your Mac. Calendar events are read from the system, preferences are stored in UserDefaults, and notification sounds live in your local Library folder. Nothing leaves your device.

mail

Questions?

If you have any questions about this privacy policy or how MeetingNudge handles your data, get in touch at hello@davebarnes.dev

Last updated: March 2026