Ask a South African business owner what governs their AI use and you will usually get a shrug, or a reference to something they read about Europe. Both assume the rules are still coming.
They are not. POPIA — the Protection of Personal Information Act 4 of 2013 — has been in force since 1 July 2020. Its long title states, in its own words, that it exists to provide for "the rights of persons regarding unsolicited electronic communications and automated decision making" and "to regulate the flow of personal information across the borders of the Republic".
Automated decision making. Cross-border data flows. Both phrases were written into the Act in 2013, seven years before a South African business could buy an AI receptionist for the price of a monthly phone contract. The law got there first.
What exists, and what does not
The national AI policy is a draft. It was published in Government Gazette No. 54477 on 10 April 2026 as Notice 3880 of 2026, out for public comment. Anyone selling you "AI compliance" against a South African AI Act is selling you a draft.
POPIA is different. It is in force: its substantive provisions commenced on 1 July 2020, with the remainder on 30 June 2021. It sets eight conditions for lawful processing in section 4(1), detailed in sections 8 to 25 — accountability, processing limitation, purpose specification, further processing limitation, information quality, openness, security safeguards, and data subject participation. All eight apply to an AI system the moment it touches a customer's name, number, email address or ID number.
The section almost nobody has read: section 71
This is the part that should change how you design an agent, and it is the part that gets skipped.
Section 71(1) says that a data subject "may not be subject to a decision which results in legal consequences for him, her or it, or which affects him, her or it to a substantial degree, which is based solely on the basis of the automated processing of personal information intended to provide a profile of such person".
Three words carry the weight: solely, substantially, profile.
The prohibition is not against using AI. It is against letting a machine decide something that matters about a person, with no human in the loop and no way to push back. Section 71(3) sets out what the escape hatch requires: an opportunity for the data subject to make representations about the decision, and enough information about "the underlying logic of the automated processing" for them to make those representations.
In plain language: if your system decides something that substantially affects a customer, you owe them a route to argue with it.
Where a South African business actually trips this
- Fully automated rejection. An agent that silently declines a booking, declines a claim, or declines credit without a human confirming it. If the decision is based solely on automated processing and it substantially affects the person, section 71 is live.
- Lead and applicant scoring. A system that profiles someone — reliability, spending, location, likely value — and then acts on that profile without a human making the call. Section 71(1) names the categories that matter: performance at work, credit worthiness, reliability, location, health, personal preferences or conduct. If your scoring touches those and the output is automatic, you are in the section.
- Cross-border transfer, quietly. Section 72(1) states that a responsible party "may not transfer personal information about a data subject to a third party who is in a foreign country" unless one of the listed bases applies — most commonly that the recipient is bound to an adequate level of protection substantially similar to POPIA's own conditions. If your agent, chatbot, CRM enricher or transcript service runs outside South Africa, you transfer personal information out of the country every time a customer's details pass through it. Having no idea which of section 72's bases you rely on is the problem.
Section 73 closes the loop: non-compliance with section 71 or 72 is expressly an interference with a data subject's personal information — and interference is what switches on the Regulator's enforcement powers. And there is no published guidance note on AI yet: the Regulator's notes cover direct marketing, elections, special personal information, children's information and exemptions. Something as recent as the 2026 draft national AI policy is still a draft out for comment. So the Act itself is the design brief. Absence of guidance is not permission.
The three questions you will be asked after a breach
- Did you take reasonable measures? Section 19 requires "appropriate, reasonable technical and organisational measures" to secure personal information, with safeguards that are identified, maintained, regularly verified and updated. An AI vendor's security page is not your section 19 answer; your own documented measures are.
- Did you notify, and how fast? Section 22 says that where there are reasonable grounds to believe personal information has been accessed by an unauthorised person, you must notify both the Regulator and the affected data subject, "as soon as reasonably possible after the discovery of the compromise". Two audiences, one clock.
- Can the customer sue you? Section 99(1) lets a data subject bring a civil action for damages "whether or not there is intent or negligence on the part of the responsible party", and section 99(3) lets a court award aggravated damages, interest and costs.
That is the exposure. Section 109(2)(c) caps an administrative fine at R10 million, and section 107(a) makes the most serious listed offences, including failing to comply with an enforcement notice, punishable by a fine or imprisonment of up to 10 years, or both. Those are ceilings, not typical outcomes. The Regulator's own media statements list records an infringement notice and a R5 million administrative fine against the Department of Justice and Constitutional Development — half the maximum, and against a government department rather than an SME. The civil-action route has no cap at all.
The check we run, and what it costs
Our Intelligence audits are a fixed R2,500 each — SEO and site, competitor intelligence, and ICP research — delivered as a written report, not a deck to interpret.
For the sections above, the useful step is not another report. It is forty minutes with an operator, in front of your own list of systems, naming which transfers need a section 72 basis and which automated decisions fall inside section 71. That is the R7,500 Assessment: three audits, a 40-minute diagnostic, and a prioritised written map of what to fix first and what each fix is worth — credited 100% to any build, so it works as a deposit.
One boundary: this tells you where you stand against the Act. It is not a legal opinion and it does not replace your attorney — it just means you are not paying specialist fees for someone to discover where your customer data goes. If you would rather start free, the Digital Presence Check costs R0, and our agents are built with these sections in mind by default: an agent that books a human-confirmed slot is a very different POPIA risk profile from one that silently turns people away.
The four things to do this week
- List every AI tool that touches customer information — including transcripts, enrichment and scheduling tools, not just the obvious ones.
- Next to each one, write where the data physically goes. If the answer is another country, you now have a section 72 question to answer.
- Find every decision your systems make without a human confirming it, and ask whether it substantially affects the person on the other end. If it does, you need a route for them to make representations, per section 71(3).
- Write down your breach procedure, with both audiences — the Regulator and the customer — and a defined "as soon as reasonably possible" clock.
None of that is expensive — most of it is an afternoon and a spreadsheet. Discovering the answers for the first time during an investigation is what gets expensive.
Book the R7,500 Assessment and we will map where your customer data actually goes, name the transfers needing a section 72 basis, and put it in writing alongside the rest of the diagnostic.