Interview Recording Consent and GDPR: What to Cover

Why an interview recording is personal data, what a consent form should cover, what changes with special category data, why it matters where transcription happens, and a checklist for before the first interview.

By ·

When you record an interview, you start processing personal data the moment the recording starts, before any transcription has happened. Whether it is for a thesis, a research project, a piece of journalism or an internal survey, before you press record you should know what legal basis you are relying on, what the interviewee has been told, and where the recording will be processed afterwards.

Please note: this article is general information and does not replace legal advice. What applies to your study or project depends on the specific case, your institution and the applicable law. Take the specific questions to your university's or organisation's data protection officer and, where required, to your ethics committee or review board.

How to get from the recording to a transcript is covered in the guide on how to transcribe interviews.

Why an Interview Recording Is Personal Data

A voice can be linked to a person. That alone means an audio recording is, as a rule, personal data under the GDPR. Then there is what is said, such as names, employers, places, experiences and opinions. Even if nobody gives their name, a person can often be identified from context, especially in small groups, organisations or professional communities.

The same goes for the transcript. As long as it contains details that could identify someone, it is personal data too, even after the name has been replaced.

Interview Recording Consent as a Legal Basis

Every processing of personal data needs a legal basis. For interviews in research, student theses or journalism, that is often the interviewee's consent under Art. 6(1)(a) GDPR. Depending on your institution and purpose, another legal basis may apply instead. Your data protection officer can tell you which one is right for you.

Art. 7 GDPR sets conditions for consent. You must be able to show that consent was given, and it must be freely given for a specific purpose. A written request must be clear and distinguishable from other matters. The person can withdraw consent at any time and must be told so beforehand. In practice, that usually means obtaining and documenting consent before you record, typically in writing or at least stated on the recording at the start, as your institution requires.

What a GDPR Consent Form for an Interview Should Cover

A consent form describes your specific processing, so a form copied from the internet will rarely fit. Many universities provide their own templates, which you should use. Whatever the format, it should answer these points in plain language:

  • Purpose. What the interview is for and how it will be analysed, such as a particular thesis or project.
  • Recording. That the conversation will be recorded, as audio, video or both.
  • Transcription. That the recording will be transcribed, whether by yourself, a service or software, and where that software runs.
  • Storage. Where the recording and transcript will be stored and how they are protected.
  • Access. Who has access, for example only you, the project team, or also supervisors and examiners.
  • Retention and deletion. How long the recording is kept, when it is deleted, and what happens to the transcript.
  • Anonymisation. Whether and how identifying details are replaced, and in what form quotations may be published.
  • Withdrawal. That consent can be withdrawn at any time, who to contact, and what then happens to the data.
  • Contact. Who is responsible and how to reach you and the data protection officer.

Special Category Data in Interviews

Some interviews touch on subjects the GDPR protects particularly closely, including health, political opinions, religious or philosophical beliefs, racial or ethnic origin, trade union membership, and sex life or sexual orientation. Art. 9 GDPR prohibits processing such data in principle and allows it only under specific conditions, such as explicit consent.

If your interviews touch on these subjects, even in passing, plan for extra care, with consent that names this data explicitly, tighter access rules, early pseudonymisation and close scrutiny of where the recording goes for transcription. For research, Art. 89 GDPR also calls for appropriate safeguards, such as data minimisation and pseudonymisation. This is where an early conversation with your data protection officer and ethics committee pays off most.

Transcription and Data Protection: Where the Recording Is Processed

For data protection in transcription, most depends on where the recording is processed.

With a cloud tool or transcription service, the recording goes to a third party. That party usually acts as a data processor, and Art. 28 GDPR then requires a data processing agreement. Also check where the provider processes the data, which sub-processors are involved, and whether data is transferred to countries outside the EU and EEA. Such third-country transfers are only permitted under additional conditions. And all of it has to match what your consent form says.

With in-house processing, the recording stays on your computer or on a server belonging to your university or organisation. The transcription stays inside your institution, so the questions about processors, third-country transfers and vendor copies fall away. The consent form becomes simpler, and many ethics committees look favourably on this route.

The questions data protection officers typically ask about a transcription setup are covered in On-Premise Transcription for GDPR: What Your DPO Will Ask.

Anonymising and Pseudonymising Transcripts

The two terms are often confused, but they have different consequences.

  • Pseudonymising means replacing names and other direct identifiers with codes or pseudonyms and keeping the key separately and securely. Pseudonymised data is still personal data, because the key lets you re-identify the person.
  • Anonymising means removing or generalising details so that the person can no longer be identified by any reasonably likely means. Truly anonymous data falls outside the GDPR. With qualitative interviews, though, true anonymity is hard to achieve, because contextual details can give a person away.

In practice, pseudonymise early, also replace indirect clues such as unusual job titles, small places or specific events, and check quotations again before publication for anything that could make someone recognisable. How you apply this consistently in your transcripts belongs in your transcription conventions.

Checklist: Interview Data Protection Before the First Conversation

  • Legal basis agreed with your data protection officer?
  • Consent form prepared on your institution's template, covering purpose, recording, transcription, storage, access, deletion, anonymisation and withdrawal?
  • Checked whether special category data is involved, and if so, named explicitly in the consent?
  • Decided where transcription happens, and for external services checked the data processing agreement, processing location and sub-processors?
  • Storage location and access rights for recordings and transcripts set?
  • Retention periods set and diarised?
  • Process for pseudonymisation and the key agreed?
  • Ethics approval obtained where required?

For dissertations, Transcribing Interviews for a Dissertation or Thesis walks through the whole process. Scriber transcribes recordings on a Linux server belonging to your institution, with speaker separation and without the recording leaving your own network. The page about transcription for research has more detail. The free hosted demo at scriber.determin.de is meant only for recordings that are not confidential. For questions, write to [email protected].

Frequently Asked Questions

Do I need consent to record an interview?

A recording contains personal data, so it needs a legal basis. For interviews in research, student theses or journalism, that is often consent under Art. 6(1)(a) GDPR. Obtain it before you record and document it. Which basis applies in your case is a question for your data protection officer. This is not legal advice.

What should an interview consent form include?

The purpose of the interview, that it will be recorded and transcribed and by whom or what, where the recording and transcript are stored, who has access, when data is deleted, how it is anonymised, that consent can be withdrawn at any time, and who to contact. Use your university's template where one exists.

Can I use a cloud service to transcribe interviews?

In principle yes, if your consent form covers it and you have a data processing agreement with the provider under Art. 28 GDPR. Also check the processing location, the sub-processors and any transfers outside the EU. If you transcribe on your own servers, those questions do not arise.

What is the difference between anonymisation and pseudonymisation?

Pseudonymisation replaces names and identifiers with codes and keeps the key separately, and the data remains personal data. Anonymisation means the person can no longer be identified by any reasonably likely means. Such data falls outside the GDPR. With qualitative interviews, true anonymity is hard to achieve.

Ready to See Scriber on Your Own Servers?

Tell us about your infrastructure and workload, and we will answer with a concrete recommendation.