Privacy Policy

Effective date: September 13, 2026. Last updated: September 21, 2026.

1. Introduction

Meetso is an AI notetaker. It joins your online meetings, records and transcribes them, and turns each one into a summary, action items and searchable knowledge for your team.

Meetso is run by Stackdrop E.E. (STACKDROP ΕΕ), Troon 26, 11851 Athens, Greece. Throughout this policy, Stackdrop E.E. is referred to as we or us.

This policy explains what information we collect, how we use it and the choices you have. It covers this website, the Meetso web and desktop apps, the notetaker, our API and the emails we send.

For your account and the way you use the service, we decide how information is handled. For the meetings your organisation records, the organisation is in charge, and we handle that content on its behalf.

2. Information we collect

Information you give us

Your account. You sign in with Google, which gives us your name, email address, profile picture and Google account id. We also store a hash of the picture.
Your organisation: its name, its members and their roles.
A voice sample, only if you choose to turn on voice recognition.
Integrations your organisation sets up, such as webhooks and API keys.
Anything you send us, such as feedback or a bug report.

Meeting content

When Meetso records a meeting, we collect:

the audio, video and screen shares of the meeting;
messages sent in the meeting chat;
the names of the participants and the times they joined and left;
the transcript, with a speaker label on each passage;
what our AI produces from it: summaries, action items and profiles of the companies and people you meet.

The same applies to recordings you upload, and to meetings you capture with the desktop app, which records your microphone and the sound of your computer once you allow it and keeps a sign-in token in the keychain of your computer.

Calendar information

If you connect Google Calendar, we read your events: the title, description, start and end time, meeting link, the names and email addresses of the attendees, the organiser and whether the event repeats. Access is read-only. We never change anything in your calendar.

Information we collect automatically

Usage and diagnostic data: identifiers, timestamps, the features used and how long things took. It holds no names and no content.
Your IP address, which we use to limit request rates and prevent abuse.
Anonymous error reports when something breaks.
Cookies that keep you signed in and remember your preferences. See Cookies and similar technologies below.

We do not collect payment card details today. If that changes, we will update this policy first.

3. How we use information

We use the information we collect to:

provide the service and keep your account working;
join the meetings on your calendar, which the notetaker does by default and which you can turn off for any meeting;
transcribe meetings and work out who said what;
produce summaries, action items, company and people profiles, and search across your meetings;
send you notifications and a weekly digest, each of which you can switch off in Settings, under Notifications;
keep the service secure, prevent abuse and fix problems;
measure what the service costs to run and how it is used;
meet our legal obligations.

We do not sell personal data and we do not use it for advertising. The analytics we show to the admins of an organisation are totals, never a view of what one member did.

4. How we use AI

Two providers do the AI work for us. pyannote.ai transcribes the audio and separates the speakers. The OpenAI API writes summaries, extracts action items and other insights, matches speakers to the people invited, translates transcripts when your organisation has chosen a transcript language, and composes the weekly digest.

We do not train AI models on your content, and neither provider trains on it. OpenAI stores request and response data for up to 30 days and then deletes it. pyannote.ai receives the audio of the meeting and, when it is recognising the voice of a user who has opted in, the name or email address used to label that voiceprint.

AI output can be wrong or incomplete. Please check it before you rely on it.

Voice recognition is opt-in. If you turn it on, we create a voiceprint so that you are recognised in future meetings. It is stored encrypted, used only in the meetings of your organisation, and deleted the moment you withdraw your consent in Settings. We never create a voiceprint for anyone who has not opted in.

Service providers

We rely on a small number of companies to run Meetso:

Amazon Web Services, European Union (Frankfurt, Germany): hosting, database and file storage for the service and all the content in it.
Vercel, United States and global edge: hosting for this website and the front end of the web app.
pyannote.ai, France: transcription, speaker separation and, for users who opted in, voice recognition.
OpenAI, United States: summaries, action items and other insights, name matching, translation and weekly digests.
Resend, United States: delivery of the emails we send you, which can include an excerpt of a meeting summary.
Sentry, United States: anonymous error monitoring and masked session replay of the web app.
Google, United States and global: sign-in and the Google Calendar connection.

The notetaker also joins meetings on Google Meet, Microsoft Teams and Zoom. Those platforms are not our service providers: they see the notetaker as one more participant in the meeting, under their own privacy policies.

Within your organisation and at your direction

Members of your organisation can see its meetings according to their role and to whether they were part of the meeting.
A meeting can be shared with another organisation on Meetso, which can then view it but not change it.
Your organisation can connect webhooks, API keys and AI assistants (through MCP). What is sent to those destinations is under your control.

Legal and corporate

We disclose information when the law requires it, or to protect the rights or safety of our users, the public or ourselves. If we are involved in a merger or acquisition, your information may pass to the new owner under this policy, and we will tell you beforehand.

6. Google user data

When you sign in with Google, we receive your basic profile: your name, email address and profile picture. We get read-only access to your Google Calendar only if you connect a calendar in Settings, under Connections, never at sign-in.

We use this information only to provide the features described in this policy: listing and joining your meetings, matching attendees to speakers, and deciding who may see a meeting. Calendar event titles and the names and email addresses of attendees are included in the AI processing described under How we use AI. We never sell Google user data or use it for advertising. You can disconnect your calendar at any time in Settings, under Connections, or at https://myaccount.google.com/permissions. Doing so deletes the access token we store, which is encrypted at rest, and stops all syncing.

Meetso's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. Meetso does not use Google Workspace APIs, or any data obtained through them, to develop, improve, or train generalized or non-personalized artificial intelligence and/or machine learning models.

7. How long we keep information

Meeting content belongs to the organisation that recorded it, and we keep it for as long as the organisation does. We do not delete meetings automatically.

Meeting content (recordings, transcripts, chat, AI output) and synced calendar events: kept until the organisation asks us to delete it or the organisation itself is deleted.
Camera video of individual participants: deleted after 90 days, while the recording of the meeting itself stays.
Voiceprints and your voice sample: kept until you withdraw consent, then deleted immediately.
Google Calendar access token: kept until you disconnect the calendar or revoke access at Google, then deleted immediately.
Sign-in sessions: expire after 30 days without activity.
Diagnostic usage events: deleted after 180 days.
The audit log of an organisation: deleted 30 days after the organisation is deleted.
Billing and usage records (durations and counts, no content): kept as accounting records.
Anonymous error reports and session replays: held by Sentry for its own retention period.

You can delete your account in Settings. That removes your profile, sign-in data, calendar connection and token, voiceprints and notification data. Meetings stay with your organisation.

The Owner can delete the organisation once they are its only member, which deletes all of its content.

To have a single meeting deleted, email privacy@meetso.ai and we will delete it within 30 days.

8. Security

We encrypt information in transit, and we encrypt access tokens, voiceprints and secrets at rest. The service is hosted in the European Union, on Amazon Web Services in Frankfurt. Inside an organisation, what a person can see depends on their role (Owner, Admin or Member), and admins can review a log of administrative actions.

Our staff can access information only as far as is needed to operate, support and test the service. This can include copying meetings that staff select into an internal test environment.

No system is perfectly secure. If you think you have found a security problem, or that your account has been compromised, please email privacy@meetso.ai.

9. International transfers

We store your information in the European Union. Some of the service providers listed above are based in the United States. When information is transferred to them, we rely on the EU-US Data Privacy Framework where the provider is certified, and otherwise on the Standard Contractual Clauses approved by the European Commission. You can ask for a copy of these safeguards at privacy@meetso.ai.

10. Legal bases (EEA and UK)

If you are in the European Economic Area or the United Kingdom, we rely on the following legal bases:

Contract: to provide your account, the service and support.
Legitimate interests: to keep the service secure, prevent abuse, understand and improve the product, and identify the participants of the meetings an organisation records.
Consent: for your Google Calendar connection, and explicit consent for voiceprints, which are biometric data. You can withdraw either at any time in Settings.
Legal obligation: to keep accounting records.

For the meetings it records, your organisation is the controller and we are its processor. It is responsible for its own legal basis, including telling participants and asking for their consent where the law requires it.

11. Your rights and choices

You can ask us to:

give you a copy of the information we hold about you;
correct information that is wrong;
delete your information;
give you your information in a portable format;
stop or restrict a particular use of your information.

You can also withdraw a consent at any time. Many of these choices are in Settings, where you can disconnect your calendar, turn off voice recognition, change your notifications and delete your account. For anything else, email privacy@meetso.ai. We answer within one month, and we may ask you to confirm who you are first.

You can also complain to the Hellenic Data Protection Authority (dpa.gr) or, if you live in the United Kingdom, to the Information Commissioner (ico.org.uk).

We do not make decisions that have a legal or similarly significant effect on you solely by automated means.

12. If you were in a meeting recorded with Meetso

You may have been in a meeting that someone else recorded with Meetso without having an account yourself. The notetaker always joins under a visible name, and on Google Meet and Microsoft Teams it also posts a notice in the meeting chat.

We hold your name as it was shown in the meeting, your voice and what you said, your video if your camera was on, any chat messages you sent, and your email address if you were on the invitation.

The organisation that recorded the meeting is responsible for telling you about the recording, and it is your first point of contact. You can also email us at privacy@meetso.ai and we will pass your request on or act on it ourselves. The rights under Your rights and choices are yours too.

13. Cookies and similar technologies

This website does not use analytics or advertising cookies. The Meetso app uses a cookie that keeps you signed in and a few that remember interface preferences. It loads no advertising or analytics trackers.

The app uses Sentry for anonymous error monitoring. An error report contains no account identifier, no IP address and no request content. Sentry also records a session replay for a sample of sessions, and for sessions in which an error occurs, so that we can reproduce problems. In a replay all text is masked and all media is blocked, so it never shows the content of your meetings.

The Report a bug form in the app sends only what you type into it.

14. Children

Meetso is a tool for work and is not intended for anyone under 18. We do not knowingly collect information from children. If you believe a child has given us information, email us and we will delete it.

15. Changes to this policy

We may update this policy from time to time. If a change is significant, we will let you know by email or in the app before it takes effect. The date at the top of this page shows when the policy was last updated.

16. Contact us

Questions about this policy or about your information are welcome at privacy@meetso.ai. Legal notices go to legal@meetso.ai. We have not appointed a data protection officer; the privacy address reaches the people responsible.

Stackdrop E.E. (STACKDROP ΕΕ)
Troon 26, 11851 Athens, Greece