Can we analyse customer calls without keeping every recording forever?

In this guide

• A recording, a transcript and a weekly report need separate decisions
• Write down the purpose before choosing a number of days
• Ask what “deleted” means at each provider
• What Call Nerd currently does
• Use a staged call to check the promised lifecycle
• Give each retained copy an owner

THE SHORT ANSWER

Yes, call analysis can use audio temporarily and retain reviewed transcripts or findings for a different period. Define the purpose, access, deletion trigger and exception process for each copy. Deleting a recording does not delete its transcript, provider copies, emailed reports or backups, and shorter retention does not remove recording or data-processing obligations.

You may want to know what customers keep asking without building a permanent library of their voices. Those are separate requirements. Audio can be an input to analysis rather than an archive you keep indefinitely.

Start by mapping the copies that exist. Then decide what each is needed for, who can access it and how its removal is checked. Download the call-data retention worksheet to use with a supplier or your own operator.

A recording, a transcript and a weekly report need separate decisions

A typical workflow creates several records:

Phone recording → processing copy → transcript → extracted questions → report.

External services, exports and backups can add more copies. Removing one does not establish that the others are gone. A transcript can still identify a customer through names, addresses, order details or the conversation itself. A report containing call references or quotations also needs a purpose and an access boundary.

On a small screen, swipe the table to see all columns.

Record	What it might be needed for	What to establish
Pending audio on the phone	Retry an upload that has not succeeded	Upload acknowledgement, local cleanup and failed-upload ownership
Audio in processing storage	Finish or retry transcription and analysis	Completion trigger, deletion result and unresolved failures
Transcript and translation	Review the wording behind a finding	Review period, access and deletion process
Questions and analysis	Find recurring issues and prepare decisions	Whether identifying detail is necessary and when findings expire
Provider-held copies	Deliver the selected speech or AI service	Exact endpoint, account controls, deletion scope and exceptions
Reports, exports and backups	Management review or recovery	Recipients, copy locations, expiry and restore procedure

This is a planning map, not a recommended legal schedule. The period appropriate for a temporary processing file can differ from the period needed for a complaint record or an approved business record.

Write down the purpose before choosing a number of days

“We might want it later” is a weak operating rule. A more useful question is: what specific task would become impossible if this record were removed?

For example, you may need the transcript long enough to check a recurring question and revise an answer. Keeping the original sound for voice-quality review is a different purpose. A dispute requiring original audio is another requirement that needs to be planned explicitly before choosing a system that cleans it up.

For UK organisations, the ICO's storage-limitation guidance explains that UK GDPR does not prescribe one universal period for every kind of personal data; retention needs justification against its purposes. That is a UK-specific source, not a worldwide retention rule. Check the rules, contracts and recording requirements that apply to your business before adopting a schedule. This guide provides operational questions, not a compliance determination.

Ask what “deleted” means at each provider

These questions are more useful than a broad “Is your AI private?”:

• Which services receive the audio, transcript and derived output?
• Does the account use stored responses, request logs, temporary uploads or model-improvement data sharing?
• What does a deletion request remove, and what has its own lifecycle?
• Does a time-to-live start deletion or guarantee that deletion is already complete?
• Which exceptions, regions and account approvals apply to the actual processing route?

AssemblyAI's production-retention documentation distinguishes uploaded audio from final transcription artifacts. Its asynchronous and streaming routes also have different retention arrangements. Deleting a transcript is therefore not enough evidence to make a blanket promise about every provider-held copy or training use. Check the configured asynchronous route and the account's data-sharing settings.

OpenAI's API data-controls documentation separates application state from abuse-monitoring logs. Setting store: false on a Responses request is not the same as obtaining approved Zero Data Retention controls. Endpoint features, model-specific limitations and the effective organisation/project settings matter. The API policy is separate from what happens when someone pastes a transcript into a consumer chat product.

Check the live account settings as well as the published policy. A product's request flag cannot prove that your organisation has a particular provider approval.

What Call Nerd currently does

We make Call Nerd. The following describes the product source reviewed on 13 October 2026; it is not an inspection of a particular customer's running deployment.

1. The phone keeps pending recordings until upload succeeds. Offline, retrying and failed recordings remain available locally. A successful upload starts local cleanup; a failed local deletion can remain pending and retry.
2. The server keeps audio while processing needs it. Incomplete or failed processing retains the source. After the transcript and analysis are committed, a durable cleanup worker deletes the source audio and clears its stored path. Cleanup failures retry, so completion does not mean an instantaneous purge.
3. Transcripts and analysis remain for review. Successful source-audio cleanup does not erase them. The current product does not supply a general age-based expiry setting for those retained call records; agree an operator-run retention and deletion process before live use. A per-call deletion workflow exists and is asynchronous.
4. External providers process the content. AssemblyAI receives audio for transcription, and OpenAI receives transcript content for analysis. Call Nerd requests provider-transcript deletion and sets store: false for OpenAI analysis. Provider retention still needs the separate checks above.
5. Reports and recovery copies need their own handling. Configured email reporting can send findings and CSV attachments outside the dashboard. An already-delivered report is a separate copy; deleting a call does not recall an email or clean up an operator's backup.

The dashboard has no source-audio player. A completed call can be analysed again from its retained transcript, but retranscription requires the audio to be supplied again. If long-term playback or original-audio evidence is essential, establish that requirement before choosing this workflow.

Use a staged call to check the promised lifecycle

Run a test with consenting colleagues and fictional customer details. Record what you observed for each step rather than treating one successful upload as a complete privacy test.

Test call reference / date:
Phone copy: pending → upload acknowledged → removed or cleanup pending
Processing copy: active → processing committed → removal confirmed
Failure case: retained source / owner / next review
Provider transcript: deletion requested / observed result / remaining limits
Retained transcript and findings: access / deletion workflow checked
Report or export copies: locations / recipients / removal responsibility
Backup restoration: how expired or deleted records stay excluded
Unknowns and responsible owner:

Have the operator verify storage and provider receipts; a missing dashboard player is not evidence of deletion. Review a failed-processing case as well as a successful one so the team knows who resolves retained audio. If a test result cannot be observed, mark it unknown and ask for evidence rather than guessing.

Give each retained copy an owner

For every row in the worksheet, record a purpose, access group, deletion trigger or review date, exception owner and evidence of completion. Include exported files and reports that have left the system. Plan what happens when a backup is restored so already-deleted records are not quietly returned to use.

You can keep useful operational evidence without treating every recording as a permanent asset. The practical decision is which evidence your team needs and whether the complete processing and deletion workflow meets that need. For the reporting task itself, use the one-page weekly call brief; for product selection, compare the recording routes and pilot checks.