AI meeting notes and GDPR, from recording to deletion
When is it legal to record sales calls and meetings under GDPR? Lawful basis, notice and retention, plus where Flowmeets stores your data.
Security · September 1, 2026 · 10 min
Before teams compare features, they usually ask two questions about an AI notetaker. Are we allowed to record our calls and meetings? And where does the recording go afterward? This post covers both, in plain language.
This is not legal advice. What applies to you depends on who you record, why and where they are. Ask your data protection officer or legal counsel to make that assessment. Flowmeets is GDPR-native, but no tool on its own makes your organization compliant. Your organization is the controller and decides how recordings are used.
Is it legal to record sales calls?
Often, yes, but the answer depends on two sets of rules. Recording laws decide whether you may record a conversation at all, and whether everyone has to agree first. Data protection rules, such as GDPR, decide how you handle the recording once you have it. A sales call can be fine under one and still fall short under the other.
Recording laws vary by country and state
In the US, recording rules are set by federal and state law. Some states require everyone on the call to agree to the recording. European countries have their own rules as well, and some require consent from all participants. When a call crosses borders, many teams simply follow the strictest rule that applies. Your legal counsel can tell you which rules cover your calls.
GDPR applies when you record people in the EU
If your company is in the EU, or the people you talk to are, GDPR is likely to apply. A recording is personal data when voices and what was said can be linked to a person. GDPR does not ban recording. It sets requirements for how you do it.
What GDPR expects before you hit record
A clear purpose
Decide why you are recording. It might be to stop taking notes by hand, to write the follow-up or to keep your CRM up to date. The purpose limits what you can later use the recording for. If the same recordings will be used to coach your own team, tell them up front.
A lawful basis
Every use of personal data needs a lawful basis. For recording at work, many organizations rely on legitimate interests. That means weighing your need against the participants’ privacy and writing down how you reached your conclusion. Consent is another basis, but it is hard to rely on between employer and employee, and people can withdraw it. No product can choose a lawful basis for you.
Notice to everyone on the call
Everyone in the meeting should know that it is being recorded, why and who to contact with questions. Put it in the invite or say it when the meeting starts, even when the tool shows it too. This applies to customers and colleagues alike.
Retention you can defend
Decide how long recordings, transcripts and summaries are kept, and delete them once they have served their purpose. People who were recorded can ask for a copy of their data and, in some cases, ask you to delete it. You need to be able to find it and remove it.
Do you need consent to record a call?
Under GDPR, not always. Consent is one of several lawful bases, and many companies use another one. But recording without consent never means recording in secret. You still have to tell people, whatever basis you use. Recording laws in some countries and US states can still require everyone’s agreement, so check those separately.
Video calls, phone calls and in-person meetings
The principles are the same. The practical steps differ.
- Video calls: the Flowmeets notetaker joins under its own name and appears in the participant list. Mention the recording when the meeting starts anyway.
- Phone calls: say at the start of the call that it is being recorded and why, and give the other person a chance to say no.
- In-person meetings: you record directly in Flowmeets on your computer or phone. Tell everyone in the room before you start. Permissions and retention work the same way as for other meetings.
How Flowmeets keeps recording visible
In an online meeting, the notetaker joins under its own name, appears in the participant list and posts a message in the meeting chat saying that the meeting is being recorded. Before an external meeting, participants can get an email with an opt-out link. If anyone opts out, the notetaker stays out of that meeting. Your team decides in the settings whether that email goes out and when the notetaker joins.
That does not replace telling people yourself, but it makes the recording visible to everyone in the meeting.
What makes an AI notetaker GDPR compliant
No AI notetaker is GDPR compliant on its own. Compliance depends on how your organization uses it. What a tool can do is make the right way of working easy and the wrong way hard. Look for:
- Storage and processing in the EU, with clear answers on where AI analysis runs.
- An included data processing agreement (DPA) and a subprocessor list you can request.
- A notetaker that is visible in the meeting, plus a way for participants to opt out.
- Retention you set yourself, and deletion of all or part of the data.
- Access rules, so people see only the conversations they should.
- No training of AI models on your data.
The sections below show how Flowmeets handles each of these.
Where recordings, transcripts and summaries are stored
All customer data, including meeting recordings, transcripts and summaries, is stored and processed in the EU. The same basics are summarized on our Security page.
You decide how long each kind of material is kept, and different departments can use different periods. Data is kept for up to three years, or less if you set a shorter period. Some teams keep the summary longer than the audio. Others delete the recording once the follow-up is sent. You can delete data in full or in part, and GDPR export is available.
Transcription and AI analysis in Europe
We use open AI models running in Europe, instead of the big US AI services many other tools rely on. Transcription and AI analysis of your meetings both happen in Europe. That gives you a clear answer when a security questionnaire asks where data is processed, not only where the company is registered.
Recordings, transcripts and summaries are stored and processed in the EU.
Transcription and AI analysis run on open AI models in Europe.
A DPA is included, and the subprocessor list is available on request
Every customer gets a data processing agreement (DPA) with Flowmeets. You can read the DPA on our site. Flowmeets acts as the processor for the personal data you put into the service. You decide the purpose and how recordings are used.
Flowmeets uses subprocessors. You can request the list, with country and purpose, through our Trust center. You get written notice 30 days before we change or add a subprocessor.
No training on customer data
We do not use customer data to train AI models. Meeting content is used for your notes, follow-ups, coaching from the transcript, CRM updates and the questions you ask. It is not used to improve a general model.
Who can see what
Users see only their own conversations, unless something has been shared in a team space. Team admins also see what is shared in their team.
When you connect an AI assistant through MCP, such as Microsoft Copilot (see AI connections), the assistant sees only what that user’s Flowmeets account can see. Copilot has read-only access and cannot change or delete anything in Flowmeets.
SSO sign-in, optional multi-factor authentication and role-based permissions let IT hold Flowmeets to the same standard as the rest of your stack.
GDPR-native, with SOC 2, ISO 27001 and ISO 42001 in progress
Flowmeets is GDPR-native, and a DPA is included. SOC 2, ISO 27001 and ISO 42001 are in progress. Current status and documentation are in the Trust center.
Before you record your first customer call
Go through these points internally, ideally with your data protection officer:
- What is the purpose of recording, and what will recordings not be used for?
- Which lawful basis do you rely on, and is your assessment written down?
- How and when are customers and colleagues informed?
- Which recording laws apply where your participants are?
- How long are recordings, transcripts and summaries kept?
- Who can see which meetings?
- How do you handle a request to access or delete data?
With those answers written down, the rollout tends to go more smoothly for both sales and security.

