Privacy Policy

Last updated: September 2, 2026

Local calendar access

MeetMac reads calendar events already stored on your Mac, through Apple’s EventKit framework, in order to display them in the menu bar. This data never leaves your device — no network request is made for local calendars.

macOS asks for full calendar access because that is the only calendar permission it offers, but MeetMac only ever reads your events — it never creates, modifies, or deletes them.

Optional Google and Yandex account linking

You may optionally connect a Google Calendar or Yandex Calendar account. This connection:

is read-only — MeetMac only reads events; it never creates, modifies, or deletes them. For Google, this is additionally enforced by the read-only permission scope MeetMac requests;
is used solely to display your meetings in the menu bar and let you join them;
stores access credentials (Google’s OAuth token or a Yandex app-specific password) only in the macOS Keychain, on your own device.
also reads the account’s email address, solely to show you which account is connected. This address is stored locally in the app’s own settings on your Mac, and is never transmitted anywhere by MeetMac.

MeetMac’s developer does not operate a server, and does not collect, store, or have access to your calendar data, credentials, or account information.

MeetMac does not share, transfer, sell, rent, or otherwise disclose Google user data to anyone. There is no third party that receives it.

This covers every piece of Google user data MeetMac touches — your calendar events, the email address of the connected Google account, and the OAuth token itself:

No servers, no service providers. MeetMac has no backend of its own, and uses no hosting, analytics, advertising, crash-reporting, or other third-party service that this data could be sent to. There are no subprocessors, affiliates, or partners.
Not even the developer. Google user data stays on your Mac. It travels only between your own device and Google’s own APIs, over a direct connection. The developer of MeetMac cannot see it.
Never used for advertising, sold to data brokers, used to determine creditworthiness or for lending purposes, or used to train generalized artificial-intelligence or machine-learning models.
Never read by a human. MeetMac does not transfer this data to anyone who could read it. The only situations in which the Google API Services User Data Policy would permit such a disclosure — your explicit consent, security investigations, or a legal requirement — cannot arise here, because neither the developer nor any third party ever holds a copy of the data.

If this ever changes, this policy will be updated and your consent will be requested before any new use of the data.

Data retention and removal

Because MeetMac stores everything locally on your Mac, you remain in control of your data at all times:

Disconnecting an account from MeetMac’s settings immediately deletes its stored credentials from the macOS Keychain, and revokes MeetMac’s access token with the provider.
Calendar events are never written to disk — they are held in memory only while the app is running, and are gone when you quit it.
Deleting the app removes all of its local data.

MeetMac’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Analytics and tracking

MeetMac does not use analytics, tracking, or crash reporting of any kind.

Contact