Effective 2026-10-29
This Privacy Policy explains how Meetingpad ("we", "us", "our") collects, uses, discloses, and safeguards your information when you use our service, including the macOS application, meetingpad.io website, and related services (the "Service").
Account information: when you sign up with Google or Microsoft, we collect your name, email address, and your Google or Microsoft account identifier. Sign-in runs on our own servers; your session token is issued and verified by us.
Identity data: for each Google or Microsoft account you connect as an "identity", we store the identity's display name, timezone, email address, which provider it is, and an encrypted OAuth refresh token issued by Google or Microsoft.
Product data: event types you configure, polls you create, votes cast on your polls (including voter name and email), and bookings made through your links (guest name, email, and chosen time).
Payment data: Meetingpad does not currently take payments and collects no billing information. If paid plans are introduced, we will update this policy to name the payment processor and describe what it collects before any payment data is gathered.
AI key: if you provide an Anthropic API key to enable AI features, we store it encrypted at rest and use it only to make API calls to Anthropic on your behalf.
Download-link requests: if you ask us to email you the download link from meetingpad.io/download (offered on phones and tablets), we collect the email address you enter, the time of the request, and whether you ticked the box asking for product updates. Without that box ticked, we use the address only to send that one email and to stop the same address being sent the link more than once a day. We send product updates only to addresses that ticked the box.
Usage & diagnostics: we log requests to our API (timestamps, endpoints, IP addresses) for security and reliability. The macOS app logs errors locally on your Mac; we only see them if you send us feedback.
Calendar events: we read your calendar events only for the features you turn on, and only the parts each one needs.
We do not store the contents of your calendar events in our database, and we never read attachments. We read descriptions and attendees only to show them to you in the Calendar screen and for missed meetings.
We do not have your Google or Microsoft password. We do not sell or share personal data with advertisers. We do not use your Google user data to train, improve, or evaluate any generalized artificial intelligence or machine learning models.
We use your information to: (a) provide, maintain, and improve the Service; (b) authenticate you; (c) send booking invites, poll invitations, nudges, and follow-up emails on your behalf using the identities you have connected; (d) process payments and manage subscriptions; (e) communicate with you about the Service, updates, and support; (f) detect and prevent fraud and abuse; (g) comply with legal obligations.
We share information only with service providers necessary to run the Service:
We may disclose information if required by law, subpoena, or to protect the rights, property, or safety of Meetingpad, our users, or others.
Meetingpad'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.
When you connect a Google account as an identity, Meetingpad requests the following OAuth scopes and uses the resulting access only for the purposes described:
openid, email: to identify the connected Google account (email address only; used as the sender address on invites and to display which account is linked in the Meetingpad UI).https://www.googleapis.com/auth/calendar.events: to (a) create the calendar invite when a guest books your Meetingpad link, (b) update or cancel that invite if the booking changes, (c) create small titleless "Busy" placeholder events on your other connected calendars so cross-account double-booking is prevented, and (d) read your events as described in section 1 for calendar blocking, your combined calendar if you subscribe to it, busy times in Propose times and polls, missed meetings if you turn it on, and the Calendar screen, (e) create, edit, reply to and delete events you choose in the Calendar screen, and add a missed meeting when you click Add to calendar, and (f) query busy times via Google's freeBusy API to compute your unified availability. We never read attachments, and read descriptions and attendees only for the Calendar screen and missed meetings.https://www.googleapis.com/auth/gmail.send: to send booking confirmations, poll invitations, nudges, and follow-up emails from the connected Gmail address so recipients see them from the account they know. We do not read, list, modify, or delete any messages in your Gmail. We only send.https://www.googleapis.com/auth/drive.file: when you attach a Google Doc, Sheet, or Slide to a follow-up email, this per-file scope lets us grant view/comment access on that specific file to the meeting recipients you designate. We never access files you did not attach.What we do NOT do with Google user data:
How Google user data is stored and secured: OAuth refresh tokens are encrypted at rest with AES-256-GCM using a server-held key. Access tokens are short-lived (1 hour) and held only in memory during a request. Free/busy interval data cached to speed up booking page loads is retained for at most 5 minutes and never contains event contents. Event titles, times, locations and video links read for your combined calendar are held in server memory only, for at most 24 hours, and are never written to disk. Calendar events we create on your behalf carry only the metadata you and your guest entered on the booking form.
Revoking access: you can revoke Meetingpad's access to any connected Google account at any time by (a) removing the identity in the Meetingpad app (Settings → Delete identity), which deletes the refresh token from our server, or (b) revoking Meetingpad in your Google Account permissions at myaccount.google.com/permissions.
When you sign in with Microsoft or connect a Microsoft account (Outlook.com or Microsoft 365) as an identity, Meetingpad asks Microsoft for the following permissions and uses them only as described:
Meetingpad does not use Microsoft account data to train, improve or evaluate any AI or machine learning models, does not sell it, does not use it for advertising, and does not let anyone read it except with your agreement, for security, or to comply with the law. It is stored and secured the same way as Google data (section 5): refresh tokens encrypted at rest with AES-256-GCM, access tokens held only in memory during a request, and event details never written to our database.
Sharing a Google Doc from a follow-up email isn't available for Microsoft accounts: the email includes the link, and Meetingpad doesn't change who can open the file.
Revoking access: remove the identity in the Meetingpad app, which deletes the refresh token from our server, or remove Meetingpad from your Microsoft account's app permissions: for personal accounts at account.live.com/consent/Manage, for work or school accounts at myapplications.microsoft.com.
We retain your data while your account is active. If you delete your account: identity data (OAuth tokens, Anthropic key) is deleted immediately; polls, votes, and bookings are deleted after a 30-day recovery window; account records may be retained longer to comply with legal, tax, and audit obligations. Download-link requests are kept until you ask us to delete them; email legal@meetingpad.io and we will remove your address and stop any product updates.
OAuth tokens and Anthropic keys are stored encrypted at rest. Traffic between the app and our server is over TLS. Access to production infrastructure is limited to authorized team members. No system is perfectly secure; we cannot guarantee absolute security.
Depending on your jurisdiction (including under GDPR and CCPA), you may have the right to: access, correct, or delete your personal data; object to or restrict processing; port your data to another service; withdraw consent for optional processing. To exercise these rights, use the export/delete controls in the app (Settings → Account) or email legal@meetingpad.io.
The Service is not directed to individuals under 18. We do not knowingly collect information from children. If you believe we have inadvertently done so, please contact us and we will delete it.
Our server infrastructure is located in the United States. If you access the Service from outside the United States, your information will be transferred to and processed in the United States. Where required, we rely on appropriate safeguards such as the European Commission's standard contractual clauses.
Our website sets no cookies and uses no tracking identifiers. There is no Google Analytics and no advertising tracker. (Until 2026-10-08 the site offered Google Analytics behind an opt-in banner. It has been removed, and the site now deletes the cookies it set on your next visit.)
Cloudflare Web Analytics. Our website is hosted on Cloudflare, which also counts visits for us with Cloudflare Web Analytics. It sets no cookies, uses no persistent identifier, and doesn't track you across sites. It records the page you visited, the site that linked you there, your browser and device type, your country, and how quickly the page loaded. We see these only as totals. It isn't loaded for visitors in the European Union.
Visit, download and sign-in counts. When you open a page on this site, click a download link, or open the app's sign-in screen, our server adds one to a count, and may send our team a short notice of the visit (the page, the linking site, your country and operating system family). It stores the step, the time, the page you clicked from, the referral tag in the link (for example "betalist"), your device's operating system family, and your country. It doesn't store your IP address, your browser details, or anything that identifies you, and nothing is stored on your device.
The Meetingpad Mac app itself contains no analytics, and nothing about your calendars, meetings, contacts, or email is part of any of these counts. Sign-in may set cookies necessary for authentication.
We may update this Privacy Policy from time to time. Material changes will be announced by email or in-app notice at least 15 days before they take effect. The "Effective" date at the top of this page indicates the latest revision.
For privacy questions or to exercise your rights, email legal@meetingpad.io or chat with support.