GDPR and Call Recording: Practical Basics for Phone Teams
What the GDPR means for recording customer calls: lawful basis, telling callers, retention, access, security, pausing for payments and a working checklist.

Recording calls helps with training, quality checks, disputes and evidence. It also captures voices, names, account details and sometimes sensitive remarks. Under the EU General Data Protection Regulation (GDPR), a recording of an identifiable person is personal data, and the rules for handling it apply from the moment you press record. This guide covers the practical points phone teams usually need to settle. For the wider picture of consent laws, see Call Recording Consent and Two-Party Consent and Recording.
The principles that apply
The GDPR sets out principles that shape every recording decision. Each one translates into a question your team can answer.
GDPR principles in call recording
- Lawfulness, fairness, transparencyDo you have a valid basis, and do callers know they are being recorded?
- Purpose limitationAre you using recordings only for the reasons you stated?
- Data minimisationDo you record only the calls and parts you need?
- AccuracyCan you correct or annotate records that are wrong?
- Storage limitationDo recordings have a defined end date?
- Integrity and confidentialityAre recordings protected and access limited?
- AccountabilityCan you show your decisions and reasons?
Choosing a lawful basis
Article 6 of the GDPR lists the bases for processing personal data. For call recording, three come up most often.
Common bases for recording
| Consent | Legitimate interests | Legal obligation | |
|---|---|---|---|
| Idea | The caller freely agrees to be recorded | You have a real business need that does not override the caller's rights | A law requires you to record or keep records |
| Typical use | Optional recordings, marketing, research | Quality, training, fraud prevention, dispute handling | Some regulated sectors such as financial services |
| Strengths | Clear and respectful when genuinely optional | Flexible, no need to ask for a yes | Strong for the specific records required |
| Watch out for | Must be freely given and easy to withdraw; "stay on the line" is a weak form of consent | Needs a written balancing test and an easy way to object | Applies only to what the law actually requires |
Many teams rely on legitimate interests for quality and training recordings, backed by a short assessment that weighs the benefit against the effect on callers. If you plan to record sensitive categories of data, such as health details, extra conditions apply. Take advice before recording in those settings.
Telling callers
Transparency is a firm requirement. Callers should hear, at the start of the call, that it may be recorded, why, and where to find more detail. Keep the announcement short and the fuller explanation in your privacy notice.
A transparent recording notice
- Announce early"Calls may be recorded for training and quality purposes." Say it before the conversation begins.
- Point to detailMention where to read how long recordings are kept and how to exercise rights, such as a web page.
- Offer a choice where it mattersIf recording is optional, give a clear way to decline, and make sure the call can continue.
- Cover outbound callsAgents should say the same at the start of calls they make.
- Match the notice to the practiceDo not announce recording for one purpose and use it for another.
Retention, access and security
- Retention: set a fixed period per purpose, and delete automatically when it ends. Keeping everything "just in case" is hard to justify.
- Access: restrict listening to people who need it, such as supervisors and trainers, and log who plays what.
- Security: use access controls, strong credentials and protected storage; the GDPR requires appropriate technical and organisational measures. See Access Controls in a Contact Center.
- Processors: if a supplier stores or transcribes recordings, you need a written agreement that meets the GDPR's requirements for processors.
- Transfers: check where recordings and transcripts are stored and whether they leave your region; special rules apply to some transfers.
- Individual rights: people can ask for access to, or deletion of, recordings of them. Handling Data Access and Deletion Requests for Call Data covers the process.
Sensitive moments: payments and special categories
Some parts of a call should never be captured. Card details are the clearest example: payment card rules generally forbid storing security codes, and recording them creates risk. Many teams pause recording when the caller reads out card information, or send callers to an automated payment line. See PCI and Phone Payments. Health, religious or similar details can also be special category data; avoid recording them unless you have a documented reason and extra safeguards. HIPAA Phone Basics discusses a related US regime.
Other laws also apply
Data protection is only one layer. Many countries have laws on intercepting communications, and some require the consent of everyone on the call. In the UK, business recording rules sit alongside data protection law. The rules differ by country and by call type, so check the laws of every place your callers are, not only where your office is. Recording an AI-handled call may also trigger disclosure expectations; see AI Disclosure on Calls.
What a short balancing assessment covers
If you rely on legitimate interests, a brief written assessment protects you and focuses your thinking. It does not have to be long. It should answer three questions: what is the benefit and who gets it, is recording necessary to achieve it, and what is the effect on callers once safeguards are in place?
- Purpose: for example, checking that advice was accurate, training new agents or settling disputes.
- Necessity: could a sample of calls, call notes or a summary do the job instead of full recordings?
- Impact: callers do not expect recordings to be used for unrelated purposes; weigh the effect of listening, storing and sharing.
- Safeguards: announcements, short retention, limited listening access and a way to object.
Review the assessment when the purpose changes, for example when you add automated transcription or start using recordings to train a system. New uses may need fresh thinking and updated notices.
A practical GDPR checklist for recording
- Purpose written down for each type of recording
- Lawful basis chosen and, for legitimate interests, a short assessment on file
- Opening announcement in place for inbound and outbound calls
- Privacy notice explains recordings, retention and rights
- Retention period set and enforced automatically
- Access limited and logged
- Supplier agreements in place
- Pause or skip process for card details and sensitive information
- Process for access and deletion requests
- Review date set
Controlling recording in Call
Call gives you several controls that map onto these steps. A queue can play a recording announcement to the caller before the call is connected, and each phone line has a monitoring notice setting: the default says it where recording needs consent, or you can choose always or never. The platform operator can set what gets recorded, choosing every call, none or a sample, for a queue, campaign or agent, and with no rules every call is recorded, so set rules deliberately. A Governance page shows the retention schedule, with what is due for removal, and the recording-consent rule applied by country. Playing recordings is limited to owners and administrators. See Call Recording Playback in Call for the day-to-day side and Data Retention for Call Data for planning retention.
Frequently asked questions
Do I need consent to record calls under GDPR?
Not always. Consent is one lawful basis, but many businesses rely on legitimate interests or a legal duty. Whatever you choose, you must be able to explain it and tell callers about the recording.
Is saying "calls may be recorded" enough?
It is a good start, but transparency also means explaining the purpose and where to find more detail, such as in your privacy notice. The announcement must match what you really do with the recordings.
How long can I keep call recordings?
As long as you need them for the stated purpose, and no longer. Set a fixed period for each purpose and delete automatically afterwards; there is no single number that suits every business.
Can customers ask for their recordings?
Yes. People have a right to access personal data about them, which can include recordings and transcripts, and sometimes a right to have it deleted. You should be ready to find and provide or remove them.
Should I record payment card details?
Generally no. Pause recording or use an automated payment method. Card rules and the GDPR both point towards not storing sensitive payment data.
Do these rules apply to calls with people outside the EU?
The GDPR can apply based on where people are and who you target, and other countries have their own laws. Check each market you serve or take advice.