The short version: POPIA does not prohibit AI. It requires that personal information is processed lawfully, for a defined purpose, with appropriate safeguards, and that any transfer outside South Africa meets section 72. The practical consequence is that identifiable client information should not go into consumer AI tools, and AI features used in a practice should either run inside the practice or receive only de-identified information.
The roles
- Responsible party. The FSP. It decides why and how client information is processed and carries the accountability condition.
- Operator. Anyone who processes personal information for the responsible party under a contract, such as a software vendor with access to the data. Operators must have a written agreement and adequate security, and must notify the responsible party of any compromise.
- Data subject. The client, and also spouses, dependants and beneficiaries who appear in the file.
An AI provider that receives identifiable client information is an operator, and an overseas one triggers section 72 as well. An AI provider that receives only de-identified facts is, in POPIA terms, not processing personal information at all, although a careful practice still records the arrangement.
The conditions that bite
- Processing limitation and minimality. Send only what the task needs. A needs analysis needs the client's age, dependants, income, assets and cover; it does not need their name, identity number or address.
- Purpose specification and further processing. Information gathered to advise a client may not be used to train a model or for anything unrelated. Check the provider's terms: business APIs from the major providers commit not to train on customer data; consumer chat tools often do not.
- Security safeguards (section 19). Appropriate, reasonable technical and organisational measures. For AI tools this means access control, encryption in transit, an audit trail of what was sent, and a written policy.
- Cross-border transfer (section 72). Personal information may only leave South Africa if the recipient is bound by law or binding agreement to substantially similar protection, or the data subject consents, or the transfer is necessary for the contract, among other grounds. A consumer AI account typically satisfies none of these in a documented way.
- Special personal information. Health details in meeting notes (medical history relevant to cover) carry stricter rules. Keep clinical detail out of what leaves the practice.
De-identification as the design principle
POPIA does not apply to information that has been de-identified so that it cannot reasonably be re-identified. That makes de-identification the cleanest way to use a cloud AI model for analysis and drafting. Done properly it means:
- Identity fields are removed before anything is sent: name, identity number, date of birth, email, phone, address.
- Those values are also scrubbed from free text, because a summary that says "Ms Fortuin, a conveyancer in Sea Point" identifies the client as surely as a field does.
- The model works with placeholders, and identity is put back inside the practice.
- The process is tested, not assumed. A practice should be able to show what the model received for a given case.
This is how Tallify is built: document reading and extraction run on the practice's own server on local models; only a de-identified set of facts goes to the drafting model; identity is substituted locally; and an automated test asserts on every change that no identity string survives into the outbound data.
Practical rules for a practice
- No client information in consumer AI chat tools, on any device, by anyone. Write it into the acceptable use policy.
- Any AI tool used with client data must be either on-premise, or contracted as an operator with an agreement that covers security, no training on your data, and breach notification, or receive de-identified information only.
- Record AI processing in the practice's POPIA processing records and mention it in the client privacy notice.
- Keep a log of what was sent to any external model, by whom and when.
- The adviser reviews and signs everything AI drafts. No communication goes to a client without a named person approving it.
- Communications consent is captured and enforced: no automated client updates without a recorded yes.
- Retention follows FAIS (five years minimum for advice records) and the practice's own schedule; AI drafts that were superseded can be deleted.
- Test the de-identification once and then every time the tool changes.
This guide is a practical summary, not legal advice. The practice's information officer and compliance officer remain responsible for its POPIA programme.
Questions
Can I paste client notes into ChatGPT to write a Record of Advice?
Not if the notes identify the client and the tool processes the data outside South Africa on terms you have not assessed. Using a consumer AI chat with identifiable client information typically fails the section 72 transfer conditions and the safeguards condition. Using a business API with a proper agreement and de-identified data is a different matter.
Is de-identified information still personal information under POPIA?
POPIA does not apply to information that has been de-identified to the extent that it cannot be re-identified again. Removing names, identity numbers, dates of birth and contact details, and scrubbing them from free text, is the standard; the practice should be able to show how it is done.
Who is the responsible party when a practice uses Tallify?
The practice. Tallify runs on the practice's own server; BlueBird Digital, which builds it, only becomes an operator if the practice grants access for support. The drafting model provider processes de-identified facts only.
Do I need client consent to use AI in producing their advice?
Processing for the advisory relationship rests on the contract and the FAIS duties, not on consent, so consent is not the lawful basis for drafting. Consent matters for communications: a practice should only send automated updates to clients who have agreed to receive them. Transparency still applies: tell clients in your privacy notice that AI tools are used and how their information is protected.