Rules and compliance

Call Data Retention and Backups: What to Keep and for How Long

How to decide what call data to keep: recordings, transcripts and logs, retention periods, deletion, backups, access requests and a sample schedule.

Call editorial team · Published · 5 min read

Phone systems accumulate data quickly: audio, transcripts, summaries, call logs, voicemails, notes. Left alone, the pile grows until nobody knows what is in it, who can see it or why it was kept. A retention schedule fixes that by deciding in advance how long each type is kept and what happens at the end. This guide shows how to build one and how backups fit in.

A records manager reviewing a retention schedule at a desk with filing shelves
Illustrative image

Start with purpose

The central idea is simple: keep personal data for no longer than you need it for the purpose you collected it. So the first question is not "how long can we keep it?" but "why do we have it?" Typical purposes are handling the customer's request, quality and training, resolving disputes, meeting legal or financial record-keeping duties and improving the service. Each has a natural length.

Data minimisation reinforces this: do not collect or keep more than you need. And personal information on calls shows what counts as personal data.

Sort your data into classes

Data classWhat it isQuestions to ask
RecordingsAudio of the callWhy record? Who may listen? How long is a dispute likely to arise?
TranscriptsText of what was saidDo they hold more than needed? Can sensitive parts be masked?
Call logsTime, number, duration, outcomeNeeded for billing, reporting and security?
Summaries and notesShort records written or generated after callsDo they replace the need to keep the recording?
VoicemailMessages left by callersIs it dealt with and then deleted?
ExportsFiles downloaded for analysisWhere are they stored, and who deletes them?

Different classes need different treatment. A call log may serve billing and reporting for a long time, while a recording is more intrusive and is usually kept for a shorter time. A summary might let you delete the recording sooner.

Choose periods you can defend

There is no single right answer. Consider the legal minimum, if any; the practical window in which problems appear, such as a dispute or complaint; the sensitivity of the data; and the cost and risk of holding it. Write down the reasoning, because you may need to explain it to a customer, an auditor or a regulator.

Setting a retention period

  1. Identify the purposeWhy does this data exist?
  2. Check obligationsIs there a legal or contractual minimum or maximum?
  3. Estimate the useful windowHow long might you realistically need it?
  4. Pick a period and an end actionDelete, anonymise or archive.
  5. Write it downRecord the period, reason, owner and review date.

Deleting properly

A schedule is only real if deletion happens. Automate it where you can, with a regular purge that removes data past its period. Test it first with a dry run that counts what would be removed, because deletion is permanent. Record when purges run and how many items were removed. Exports and downloaded files are easy to forget, so include them in the schedule.

Backups and deletion

Backups protect you against loss, but they keep copies of what you have deleted. That does not make deletion pointless; it means you must understand how long backup copies live and how they are removed. Ask your provider, or check your own arrangements, how backups are taken, how long they are kept, where they are stored, who can restore them and what happens to deleted records when a backup is restored.

Live data vs backup copies

Live systemBackup copy
PurposeDay-to-day useRecovery after loss or failure
Who accesses itStaff with permissionFew, usually administrators
DeletionImmediate when purgedFalls away when the backup expires
RiskOver-retentionForgotten copies that outlive the schedule

Treat backup retention as part of the schedule. A common approach is to keep backups for a limited, stated time, and to make sure that restoring one does not quietly bring back data that should have been erased. If a customer asks you to erase their data, be ready to explain what happens to backup copies.

Access and erasure requests

People may ask to see the data you hold about them, or to have it erased. The rules vary, but the practical needs are similar: you must be able to find everything about a person, usually starting from a phone number, assemble it and, where erasure applies, remove it. A well-organised schedule makes this much easier, because there is less data in fewer places. See data subject requests on calls for the EU and UK picture.

Control who can see what

Retention is about time; access is about people. Fewer people should see recordings than see call logs. Record who plays recordings, use roles rather than shared logins and review the list of people with access every few months. Access controls for contact centres and why audit logs matter explain the practice.

A schedule you can adopt

The example below is hypothetical and deliberately has no numbers, because the right periods depend on your sector, your country and your risks. Fill in the periods after you have taken advice.

Data classKeep forThenOwner
RecordingsShortest period that covers quality review and disputesDeleteHead of quality
TranscriptsSame as recordings, or shorter if maskedDeleteHead of quality
Call logsPeriod needed for billing and reportingDelete or anonymiseOperations manager
Summaries and notesPeriod needed for service historyDelete or archiveTeam leads
VoicemailUntil dealt with, plus a short bufferDeleteTeam leads
ExportsUntil the task is doneDeleteWhoever created them

Retention review checklist

  • Every data class has a purpose, a period and an owner
  • Deletion is automated or scheduled
  • A dry run was done before the last purge
  • Backup retention is known and documented
  • Access and erasure requests can be answered quickly
  • Access to recordings is limited and reviewed
  • Schedule reviewed in the last year

Doing it in Call

In Call, the Governance area shows a retention schedule with each data class, how long it is kept, what is due for removal, the last purge and how many records have been removed. The platform operator can change the days kept and run a dry run before a purge; a purge cannot be undone. Transcripts are kept only as long as the transcript retention rule, and turn-by-turn conversations are kept for a limited time. Data requests, for access or erasure, are recorded and fulfilled from the same area, and calls can be exported to a spreadsheet for your own records. Recording rules are set by an operator, and with no rule in place every call is recorded, so check them. Ask your administrator about backups for your workspace.

Frequently asked questions

How long should I keep call recordings?

As short as your purpose allows. Consider legal duties, the window in which disputes appear and the sensitivity of the data, and write down your reasoning.

Do transcripts need the same period as recordings?

Not necessarily. Transcripts may be easier to search and mask, but they still hold personal data. Decide a period for them on purpose.

What about backups?

Backups keep copies of deleted data until they expire. Know how long yours live and how restoring one affects data that should have been erased.

Can I delete data when someone asks?

Often, but rules differ and some data must be kept for legal reasons. Record the request, check exceptions and remember that erasure is permanent.

Who should own the schedule?

Name one accountable person, usually in operations, quality or compliance, with a review date at least once a year.

Is a dry run really necessary?

Yes. Purges are permanent, and a dry run shows how many records would be removed before you commit.

Review your retention schedule in Call

In the demo console you can try incoming calls in a simulation.

Related guides