Compliance
Recording customer calls in Kenya: what the Data Protection Act means for your call centre
By the V4N team · Published · 3 min read
The short answer
Under Kenya's Data Protection Act, 2019, a call recording is personal data, because a voice identifies a person. In February 2026 the Office of the Data Protection Commissioner found that recording a person's voice without consent was unlawful and awarded compensation. In practice: tell callers at the start of the call, state a specific purpose, restrict who can listen, set and enforce a retention period, and know where recordings and any speech-AI processing are held. This is general information, not legal advice.
What changed
Kenya's Data Protection Act, 2019 is enforced by the Office of the Data Protection Commissioner (ODPC). In February 2026 the ODPC decided a complaint against Liquid Telecommunications Kenya Ltd, finding it had processed an employee's voice recording without consent and awarding KSh 700,000 in compensation. As reported by Capital FM, the regulator treated the recording as personal data.
That case concerned an employee, not a customer, but the reasoning applies to any recorded call: a voice is data about an identifiable person, so the rules on consent, purpose and security apply to it.
A checklist for your call centre
- Tell people before you record. Play a short notice at the start of every call, on inbound and outbound, in the languages your callers use. Keep a record of the wording and the dates it was in use.
- State a specific purpose. "Quality, training and dispute resolution" is a purpose; "business reasons" is not. Do not reuse recordings for a new purpose without checking.
- Limit who can listen. Give playback and download to named roles only, and keep a log of who played what and when. A recording nobody can account for access to is a liability.
- Set a retention period and enforce it. Decide how long each kind of call is kept, and delete automatically afterwards. "Forever" is the default most centres have, and the hardest to defend.
- Be able to find a person's calls. A person may ask what you hold on them. Can you search all calls from one phone number, today, in minutes?
- Know where recordings live. Check where they are stored and whether any of it leaves Kenya. The Act has rules on transfers outside the country, so get this answered in writing by your provider.
- Treat speech-AI vendors as processors. If audio goes to a transcription service, that service handles personal data for you. You need an agreement with it and a clear view of what it keeps.
- Check your registration. Controllers and processors may need to register with the ODPC. Confirm your position and whether large-scale recording calls for an impact assessment.
Questions to put to any call-recording vendor
- Where are recordings stored, and can we choose, including our own storage bucket?
- Can we set retention per queue or call type, and does deletion actually remove the file?
- Is every playback and download logged, with who and when?
- Which roles can hear recordings, and can that be restricted by team?
- Which speech or AI services process the audio, under whose account, and do they keep it?
- Can we export or delete everything held about one phone number?
Those questions are also how to check your own setup. If you cannot answer them for the system you run today, that is the first thing to fix. For how V4N answers them, see our security and data section.