Meetbell

Privacy policy

Last updated: 25 October 2026

Meetbell is a desktop app that reminds you of your meetings. It is built so that nothing about you leaves your computer except what is needed to show your calendar and the weather, and none of it reaches us: the app has no servers, no accounts, no analytics and no advertising. Meetbell is made by Abhishek Johri, an independent developer in India.

What the app reads, and where it goes

WhatWhyWhere it goes
Your calendar events (title, time, meeting link, location, organizer and attendee addresses) To fly a reminder before each meeting, open the meeting, mark VIP meetings and write the "running late" message Read directly from Microsoft 365 / Outlook.com, Google Calendar, iCloud or another CalDAV calendar (Fastmail, Yahoo, Zoho, GMX, WEB.DE, Nextcloud, Synology…), a calendar (.ics) link you add, classic Outlook on this computer, or (on a Mac) the calendars in Apple's Calendar app. Meetbell only reads them: Microsoft and Google grant read-only access, and an app password or calendar link is used only to read. Right after you connect a calendar, its next 7 days are read once, to show you its next meeting. Never sent anywhere else.
The last meetings read from each calendar (title, time, meeting link, location, organizer and attendees; not the invitation text) So reminders still come right after the computer starts, while you're offline, or while a calendar can't be reached Kept on your computer in cache.json in the app's folder, for 24 hours at most; a calendar you remove is taken out of it. Never sent anywhere.
Sign-in tokens for Microsoft or Google (only if you connect those) To keep reading your calendar without signing in again Stored on your computer, encrypted by Windows (DPAPI) or the macOS Keychain. Sent only to Microsoft or Google. Removed when you sign out, and on Windows when you uninstall the app (see Your control). If you untick the calendar box on Google's consent page, Meetbell has nothing it may read and gives the sign-in back to Google at once (a revoke request to oauth2.googleapis.com).
Your account's name and e-mail address (only if you sign in with Microsoft or Google) To show which account is connected, put your first name on the boarding pass, and recognise meetings you declined Stored on your computer, encrypted with the sign-in. Never sent anywhere.
The e-mail address you sign in with (only when you press a sign-in button) So Microsoft's or Google's sign-in page opens on that account, in your language, without asking you for it again Sent only to Microsoft or Google, as part of the sign-in page that opens in your browser: the address you typed or picked (login_hint); for a Microsoft work account also your organisation's tenant ID when Meetbell knows it (domain_hint); and Meetbell's language (ui_locales for Microsoft, hl for Google). Nothing is sent before you press the button.
The domain of the e-mail address you type to connect a calendar (only after you press Continue) To find out which service holds your calendar (Microsoft 365, Google Workspace, iCloud, Zoho, a CalDAV server…), so you don't have to know For Gmail, Outlook.com, iCloud, Yahoo, Fastmail, Zoho, GMX, WEB.DE and Proton addresses, nothing: Meetbell knows them. For any other address, only its domain (the part after the @), never the address itself: Microsoft's public sign-in service (login.microsoftonline.com) is asked whether it is a Microsoft 365 organisation, and your DNS resolver (usually your internet provider's or your company's) for the domain's mail servers (an MX lookup). If neither tells, your DNS resolver is asked for the domain's calendar server (_caldavs._tcp.<domain>), and https://<domain>/.well-known/caldav is asked, without any user name or password, whether it has one.
The accounts already set up on this computer (Windows): the work or school account Windows or Office is signed in with, the Microsoft account Windows uses, and classic Outlook's accounts To offer them in the Calendars window, so you can connect one with a click Read on your computer (from the Windows registry, without changing it) when the Calendars window opens, and only shown there. Not stored and never sent anywhere; only an address you click goes to Microsoft, as the sign-in hint above.
Your computer's user name (only when no Microsoft or Google sign-in gives a name) To put a first name on the boarding pass and the flight-log picture Read on your computer when the pass or the picture is drawn; not stored and never sent anywhere. The picture leaves your computer only if you share it yourself, and "Hide my name" leaves the name off.
The user name and app password of an iCloud or other CalDAV calendar (only if you add one) To read that calendar Stored on your computer, encrypted like the sign-ins. Sent only to that calendar's own server, over an encrypted (https) connection; never to another website, even if the server points somewhere else. For a Zoho account whose region isn't known yet, they are tried on each of Zoho's own regional calendar servers (calendar.zoho.com, .eu, .in, .com.au, .jp, .sa and calendar.zohocloud.ca) at once, to find yours. For Nextcloud you can instead sign in on your own Nextcloud's page in your browser: Meetbell asks your server, without a password, to start its login, opens that page, then asks your server with the one-time token it gave until it hands over an app password. Removed when you remove the calendar.
Calendar (.ics) links you add To read those calendars Stored on your computer, encrypted like the sign-ins (they work like passwords). Sent only to the calendar's own server, which is asked once when you add the link, to check that it works, before it is kept. Never written to the app's log.
The calendars on your Mac (only if you allow it) To read the events in Apple's Calendar app macOS asks you first, and you can turn it off in System Settings › Privacy & Security › Calendars. Read on your Mac; nothing is sent anywhere.
Your work e-mail domain (only if you use "Ask IT" or the admin-approval link in the Calendars window) To find your organisation's Microsoft tenant, so the approval link goes to the right place Sent to Microsoft's public sign-in service (login.microsoftonline.com), which answers with the organisation's ID. Nothing else is sent.
What's on your clipboard (only in the Calendars window) To paste an app password for you, and to offer a Google secret address you have just copied Read on your computer only when you press Paste, and on the Google calendar-link steps when you come back to the window (only a shortened hint of the address is shown). Not stored and never sent anywhere; a link goes to its calendar only if you add it.
The city you choose for the weather (its name and map position) To show weather and air quality in the widget While you search for a city, what you type (and the app's language, for the place names) is sent to Open-Meteo's place search; afterwards only the city's map position (latitude and longitude) is sent to Open-Meteo, a free weather service, from your computer. No account and nothing about you is sent; like any website, Open-Meteo sees your internet (IP) address.
Whether an app is using your microphone or camera right now, whether a full-screen app is running, and whether Windows' "Do not disturb" is on (Windows) To make reminders small and silent while you're on a call, sharing your screen, presenting or not to be disturbed, and to notice that you joined a meeting from another app Checked on your computer when a reminder is about to fly and, while "Notice when I join from another app" is on (the default), a few times from 2 minutes before to 10 minutes after the start of each online meeting you didn't join from Meetbell. Only whether the microphone or camera is in use is read: Meetbell never hears or sees anything. If it was in use, today's meeting log marks that meeting as joined. Nothing is sent.
Your settings, frequent-flyer miles, the reminders you add, today's meeting log, a count-only summary of past days (how many meetings, how many on time; no titles or people) and the recurring series you mute To remember your choices, show your boarding pass and landing report, make your flight-log picture, and stop reminders for a muted series Stored on your computer in the app's folder. Today's meeting log keeps the meetings' titles until the next day: once Meetbell runs on a later day, only that day's counts are kept, and the summary keeps the counts of up to 400 days. A muted series keeps its title until you unmute it. Never sent anywhere. The flight-log picture is made on your computer and leaves it only if you copy, save or post it yourself.
A request for the latest version number (only in the versions downloaded from Meetbell's website, not the Microsoft Store or Mac App Store ones) To tell you when a new version is out: the stores update their copies, but a downloaded copy doesn't update itself Once a day, https://abhi10304.github.io/meetbell-site/version.json is asked, with no cookies and nothing about you or your computer: no ID, no settings, no app or system version. The answer is a version number and a link. The website has no analytics; like any website, its host, GitHub, sees your internet (IP) address. Turn it off in Settings › General.
A log of what the app did and crash reports To find out what went wrong if you ask for help Kept on your computer only, in the app's folder. Calendar links, e-mail addresses, tokens and passwords are taken out before anything is written, and meeting titles are never written. Nothing is uploaded; "Copy diagnostics" copies a short report to your clipboard for you to send yourself.

When you press Running late?, the app opens a Teams chat or an e-mail draft addressed to the organizer. Nothing is sent until you press Send in that app yourself.

When you press Save video (Share › Flight video), a short clip (about 8 seconds) is made on your computer and saved as a file in your Videos folder (on the Mac App Store version, where you choose): a sample plane with the title you type, never a meeting from your calendar. It leaves your computer only if you share it yourself.

Tell me what to improve on the landing report opens an e-mail draft to the developer with only the app's version in the subject: no meetings, calendar or computer details. Nothing is sent until you press Send yourself.

When a reminder can't be shown as a plane (your screen is locked, you're away, or the plane couldn't fly), the app may also show it as a system notification. On the lock screen, and while you're away, that notification says "Meeting" instead of the meeting's title.

Google user data

Meetbell's use and transfer 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 on your computer: to show your reminders, the widget, your boarding pass and landing report, and to address a “running late” message that you choose to send. It is not stored on any server, not used for advertising, not sold, not used to train AI models, and not read by people.

What the app does not do

Your control

Children

The app is a work tool and is not directed at children.

Changes

If this policy changes, the new version will be published at this address with a new date.

Contact

Questions: elyxaj@gmail.com