Privacy.

Version 1.5 · Effective 27 October 2026

The short version. MeetBar runs on your Mac. It reads the calendars your Mac already has, or your Google Calendar if you connect a Google account inside the app, counts your meetings down, and writes notes as plain text files on your disk. Your Google Calendar data goes straight from Google to your Mac over an encrypted connection and is never sent to or stored on our servers. You sign in with Google on this site for your trial, your licence and the download; that website sign-in only gets your name and email and never sees your calendar. Once a day, its update check sends a small, anonymous signal (see "Licences and updates"). If you join the invite-only beta, MeetBar also records how you use its own windows (see "If you join the beta"). Meeting titles, notes, attendees and calendar contents never reach our servers.

What MeetBar reads

Your calendar. Through macOS Calendar access, or straight from Google Calendar if you connect a Google account (see "Google Calendar"). Event titles, times, attendees and meeting links, read on your Mac to show and count down your next meeting and to build the meeting card.
Your notes. The notes you type in MeetBar, stored as Markdown files in a folder on your Mac. You choose the folder. They are yours: open them in any app, move them, delete them.

What stays on your Mac

Calendar data, notes, and the app's own settings. All local.
Recordings, when you use the built-in recorder: audio is captured and kept on your Mac. It is never uploaded by MeetBar.
Transcripts made on your Mac stay on your Mac.

What can leave your Mac, and only when you choose

Cloud AI features. Off unless you turn them on; the on-device engine sends nothing. If you turn one on, the text needed for a summary or prep brief (the meeting title, your notes and transcript lines) is sent to the AI provider you pick, only to make that summary for you. Audio is never sent. Text sent this way is not used to train models.
Feedback and bug reports. Report a Bug opens a short form. It sends what you type, your email only if you type it, and a screenshot only if you attach one. "Include diagnostics" is on unless you switch it off: it adds the app version, your macOS version, the last crash text and, if you are in the beta, your recent clicks in MeetBar. Nothing goes until you click Send.
Crash reports. After a crash, MeetBar asks once if you want to send a report. Yes opens the same form with the crash text filled in, so you can read it before you send.
Usage counts. MeetBar asks once if you want to share anonymous counts of which features you use (Settings → Share anonymous usage). Off sends nothing. The counts hold no content.
Send to your apps. When you click Send, the item you approved goes to the app you chose (for example Reminders or Things). Nothing sends itself.
Joining a meeting. Clicking Join opens the meeting link in the meeting app or browser you already use.
Email you send us. If you write in, we keep the email to reply to you.

What MeetBar does not do

No ads. Nothing leaves your Mac except what this page lists.
No note content, calendar content or audio is ever included in anything MeetBar sends to us.
No selling or sharing of your data with anyone.
This site has no tracking pixels. It counts page views and download clicks with its own small counter: no cookies, no visitor ID, and your IP address is not stored.

If you join the beta

The beta is invite-only and needs an invite code. Nothing in this section is recorded until you join, and MeetBar shows you a notice the moment you do.

What is recorded. Where you click inside MeetBar's own windows, the name of the MeetBar button you clicked, and the window size. Which MeetBar screens you open and for how long. Tasks you start in MeetBar and whether you finish them. Error codes. Which MeetBar features you use. Each upload also carries the app version, your macOS version and the random install ID.
What is never recorded. Meeting titles, notes, attendee names or emails, calendar contents, or anything outside MeetBar's windows.
Who sees it. Only Tanny, who makes MeetBar.
Where it is kept. On your Mac until it is sent (sent copies stay on your Mac for 14 days), then in our Vercel Blob storage.
When it is deleted. When the beta ends, MeetBar stops sending, and within 30 days we delete the beta data from our storage. Tanny may keep one private copy to read the results; that copy is deleted within 90 days of the end.
How to stop. Settings → General → Beta tester → Leave. MeetBar stops recording and deletes the beta data on your Mac.
How to have it deleted. Email us and we delete what we hold about you.

Your account on this site

You sign in with Google. This sign-in asks Google only for your name and email. We keep your email, your name, your Google account ID, an account ID made from your email, and a cookie that keeps you signed in for 30 days. Our servers do not read your Gmail, Drive, calendar or anything else in your Google account. (Connecting Google Calendar inside the Mac app is separate and stays on your Mac; see "Google Calendar".)
The account holds your trial or licence and, in the beta, your invite code.

Licences and updates

Google sign-in. You sign in with Google on this site to start your 14 days free and to hold your licence. It is only used for your account and never sees your calendar.
The licence key works offline and covers 1 Mac. Activation links the key to that Mac with a random install ID and the Mac's name, and we note when it last checked in, so you can see and move your licence on your account page. Without a licence after your free days, MeetBar switches to Show-only.
Updates come as a signed, notarized download from this site. Once a day, MeetBar's update check sends its version, your macOS version and a random install ID. Our server keeps your country and a scrambled form of your IP address, never the address itself. Nothing about your meetings, notes or calendars is ever sent.

Payments

MeetBar costs $9.99, paid once through Stripe. MeetBar never sees your card number. Stripe tells us that you paid and your email, so we can issue your licence and link it to your account. Any paid licence can be refunded within 14 days.

Deleting everything

Drag MeetBar to the Trash. Your notes folder stays where you put it; delete it if you want it gone. Calendar access can be removed in System Settings → Privacy & Security → Calendars. A connected Google account is removed in MeetBar's Settings → Calendar → Remove, and you can cut MeetBar's access at any time at myaccount.google.com/connections. To remove your account or beta data, email us and we delete it within 30 days. Beta data is also deleted by itself after the beta ends (see "If you join the beta").

Google Calendar

Connecting a Google account inside MeetBar is optional. If you do, MeetBar asks Google for:

See your calendars and events (calendar.readonly): to list your calendars and show, count down and open your meetings.
Change events you act on (calendar.events): only when you do it in MeetBar, such as creating an event, moving it, adding time, renaming it, answering or declining an invite, or deleting it. An event you create while offline is sent when your Mac is back online.
Your email, name and profile picture (email, profile, openid): to show which account is connected.

Where it goes. Calendar data travels straight from Google to MeetBar on your Mac. It is not sent to our servers, and we never see it.
Where it is kept. Events are held in the app's memory while it runs and are not saved to disk. What stays on your Mac: the notes you write (named after the meeting), events you created offline until they are sent, and which calendars you picked.
Who it is shared with. No one. We do not sell Google user data, use it for ads, or give it to anyone. The one exception is your choice: if you turn on a cloud AI feature, the text described in "Cloud AI features" goes to the provider you pick, only to make your summary.
AI and machine learning. MeetBar does not use Google Workspace API data, including your Google Calendar data, to develop, improve or train generalized or non-personalized AI or machine-learning models, and does not let any AI provider use it for that.
How long it is kept. Until you disconnect the account or delete MeetBar. Disconnecting deletes the account's sign-in key from your Mac at once.

How we protect your data

Encrypted in transit. Every connection MeetBar and this site make to Google, to us, to Stripe and to AI providers uses HTTPS (TLS). The only plain connections stay inside your own Mac.
Safe Google sign-in. MeetBar uses Google's own sign-in page with OAuth and PKCE. MeetBar never sees your Google password.
Sign-in keys stay on your Mac. The key that keeps your Google account connected is stored only on your Mac, in a file that only your macOS user account can open. Short-lived access keys are kept in memory only.
Least data. Your Google Calendar data never leaves your Mac for our servers, so there is nothing of it there to leak. MeetBar asks only for the Google access its features need.
Our servers. Account and licence records sit with our host, Vercel, in private storage that only our server can read with a secret key, and Vercel encrypts stored data with AES-256. Your sign-in cookie is signed, and set as HttpOnly and Secure so pages and plain connections cannot read it. IP addresses are kept only as a one-way scrambled hash. Card details are handled by Stripe and never reach us.
Who can get in. Only Tanny, who makes MeetBar, can reach the servers and stored records, through accounts that need a sign-in. Secret keys live in the host's protected settings, never in the page or the app's code.
If something goes wrong. If we learn that your data was exposed, we will tell you by email without delay and say what happened and what we did.

Google API Services User Data Policy

MeetBar'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.

Changes and contact

This page will change as MeetBar changes; the date at the top tells you which version you are reading. Questions: email us.