---
title: GDPR Call Recording
seoTitle: GDPR Call Recording for Microsoft Teams
description: Record calls under GDPR and UK GDPR with Argus Archive. Choose who is recorded, delete recordings on schedule, answer access requests and keep data in the EU.
subnav: true
finished: true
---

> [!herorow]
> GDPR
>
> # GDPR call recording *with the controls built in*
>
> Record only the calls you need, keep them only as long as you should, and find a person's calls when they ask for their data.
>
> [Get a demo](/request-a-demo/)
>
> ![A recorded meeting playing back in Argus Archive, with its video and screen share, speaker-labeled transcript, AI summary and keywords](/media/uploads/2026/10/29-meeting-transcript.jpg)

> [!grid]
> Principles
>
> ## What GDPR asks of call recording
>
> Recording a call is processing personal data. GDPR and UK GDPR allow it when there is a clear reason, people are told, the data is kept safe and it is deleted when the reason ends. This is general information, not legal advice.
>
> ### A lawful basis
>
> Each recording needs a reason the law accepts, such as a legal duty to record or a legitimate interest.
>
> ### Clear notice
>
> People on recorded calls are told that the call is recorded and why.
>
> ### Only what you need
>
> Only the people and calls your purpose covers are recorded.
>
> ### A set retention period
>
> Recordings are deleted when the reason to keep them ends, unless a legal hold applies.
>
> ### Kept secure
>
> Access control, encryption and an audit trail protect each recording.
>
> ### Rights respected
>
> People can ask for a copy of their recordings, so every call they were on needs to be found.

> [!faq]
> FAQ
>
> ## GDPR call recording questions
>
> Still have questions? Ask the team that built it.
>
> [Talk to us](/contact/)
>
> ### Can we record only some people?
> Yes. You choose which users and groups are recorded.
>
> ### How do we find a person's calls for an access request?
> Search by participant across calls and meetings, then export the recordings and transcripts you need.
>
> ### What happens when a retention period ends?
> Argus Archive deletes the recording automatically, unless it is under a legal hold.
>
> ### What does the AI do with our calls?
> It transcribes calls and checks them against the rules you write, using AI models hosted in the EU. Your data is never used to train AI, and there is no emotion or voice recognition.
>
> ### Where is our data processed and stored?
> On Microsoft Azure in the European Union. Each customer has its own database and storage container.

> [!security]
> Controls
>
> ## How Argus Archive helps
>
> ![](/assets/icons/callrec-icon-internal-calls.png)
>
> ### Choose who is recorded
>
> Record only the users and groups your purpose covers.
>
> ![](/assets/icons/callrec-icon-retention-hold.png)
>
> ### Delete on schedule
>
> Retention policies delete recordings when their period ends, and a legal hold pauses deletion.
>
> ![](/assets/icons/callrec-icon-responsible-ai.png)
>
> ### Only the side that matters
>
> Each rule checks your staff, the customer or both, and only for the people it is assigned to.
>
> ![](/assets/icons/comprec-icon-role-access.png)
>
> ### Access by role
>
> People see only the calls their role allows, and the audit log records who viewed or changed a recording.
>
> ![](/assets/icons/callrec-icon-eu.png)
>
> ### Processed and stored in the EU
>
> Recordings are processed and stored on Microsoft Azure in the European Union, and transcripts come from AI models hosted in the EU.
>
> ![](/assets/icons/callrec-icon-export.png)
>
> ### Answer access requests
>
> Search for a person across calls and meetings, and export what they ask for.

> [!articles]
> Articles
>
> ## Worth reading
>
> GDPR, recording rules across the EU, and choosing who to record.
>
> - /blog/gdpr-call-recording-in-2026/
> - /blog/telephone-call-recording-and-gdpr-understanding-the-rules-across-the-eu/
> - /blog/microsoft-teams-native-recording-vs-policy-based-compliance-recording/