POPIA and AI: what South African businesses need to know
POPIA — South Africa's Protection of Personal Information Act — applies to your business the moment you put customer, employee or supplier information through an AI tool. The Act does not mention AI, and it does not need to: it governs the processing of personal information, and pasting a client's details into a chatbot is processing. The practical obligations are ordinary ones — have a lawful reason, use it only for that reason, keep it secure, and know where it goes.
This article is general information, not legal advice. It is written from the perspective of a registered Information Officer working with small businesses, to help owners ask better questions. For advice on your specific circumstances — particularly if you handle large volumes of personal information, or special personal information such as health, biometric or children's data — consult a qualified attorney or privacy professional.
Does POPIA apply when I use AI tools?
Yes, if personal information is involved. POPIA governs the processing of personal information by a responsible party in South Africa, and "processing" is defined broadly — collecting, storing, using, sharing, even just viewing. Typing a customer's name, email address, ID number or account history into an AI assistant is processing that information.
The Act is technology-neutral. It does not care whether the processing happens in a spreadsheet, a CRM or a language model. What matters is that personal information about an identifiable person is being handled, and that you can justify how.
Note also that POPIA's definition of personal information extends further than many owners expect — it includes information relating to identifiable juristic persons (companies), not only natural persons.
What is an Information Officer, and why does registration matter?
Every responsible party in South Africa has an Information Officer. By default it is the head of the organisation — the business owner, in most small businesses — whether or not anyone has thought about it. The role can be delegated to deputies, but the default sits at the top.
The Information Officer is accountable for the organisation's compliance: encouraging compliance with the Act's conditions for lawful processing, dealing with requests made to the organisation, working with the Information Regulator on investigations, and generally making sure the business does what POPIA requires.
Information Officers must be registered with the Information Regulator, which is done through the Regulator's online portal. Registration is free.
Why it matters in practice: it is a low-effort signal that the business takes its obligations seriously, and it forces someone to actually own the question. In my experience the registration itself is not the valuable part — the valuable part is that somebody in the business now has the job of noticing when personal information is about to be handled carelessly.
Disclosure: Phantom Ops (Pty) Ltd is registered, and I am the registered Information Officer. That is why I can write this — not a claim that registration alone makes any business compliant.
What does POPIA actually require?
The Act sets out eight conditions for the lawful processing of personal information. In plain terms, and as they bear on AI use:
| Condition | What it means when you use AI |
|---|---|
| Accountability | Someone in the business is responsible. Using a third-party tool does not transfer that responsibility. |
| Processing limitation | You need a lawful basis, and you should use the minimum information necessary. Pasting an entire client file when a summary would do is hard to justify. |
| Purpose specification | Collect for a specific, stated purpose. "We might use it for AI things later" is not a purpose. |
| Further processing limitation | Using data for something new must be compatible with why you collected it. Feeding customer records into a tool for an unrelated reason is where businesses drift. |
| Information quality | Keep it accurate. AI output can be confidently wrong — if it writes something inaccurate about a person into your records, that is now your inaccurate record. |
| Openness | People should know what you do with their information. If AI processing is a meaningful part of that, your privacy notice should say so. |
| Security safeguards | Reasonable technical and organisational measures. This is the condition most directly stressed by casual AI use. |
| Data subject participation | People can ask what you hold, and ask for correction or deletion. You need to be able to answer — which is hard if information has been scattered into tools nobody tracks. |
What's the actual risk with pasting customer data into consumer AI tools?
Three practical concerns, none of them exotic:
1. You may not know where it goes, or how long it stays
Consumer-grade tools often retain conversations, and some use submitted content to improve their services unless you are on a plan or setting that says otherwise. Business and enterprise tiers commonly offer different terms. The obligation to know this sits with you, not the employee who pasted the file.
2. It is often a cross-border transfer
Most of these services process data outside South Africa. POPIA places conditions on transferring personal information across borders — broadly, there must be an appropriate basis, such as comparable protection at the destination, consent, or necessity for the contract. This does not make foreign tools unusable. It does mean it should be a considered decision rather than an accident.
3. It is invisible
This is the one I see most. Nobody approved it, nobody documented it, and if a customer exercised their right to ask what you hold about them, nobody could answer accurately. The compliance failure isn't the tool — it's that the business genuinely does not know what has been sent where.
What are sensible guardrails for a small team?
You do not need a formal governance programme. For most owner-run businesses, a single page that everyone has actually read beats a policy nobody opens. Cover:
- What must never be pasted into a general AI tool. Be specific and concrete: ID numbers, banking details, medical information, anything about a child, full customer databases. A named list works better than "sensitive data".
- Which tools are approved, and on which plan. "ChatGPT" and "ChatGPT on our business account" are different answers.
- Default to de-identifying. Most tasks work perfectly with "a customer" instead of a name. If the output doesn't need the identity, the input shouldn't carry it.
- Written agreements with anyone processing on your behalf. Where a supplier processes personal information for you, POPIA requires that relationship to be governed by a written contract with security obligations.
- Say it in your privacy notice if AI processing is a meaningful part of how you handle personal information.
- Keep a simple record of what goes where. A short list beats perfect documentation that never gets written.
- Human review before anything about a person is acted on. Both an accuracy safeguard and a fairness one.
The single highest-value change for most small businesses is the de-identification habit. It removes most of the risk, costs nothing, requires no new software, and barely affects the quality of the output. If you only do one thing from this article, do that one.
Does this mean my business should avoid AI?
No — and treating POPIA as a reason to avoid AI is its own kind of mistake. The Act does not prohibit processing; it requires that processing be lawful, purposeful and secure. Plenty of high-value AI work touches no personal information whatsoever: drafting general content, summarising public documents, internal reporting on non-personal figures, market research.
The right posture is neither "no AI" nor "paste everything and hope". It is deciding, up front, which categories of information may go where — and then designing the systems so the safe path is also the easy one. Compliance that depends on everyone remembering to be careful will fail eventually.
Where can I check the official position?
The Information Regulator (South Africa) publishes guidance, registration facilities and enforcement information at inforegulator.org.za. For anything consequential — a breach, a complaint, large-scale processing, or special personal information — get proper legal advice rather than relying on an article.
Want the data question handled properly from the start?
Every Phantom Ops AI Opportunity Audit covers what data a proposed system would touch and what the rules around it should be — before anything is built. Phantom Ops is a registered POPIA Information Officer.
Book your AI opportunity audit
Teeanu "Teejay" Thomas
Founder of Phantom Ops (Pty) Ltd, an AI transformation partner in Johannesburg, South Africa. Registered POPIA Information Officer with South Africa's Information Regulator (Reg. 2026-061581). Writes on AI, operations and data responsibility for South African businesses.
Sources
- Protection of Personal Information Act 4 of 2013 (POPIA), South Africa — conditions for lawful processing; Information Officer duties; transfers outside the Republic.
- Information Regulator (South Africa) — Information Officer registration and published guidance.