How to Record Job Interviews Online in a GDPR-Compliant Way

If you want to record job interviews online and stay on the right side of GDPR, the work is mostly process, not technology. Recording is useful: it lets a second interviewer review a candidate without sitting through every call, reduces note-taking burden during the conversation, and gives a more honest picture than memory does a week later when the shortlist comes together.

It also creates real obligations. The candidate is a data subject, the recording is personal data, and your hiring process is the controller. The good news is that a clean workflow takes care of those obligations without making the candidate feel surveilled.

GDPR requires a lawful basis for processing personal data. For interview recordings, the most defensible options are usually explicit consent or legitimate interest, depending on how core the recording is to your hiring process and how you mitigate impact on the candidate.

• Lawful basis: pick one, document it, and apply it consistently across candidates rather than ad hoc
• Transparency: tell candidates clearly before the interview that the call will be recorded, why, who will see it, and how long it will be kept
• Data minimization: record only what you need; do not retain video if audio is sufficient for review
• Retention: define a fixed retention period (often 90 to 180 days post-decision) and actually delete on schedule
• Right to access and erasure: candidates can ask for a copy of their recording or for it to be deleted; have a process to handle both
• Security: store recordings somewhere access-controlled, not in a shared drive everyone in the company can browse

The most respectful and the most compliant version of this overlap almost entirely: tell candidates exactly what is happening, before the interview, in writing.

1. 01

   In the interview invitation

   Include one short paragraph explaining that the interview will be recorded, the purpose (typically: enabling other interviewers and the hiring manager to review), who has access, and how long it will be retained.

2. 02

   Link to your candidate privacy notice

   The invitation should link to the privacy notice that covers recruitment processing. Make sure that notice actually describes recording, the lawful basis you use, and candidate rights.

3. 03

   Reconfirm at the start of the call

   When the candidate joins, briefly confirm that you will start recording and ask if they have any questions about it. Press record only after that confirmation.

4. 04

   Make refusal real

   If a candidate prefers not to be recorded, have a fallback: a non-recorded interview with structured notes. The candidate should not feel that refusing the recording costs them the role.

Some interview recording tools require the candidate to install software, create an account, or grant intrusive permissions on their machine. That is a poor experience and it makes consent feel coerced. A browser-based recorder removes that friction.

• No installation: the candidate joins from a single browser link without downloading anything
• No account: the candidate is not asked to sign up for a vendor's product just to have a conversation with you
• Local recording: each side records on their own device so a flaky candidate connection does not destroy the source file
• Separate audio tracks: useful when a second interviewer wants to re-review only the candidate's responses
• Searchable transcript: lets reviewers jump to specific answers without re-watching the full session

Airtape fits this shape: browser-based, no install, no candidate account, separate tracks, transcription on request with a monthly allowance. Hosting and infrastructure details should always be validated against your own DPA and data protection requirements before adoption.

Policies are easy to write and hard to operate. The retention and deletion part is where most teams quietly fail. A simple, boring system you actually run beats an elaborate one you do not.

• Pick a single retention window and apply it to every interview recording, with a defined extension only for active disputes or open legal matters
• Schedule deletion: put the deletion task on a recurring calendar or, better, use the tool's automatic deletion if supported
• Limit access by role: hiring manager, interviewers on that loop, and HR, not the wider team
• Log access if your tool supports it, so you can answer subject access requests honestly
• When a candidate asks for deletion or a copy, treat it as a real request with a clear response time, not a casual email

Compliance is the floor. The ceiling is whether the candidate walks away thinking your company is thoughtful or surveillance-y. The difference is mostly in tone and clarity.

• Acknowledge the recording in plain language at the start, then forget about it; do not keep referencing it through the call
• Do not record warm-up small talk if it is not part of the decision; start the recording when the structured portion begins
• Offer the candidate the option to receive a copy of their own recording on request
• If you reject the candidate, do not retain the recording beyond your defined window even if you think they might reapply
• Train every interviewer on the script so candidates get the same experience regardless of who they meet first