Data Access and Deletion Requests: Handling Call Data Under GDPR
How to handle requests to see or erase personal data held in call recordings, transcripts and logs: verification, searching, timing, exceptions and records.

A caller phones your support line, and weeks later writes to ask for everything you hold about them, or asks you to delete it. For a contact centre this is not a rare edge case; call data is spread across recordings, transcripts, logs and notes, and finding it all takes planning. This guide describes how to prepare for and handle such requests. It builds on GDPR and Call Recording and Data Retention for Call Data.
The rights people can use
The GDPR gives people a set of rights over their data. Three come up most often with calls.
Rights most relevant to call data
- AccessA person may ask whether you hold data about them, and receive a copy and certain information about how you use it.
- ErasureIn some circumstances, a person may ask you to delete their data; it is not an absolute right.
- RectificationA person may ask you to correct data that is inaccurate.
- ObjectionA person may object to processing based on legitimate interests or marketing.
- RestrictionA person may ask you to pause some uses while a dispute is resolved.
- PortabilityIn limited cases, a person may ask for data they supplied in a usable format.
Requests do not have to use special words or a form. A customer who writes "please delete my recordings" or says it to an agent has made a request. Train front-line staff to recognise one and pass it on the same day.
Receiving and verifying a request
From request to confirmed identity
- Log itRecord the date received, the channel, who asked and exactly what they asked for.
- AcknowledgeTell the person you have it, and how long you expect to take.
- Verify identityConfirm the person is who they say. Ask only for what you need, and use details you already hold where you can.
- Clarify scopeIf the request is broad, you may ask what they mean, but the clock may not stop for long.
- Open a fileAssign an owner, a due date and a place to keep notes and decisions.
Be careful with phone numbers. A person asking about "the calls from my number" may share a number with others, and call data often involves two people. Verify that the requester is the account holder, and be ready to remove or redact other people's details before you disclose anything.
How long you have
The standard deadline is one month from receiving the request, which can be extended by up to two further months for complex or numerous requests if you tell the person within the first month. In practice, start as soon as the request arrives; searching call systems takes longer than you expect. Treat the deadline as a calendar commitment and check what your national law says on counting time.
Finding call data
Call data lives in more places than the recording. Make a map of your systems before the first request arrives and keep it up to date.
| Where to look | What may be there |
|---|---|
| Call recordings | Audio of the call, possibly several calls over time |
| Transcripts and summaries | Text of what was said, AI-generated summaries, topic labels and sentiment scores |
| Call logs | Numbers, dates, durations, queue, agent and outcome |
| Voicemail and callbacks | Messages, transcripts and requested call-back times |
| CRM and ticket records | Notes, tags, follow-ups and linked contacts |
| Messages and email | Follow-ups sent after the call |
| Quality reviews and coaching files | Scores and notes about the call that name the caller |
| Backups and exports | Copies kept for disaster recovery or reporting |
Responding to an access request
An access response normally includes a copy of the personal data and supporting information: why you process it, who receives it, how long you keep it, and the person's other rights. For recordings, you may provide the audio or a transcript, depending on what the person asks for and what is practical.
- Redact or withhold information about other people, such as the agent's personal details where appropriate, or another customer on a shared line.
- Deliver the response in a way that does not create new risk, such as an encrypted link, not an open email attachment.
- Explain anything you are not disclosing and the exemption you relied on.
- Keep a copy of exactly what you sent.
Responding to an erasure request
Erasure is not automatic. You must delete the data when a valid ground applies, such as when it is no longer needed or the person withdraws consent and there is no other basis. You may refuse where you must keep the data to comply with a legal obligation or to establish, exercise or defend legal claims. Many call-centre records have legitimate retention reasons, such as financial records or an ongoing complaint, so check each class of data.
Delete or keep?
| Often deletable | Often retained, with a reason | |
|---|---|---|
| Examples | Marketing call recordings, quality-review recordings past retention, optional transcripts | Records tied to a contract or payment, regulatory records, evidence in a live dispute |
| Action | Erase from live systems and plan the backup cycle | Keep only what is needed, restrict use, tell the person |
| Tell the person | What was deleted and when | What you kept, why and when it will go |
Do not forget backups and copies. You may not be able to remove an item from an archive at once, but you should put it beyond use and make sure it is deleted when the backup expires. Also record the person's number on a suppression list if they have asked not to be called, because deleting everything could make you forget they refused contact.
Records, training and improvement
Make requests routine
- A named owner and a deputy for data requests
- A request log with dates, decisions and evidence
- A map of every system that holds call data
- Templates for acknowledgement, access response and refusal
- Training for agents on recognising and passing on a request
- Retention periods set so there is less to search and less to delete
- A review after each request to improve the process
A hypothetical walk-through
Suppose a customer emails a support team: "Please send me everything you have about my calls, and delete my recordings." The team lead logs the email, replies the same day, and verifies identity by asking the customer to confirm details that match the account. They search by phone number and customer ID across recordings, transcripts, call logs, voicemail and ticket notes.
Two recordings fall within the retention period and have a quality-training purpose; one call relates to an open complaint. The team prepares an access pack for the customer, deletes the training recordings, and explains that the complaint recording will be kept until the dispute closes, after which it will be removed. The log records each decision and who made it. The process is not complicated, but it depends on knowing where the data is.
Good retention practice makes requests easier: data you no longer hold needs no search. Data Minimisation in Support and Why Audit Logs Matter help keep the load manageable.
Handling requests in Call
Call has a Data requests tab under Governance. Choose the type, access or erasure, enter the person's phone number and open the request. When ready, press Fulfil: an access request produces a subject access pack, and an erasure asks you to confirm first because it cannot be undone. The Retention tab shows how long each class of data is kept and what is due for removal, which keeps future searches smaller. A suppression list keeps a number from being called again. See Call Recording Playback in Call and Opt-Out Management for related tasks. Always review the pack and apply your own checks before sending it.
Frequently asked questions
How long do I have to respond to an access request?
Generally one month from receipt, with a possible extension of up to two months for complex cases if you tell the person in time. Check your national rules.
Do I have to provide call recordings in response to an access request?
Recordings of the person are personal data, so they are usually in scope. You may provide the audio or a transcript, and you should protect other people's information.
Can I refuse a deletion request?
Sometimes. You may keep data you must hold by law or need to establish or defend legal claims. Tell the person what you kept and why.
Do I need to delete data from backups?
You should ensure it is not used and is deleted when the backup cycle allows. Document how backups are handled.
Can I charge for a request?
Normally not. Fees apply only in limited cases such as manifestly unfounded or excessive requests; check official guidance first.
What if the request comes by phone?
It still counts. Take the details, log the request and confirm in writing if you can, then follow the same process as for any other request.