Recording meetings and the GDPR
You want to record a meeting and have it written out. What does the GDPR ask of you, and what changes if the recording never leaves your own devices? A calm walk through the rules, with the official sources we read.
This is general information, not legal advice. It is about the GDPR as it applies in the Netherlands and the European Union. Your own situation, your sector or other laws can ask more of you. When in doubt, ask your data protection officer or a lawyer.
Published on 15 November 2026. Sources read on 15 November 2026.
A recording is personal data
A sound recording in which someone can be recognised is personal data. So is a transcript that says who said what. The Autoriteit Persoonsgegevens (AP), the Dutch data protection authority, names sound recordings as an example.[1][2]
The GDPR does not apply to a purely personal or household activity, such as a family conversation at the kitchen table that you record for yourself. A meeting at work or with clients is different: then the rules below apply.[2][3]
When you may record a meeting
Before you start, you need a legal basis. The GDPR has six (Article 6). For recording a meeting you usually look at consent and legitimate interest first. Which basis fits is yours to judge: the AP does not advise on it.[2][3]
- Consent. It must be freely given, unambiguous, informed and specific, and withdrawing it must be as easy as giving it. Mind the balance of power: the AP points out that employees can hardly refuse a request from their employer.[4][2]
- Legitimate interest. You have a real, concrete interest of your own, the recording is necessary for it (could it be done less intrusively, with notes for example?), and your interest outweighs that of the people you record. A public authority cannot use this basis for its tasks.[3][2]
Tell people, before you start
Whatever basis you choose, the people you record have the right to know. The GDPR asks you to tell them, when you collect the data, who you are, why you record, on what basis, who receives the recording, how long you keep it and what rights they have (Article 13).[2][5]
The AP's guidance on recording phone calls at work is concrete: say it at the start, for example with a signal whose meaning you explained beforehand, and say what the recording is for. Telling employees once, when they join, is not enough, and the person on the other end of the line must be told in advance too.[6]
For a meeting this usually means: put it in the invitation, say it again when you press record, and let your privacy statement say where recordings go and how long they stay.
Recording without telling is a different matter
Recording people who do not know it is a different situation altogether. For employers, the AP says recording phone calls in secret is almost never allowed: only in exceptional cases such as threats or a suspected criminal offence, never to coach, train or assess staff, and even then under strict extra conditions. Laws other than the GDPR can apply too. This guide does not cover secret recording; if you are considering it, get legal advice first.[6]
Record only what you need
Collect only what is necessary for your purpose, and use it for that purpose only (Article 5).[2]
- Decide the purpose first: minutes, a list of decisions, an exact quote. The purpose sets what you need.
- Is a transcript enough? Then you may not need to keep the audio once the text has been checked.
- Pause the recording for parts you do not need, such as the chat before you start or something personal.
- Be careful with voice recognition. Data you use to recognise who is speaking can be biometric data, a special category the GDPR prohibits unless an exception applies, such as explicit consent (Article 9).[7][1][3][2]
Decide how long you keep it
The GDPR sets no fixed retention period for a recording. You decide it yourself, and the starting point is: no longer than necessary, as short as possible. Write down the period and why you chose it, mention it in your privacy statement, and delete or anonymise the recording when the period is over. A system that deletes automatically at a set moment helps.[8][2]
A recording kept too long is also a reason people can ask you to delete it.[8][9]
Decide who may listen
A recording of a meeting is often more sensitive than the minutes: tone of voice, asides, things said in confidence. The GDPR asks for appropriate security against unauthorised access and against loss (Article 5).[2]
- Give access only to people who need the recording for the purpose.
- Keep the recording in one known place, not as an attachment in mails and chats.
- Know which copies exist: on a phone, a laptop, a shared folder, a backup.
Transcribing in the cloud means a processor
If an outside service stores or transcribes the recording for you, that service is a processor: it processes personal data on your behalf. The AP names a cloud service that stores personal data as an example. You remain the controller and stay responsible, also for what you outsource (Article 4).[2][10]
You then need a written processing agreement with that service (Article 28). It says, among other things, that the service works only on your instructions, keeps the data confidential and secure, uses sub-processors only with your permission, helps you with requests from the people you recorded, and deletes or returns the data when the service ends. Without such an agreement, you and the service are both in breach.[2][11]
Check too whether the service uses the recordings for its own purposes, for example to improve its models. Then it decides on purposes itself and is, for that part, not only your processor. And if the data go outside the European Economic Area, you have to tell people that as well.[10][2]
People can ask for the recording
Everyone you record keeps their rights. They can ask whether you hold data about them and get a copy, free of charge, within one month (for a complex request that may be extended by at most two months). Because someone's voice and words are personal data, this covers the parts of a recording or transcript about them (Article 15).[2][12]
Other people speak in the same recording. A copy of someone's personal data is not automatically a copy of the whole document; often an overview is enough. If you do hand over whole documents, other people's personal data must be removed or made unreadable.[12]
People can also ask you to delete their data, for example when you no longer need it for the purpose, when they withdraw their consent and you have no other basis, or when you kept it longer than you were allowed to.[9]
What local processing changes, and what it does not
Some programs record and transcribe on your own phone or computer, without sending the audio to a service. That changes one thing that matters.
What changes
- No processor for the recording itself. If the audio and the text are made and kept only on devices you manage yourself, no outside service processes them on your behalf. For that step there is no processing agreement to sign.[2][10]
- No transfer to explain. The recording does not travel to another company or another country.
- Fewer copies. There is no second copy at a provider that you have to trust, check and later have deleted.
What does not change
- You are still the controller. You decide why and how you record, so the responsibility is yours.[2]
- You still need a legal basis, and you still tell people beforehand that you record.[2]
- Retention still applies. A recording on your own laptop that nobody deletes is kept too long all the same.[8]
- Rights still apply. People can still ask for a copy or for deletion.
- Security is now up to you. A lost or shared device is where the risk sits: lock it, and know who uses it.
- Your other programs count too. If your computer backs up to a cloud service, or you mail the transcript around, that service is a processor again for that copy.[10]
A short checklist
- I know why I am recording, and I wrote the purpose down.
- I chose a legal basis, and with consent, people can say no without consequences.
- Everyone knows before the recording starts, and I say it again when I press record.
- My privacy statement says what I record, why, for how long and who receives it.
- I record only what the purpose needs, and use voice recognition only for people who explicitly consented to it.
- I chose a retention period and a moment to delete.
- Only the people who need it can open the recording.
- I have a processing agreement with every outside service that stores or transcribes the recording.
- I know how to find and hand over someone's parts when they ask.
Questions
Do I need everyone's consent to record a meeting?
Not always. Consent is one of six legal bases; legitimate interest can fit too, once you have made the weighing. Whatever basis you choose, you must tell people beforehand that you record and why.
Is it enough to mention recording in our privacy statement?
Usually not as the only step. The AP's guidance on recorded calls asks you to say it when the recording starts, and what it is for; informing people once is not enough. Your privacy statement is where you give the full details.
Is a transcript personal data too?
Yes, when it can be linked to the people who spoke, for example because their names are in it. The same rules on purpose, retention and access apply to the text as to the audio.
If I transcribe on my own device, have I met the GDPR?
No. You then need no processor for that step, but you remain the controller: you still need a legal basis, you inform people, you keep the recording no longer than necessary and you answer requests.
How long may I keep a meeting recording?
The GDPR sets no number. Keep it as long as the purpose requires and no longer, write down the period with your reasoning, and delete the recording when the period is over.
Where Notetaker fits
We make Viaalink Notetaker. This is how it relates to the above, in facts.
- Notetaker records the conversation and writes it out on your own phone or computer. Recording and transcribing work without internet.
- Your audio, transcripts and reports never reach us, and Notetaker does not send your audio anywhere else either. Recordings stay on the device that made them, until you delete them.
- No bot joins your online meeting; on a computer it records your microphone and the computer's sound.
- Voice profiles, to recognise who is speaking, are made only for people who gave their consent, and they stay on the device.
- The app has no ads, no advertising ids and no analytics or crash reporting.
- In this version the connection between your phone and your computer is not encrypted: pair only on a network you trust.
So there is no processor between you and the recording itself. The rest it does not do for you: you still choose the basis, tell people, decide how long you keep recordings and delete them. What does reach viaalink.com, such as the details sent when you activate, is in our privacy statement.
Sources
All sources read on 15 November 2026. The Autoriteit Persoonsgegevens pages are in Dutch. The GDPR is the text from the Official Journal of the European Union, published by the Publications Office of the EU.
- Autoriteit Persoonsgegevens: Wat zijn persoonsgegevens? (What is personal data?). www.autoriteitpersoonsgegevens.nl/themas/basis-avg/privacy-en-persoonsgegevens/wat-zijn-persoonsgegevens, read on 15 November 2026.
- Regulation (EU) 2016/679 (General Data Protection Regulation), Official Journal L 119 of 4 May 2016. publications.europa.eu/resource/cellar/3e485e15-11bd-11e6-ba9a-01aa75ed71a1.0006.03/DOC_1, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Grondslagen AVG uitgelegd (The legal bases of the GDPR explained). www.autoriteitpersoonsgegevens.nl/themas/basis-avg/avg-algemeen/grondslagen-avg-uitgelegd, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Grondslag toestemming (Consent as a legal basis). www.autoriteitpersoonsgegevens.nl/themas/basis-avg/avg-algemeen/grondslag-toestemming, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Recht op informatie (Right to information). www.autoriteitpersoonsgegevens.nl/themas/basis-avg/privacyrechten-avg/recht-op-informatie, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Controle van communicatiemiddelen (Monitoring means of communication). www.autoriteitpersoonsgegevens.nl/themas/werk-en-uitkering/controle-van-werknemers/controle-van-communicatiemiddelen, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Biometrie (Biometrics). www.autoriteitpersoonsgegevens.nl/themas/identificatie/biometrie, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Bewaren van persoonsgegevens (Keeping personal data). www.autoriteitpersoonsgegevens.nl/themas/basis-avg/privacy-en-persoonsgegevens/bewaren-van-persoonsgegevens, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Recht op gegevens verwijderen (Right to erasure). www.autoriteitpersoonsgegevens.nl/themas/basis-avg/privacyrechten-avg/recht-op-gegevens-verwijderen, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Verantwoordelijke en verwerker (Controller and processor). www.autoriteitpersoonsgegevens.nl/themas/basis-avg/avg-algemeen/verantwoordelijke-en-verwerker, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Verwerkersovereenkomst (Processing agreement). www.autoriteitpersoonsgegevens.nl/themas/basis-avg/avg-algemeen/verwerkersovereenkomst, read on 15 November 2026.
- Autoriteit Persoonsgegevens: Recht op inzage (Right of access). www.autoriteitpersoonsgegevens.nl/themas/basis-avg/privacyrechten-avg/recht-op-inzage, read on 15 November 2026.