POPIA-compliant call recording in South Africa: the 2026 checklist
Recording business calls is legal in South Africa, but only if you satisfy two laws, not one. Here is exactly what POPIA and RICA require, and a seven-step checklist to get compliant.
Is call recording POPIA compliant in South Africa?
Yes, if you satisfy both laws. RICA lets you record a call you are a party to and monitor business calls, provided you tell people. POPIA then requires a lawful basis (consent, contract or legitimate interest), a stated purpose, secure storage, a retention limit and the ability to honour a caller’s access or deletion request. Announce recording on every line, document your basis per call type, and enforce a deletion schedule.
Two laws, not one, govern a recorded call
Most South African businesses treat call recording as a POPIA question. It is actually governed by two laws working together, and missing the second is the most common mistake we see.
RICA (the Regulation of Interception of Communications Act) treats recording a call as an interception of a communication. The good news: RICA lets you record a call you are a party to, and lets a business monitor its own calls, as long as you take reasonable steps to inform people. POPIA (the Protection of Personal Information Act) then governs the recording itself as personal information: you need a lawful basis to hold it, you must keep it secure, you cannot keep it forever, and the caller has rights over it. Get RICA right and you may lawfully make the recording. Get POPIA right and you may lawfully keep and use it. You need both.
The lawful recording chain
A recording that fails any one of these links is a liability, not an asset. The point of this page is to make every link easy to satisfy.
Your lawful basis: consent is one option, not the only one
POPIA section 11 lists the grounds for processing personal information. For call recording, three are practical, and consent is not always the strongest.
Consent is the ground everyone reaches for first, and the recorded announcement (“this call may be recorded for quality and training”) plus the caller staying on the line is the usual way it is given. It works, but it is fragile: a caller can withdraw consent, and a purely consent-based model struggles when someone objects but you still need the recording for a dispute.
Performance of a contract covers recordings that are genuinely necessary to deliver or prove a transaction, common in financial services and debt collection where the call itself is the agreement. Legitimate interest covers recording for quality assurance, training, fraud prevention and dispute evidence, provided that interest is real and is not outweighed by the caller’s privacy. For most contact centres a documented legitimate-interest assessment, backed by a clear announcement, is more robust than consent alone. Whichever ground you choose, the rule is the same: decide it deliberately, per call type, and write it down.
What compliant recording actually requires
Six requirements turn a pile of audio files into a defensible, POPIA-ready recording programme. None of them needs new software; they need decisions and enforcement.
| What the law wants | What it means for a recorded call | How you comply |
|---|---|---|
| Lawful interception (RICA) | Recording a call is legally an interception. You may record a call you are a party to, and monitor business calls, provided you take reasonable steps to tell people. | Announce recording at the start of every call, on every line. |
| Lawful basis (POPIA s11) | You need a ground to process the recording: consent, performance of a contract, a legal duty, or a legitimate interest that is not overridden. | Write down which ground applies to which call type, before you record. |
| Purpose limitation | You may only use the recording for the purpose you gave (quality, training, dispute evidence), not repurpose it later. | State the purpose in your notice and your privacy policy, and stick to it. |
| Security safeguards (s19) | Recordings are personal information and often contain card or ID data. They must be protected against loss and unauthorised access. | Encrypt at rest, restrict who can play back, log every access. |
| Retention limitation (s14) | You cannot keep recordings forever. Hold them only as long as the purpose or a law requires. | Set an automatic deletion schedule per call type and enforce it. |
| Data subject rights (s23, s24) | A caller can ask what you hold, ask for a copy, or ask you to delete it. | Be able to find one caller’s recordings quickly and act on the request. |
Recording every call because everyone does, with no announcement, no chosen lawful basis and no deletion schedule, is three POPIA failures and a RICA one in a single habit. The fix is an afternoon of paperwork, not a new system.
WhichVoIP editorial
The recording compliance checklist
Work through these seven steps once, then audit them quarterly. This is the recording-specific companion to our broader POPIA compliance checklist for call centres.
What to ask a platform before you trust it with recordings
Compliance is your responsibility, but the right platform makes it far easier. These questions separate a recording feature from a compliance-ready capability.
Ask whether consent announcements can be configured per queue and language; whether retention and automatic deletion are built in per call type or left to you; whether playback access is role-based and logged; whether recordings are encrypted at rest; and where, physically, the audio is stored. A platform that answers these cleanly is doing half your POPIA work. One that cannot is quietly handing the risk back to you. This is the compliance layer generic feature comparisons skip, and it belongs on your shortlist alongside the capabilities in our guide to call centre software features that matter.
Our verdict
Call recording is entirely lawful in South Africa and genuinely valuable for quality, training and dispute evidence. What makes it a liability is treating it as a technical feature instead of a two-law compliance obligation. Get RICA right with a clear announcement, get POPIA right with a documented basis, secure storage, a retention limit and a way to honour data subject rights, and your recordings become defensible assets instead of a breach waiting to be found.
Need a recording-ready call platform?
Tell us your call volumes and compliance needs. We will line up quotes from SA providers whose recording, retention and access controls are built for POPIA, not bolted on.
Frequently asked questions
Do I need consent to record a call in South Africa?
What must the recording announcement say?
How long can I keep call recordings under POPIA?
Does POPIA apply if my recordings are stored overseas?
What is the penalty for non-compliant call recording?
Is this the same as the general POPIA checklist?
Keep reading
Sources: POPIA (Protection of Personal Information Act 4 of 2013), sections 11, 14, 19, 23, 24, 72 and the administrative-fine provisions; RICA (Regulation of Interception of Communications Act 70 of 2002), party-to-communication and business-purpose provisions; Information Regulator (South Africa) guidance. Verified 7 July 2026.