Private by design.
MeetKeeper is built so your data never has to leave your Mac. This page says exactly what the app touches and what it does with it.
Last updated 6 October 2026
- no accountNothing to sign up for. Download, open, done.
- no cloud copyNo MeetKeeper server holds your calendars. Your events never pass through us.
- no telemetryNo usage statistics or crash reports. The app calls home only to check for updates, or when you send feedback.
What MeetKeeper does with your data
- Calendars on your Mac. With your permission, MeetKeeper reads events through Apple's Calendar framework (EventKit) to display them, and creates the events you add. This data stays in Apple's calendar database on your Mac.
- Google Calendar (optional). If you connect a Google account, MeetKeeper uses the Google Calendar API to read your calendars and events, to create events you add, to invite the people you choose, to reply to invitations and to attach Google Meet links. Access tokens are stored in a file on your Mac that only your user account can read (
~/Library/Application Support/MeetKeeper/). They are never sent anywhere except to Google. - Outlook (optional). If you connect a Microsoft account, MeetKeeper uses Microsoft Graph to read your calendars and events, to create events you add, to invite the people you choose, to reply to invitations and to attach Microsoft Teams links. Access tokens are stored in the same folder, readable only by your user account, and are sent nowhere except to Microsoft.
- Notion (optional). If you connect a Notion integration, MeetKeeper reads pages from the databases you select to show them alongside your events. The integration token is stored the same way.
Payments and licences
MeetKeeper is free to try for 14 days and then sold as a one-time licence. Purchases are handled by Polar (Polar Software, Inc.), our merchant of record.
- At checkout. You pay on Polar's checkout page. Polar collects your name, email address, billing country and payment details to take the payment, handle sales tax or VAT, prevent fraud, and send your receipt and licence key. Your card details go to Polar and its payment partners; we never see or store them.
- What we receive. Polar shares with us the order details we need to support you: your name, email address, country, what you bought, when, and the licence key. We use them only to deliver your licence, answer your emails and handle refunds, and we never use them for marketing without asking.
- In the app. The trial runs on your Mac and needs no account. When you enter a licence key, MeetKeeper sends the key and a label for your Mac to Polar to confirm it is valid, and repeats that check every few days so that refunded or cancelled keys stop working. The label is the Mac's model and a short random code, not your name. Nothing about your calendars is ever part of that check.
- Their policy. Polar processes this data under its own privacy policy and checkout buyer terms. Our refund policy explains refunds.
Feedback you send
Send Feedback, in the MeetKeeper menu and in Settings, lets you write to us from the app. Nothing is sent until you press Send.
- What is sent. The topic you pick, your message, the app version, and your email address if you type one so we can reply. Your country is read from the request, at country level only.
- Diagnostics, if you leave them on. A short description of how the app is set up: the app and macOS versions, the Mac model, notch, panel, alert and shortcut settings, whether MeetKeeper has Calendar access, how many Google, Outlook and Notion connections you have, when they last synced and any sync error (with email addresses and calendar names removed), the licence state, whether automatic updates are on, and your time zone's offset from UTC. The app shows this text in full before you send, and you can switch it off. It never includes event titles, people, times, calendar names, email addresses or your licence key.
- Where it goes. Feedback is stored in our Upstash database (see subprocessors) and read only by us, to answer you and to improve MeetKeeper. It is never used for marketing, sold or shared.
- How long. Each message is deleted automatically 12 months after it was sent. To have yours deleted sooner, email hi@realanshuman.com. To limit abuse, a hash of your network address that changes every day is kept for one hour, to cap how many messages can be sent.
What MeetKeeper does not do
- There is no MeetKeeper account, and no MeetKeeper server holds your calendars. The app talks only to Apple's frameworks on your Mac, to Google's, Microsoft's and Notion's APIs directly if you connect them, to Polar when you enter a licence key, and to meetkeeper.fun to check for updates and to deliver feedback you send.
- MeetKeeper does not collect usage statistics, crash reports or telemetry. Its regular call home is the update check: a request to meetkeeper.fun every few hours that carries the app version and nothing else. We count those requests in aggregate to know how many copies are in use; they say nothing about you or your calendars. The only other thing the app sends us is feedback, when you write it and press Send.
- MeetKeeper does not sell, share, transfer or use your data for advertising, for building profiles, or for training machine-learning models.
- No human at MeetKeeper can see your calendar data.
How your data is protected
Your Google, Microsoft and Notion data is sensitive, so MeetKeeper protects it with the following safeguards:
- Encryption in transit. Every request to Google, Microsoft and Notion goes over HTTPS (TLS), enforced by macOS App Transport Security. MeetKeeper never sends calendar data over an unencrypted connection.
- Secure sign-in. Google and Microsoft sign-in happens in your own browser using OAuth 2.0 with PKCE and a one-time state check. MeetKeeper never sees or stores your password. The sign-in reply is received only on your Mac's local loopback address (127.0.0.1), which other computers cannot reach.
- Restricted token storage. Access and refresh tokens are kept in files under ~/Library/Application Support/MeetKeeper/ with owner-only permissions (0600), so other user accounts on the Mac cannot read them. They are protected by macOS's own account security and, if you use it, FileVault full-disk encryption.
- Calendar data stays in memory. Events fetched from Google or Microsoft are held in the app's memory only to display them. They are not written to disk, not cached on any server and not included in logs.
- No copy of your calendars. No server holds your calendar data, so there is no server-side copy of it that could be breached. Data goes directly between your Mac and Google, Microsoft or Notion. The only thing the app ever stores with us is feedback you choose to send.
- Least privilege. MeetKeeper requests only the permissions listed below, and uses them only for the features you use.
- Signed updates. App updates are verified with an Ed25519 signature before they are installed, so a tampered update is refused.
- Retention and deletion. Data is kept only while an account is connected. Disconnecting an account in Settings deletes its tokens from your Mac, and removing the app deletes everything it stored. You can also revoke access at any time from your Google or Microsoft account.
Google API Services: Limited Use
MeetKeeper's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Calendar data is used only to display your events in the app and to create, on your explicit request, the events, invitations and Meet links you ask for. It is not transferred to anyone else and is not used for any other purpose.
Permissions requested from Google
- See and download any calendar you can access: to list your calendars and show your events.
- View and edit events on all your calendars: to create the events you add in MeetKeeper, invite people and attach Google Meet links.
You can disconnect at any time from MeetKeeper's Settings, or by removing MeetKeeper at myaccount.google.com/permissions. Removing the app from your Mac deletes everything it stored.
Permissions requested from Microsoft
- Read and write your calendars (Calendars.ReadWrite): to show your Outlook events, create the events you add, invite people, reply to invitations and attach Teams links.
- Sign you in and read your profile (User.Read): to label the account with its address in Settings.
- Maintain access to data you have given it access to (offline_access): so you sign in once, not every hour.
You can disconnect from MeetKeeper's Settings, or by removing MeetKeeper under app permissions at myaccount.microsoft.com.
The website
www.meetkeeper.fun is hosted on Vercel. It counts page views and download clicks with a small script of our own, not a third-party service. Each count records the page, the button, your country, device and browser family, the site that referred you, and a hash that resets every day, so a repeat visit within a day counts once and days can't be linked. No cookies are set and no IP addresses are stored. With the Global Privacy Control signal on, nothing about your visit is recorded: page views aren't counted, and a download only adds one to the day's total and to the button you clicked. Vercel may keep standard, short-lived server logs.
Changes and contact
See also the terms of service, the refund policy and the list of subprocessors. If this policy changes, the new version will be published here with a new date. Questions: email hi@realanshuman.com or use the contact page.