Subject Access Requests: Retrieving and Redacting Call Recordings
The email arrives on a Tuesday: the sender wants a copy of every call the company holds about them. It reads like a customer complaint, but it is a legal request with a deadline attached, and the answer depends on whether anyone can find the calls, isolate them, and remove the parts that belong to other people.
The Request Is Easy. The Retrieval Is Not
Most organisations can describe their recording retention policy. Far fewer can produce a specific caller's calls within a month. The gap appears because recordings are indexed by time and extension, not by caller. A number that called in and was transferred three times may appear under three different internal legs, plus a queue recording, plus an outbound callback logged against a different extension entirely.
The first design decision is therefore about search keys. If the platform can search by calling number, the request becomes a query. If it cannot, the work becomes a listening exercise across a date range, and the cost of compliance rises with every request.
| Search key | Reliability | Practical note |
|---|---|---|
| Calling number | High when the caller used one consistent line | Fails for withheld numbers and for calls from a switchboard |
| Account or reference number | High if captured by IVR or agent | Requires the field to be stored with the recording, not just in the ticket |
| Date and time window | Moderate | Useful as a filter, not as an identifier |
| Agent extension | Low as an identifier | Useful only after the caller's calls are narrowed |
| Name spoken in the call | Low | Requires transcription and still needs human review |
Identity Before Content
Before any recording is released, the requester's identity has to be established to a standard proportionate to the sensitivity of the data. A voice recording is more identifying than a transaction list: it carries tone, accent, and background. A common failure is to release quickly because the request feels administrative, when the correct sequence is to verify first and then search.
Redaction Is the Hard Part
A call between two people contains two people's data. Releasing the whole recording to one of them discloses the other's voice, name, and circumstances. The workable approach is to identify the requester's own contributions and the information about them, then remove or mute the remainder. In practice this means a listening pass with timestamps, and a redacted copy that is audibly discontinuous rather than silently edited.
- Log the request date, because the response clock starts there
- Verify identity proportionately and record how it was done
- Search by calling number first, then by reference, then by date
- Listen to every candidate recording before release
- Mute or remove third-party personal data and note the timestamps
- Deliver in a format the requester can actually use, with a written index
- Keep a copy of what was released and why, for the next request
What Most Requests Actually Reveal
In practice the request is rarely about the recording. It is about a dispute: a refund refused, a service not delivered, a promise allegedly made. Releasing the recording often resolves the dispute faster than the internal process would have, which is an argument for making retrieval routine rather than treating each request as a crisis. The organisations that handle these well have run the exercise once, deliberately, and written down what they learned.
Redstone Approach
Redstone voice platforms retain call detail records alongside recordings, with search by calling number, date range, and extension, so a request can be narrowed before anyone listens. Recording permissions are assigned per role, and retrieval is logged, which gives the audit trail that a response to an access request should be able to cite.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.

Current Location :

