Binding law — in force AI-adjacent law
No decision with legal or substantial effect may rest solely on automated profiling, save with representations and information on the logic (POPIA s. 71)
South Africa's POPIA provides that a data subject may not be subject to a decision with legal consequences or substantial effect based solely on automated processing of personal information intended to profile them, including their performance at work, creditworthiness, reliability, location, health, personal preferences or conduct (s. 71(1)). The bar does not apply where the decision is taken in connection with a contract and the person's request was met or appropriate measures protect their legitimate interests, or where a law or code of conduct specifies appropriate measures (s. 71(2)). The appropriate measures must give the person an opportunity to make representations about the decision and require the responsible party to give them sufficient information about the underlying logic of the automated processing (s. 71(3)). Detect a model output that becomes a decision about a person with no representations route and logic explanation, and no human decision.
Trust and provenance not reviewed by a lawyer · audit-grade · source verified 3 Oct 2026 · release 2026.10.03.3
- Lane
- Binding law — in force In force: applies since 1 Jul 2020
- Official source
- s. 71(1) (no decision based solely on automated profiling) · captured 3 Oct 2026 · anchor hash (SHA-256)
83e90c27b636…· 6 more anchors in the data release - Verification
- Quoted text found word for word in the captured official document (3 Oct 2026). Source last verified 3 Oct 2026: checked against the captured official document; not in the weekly watcher's list; checked against the captured document.
- Data release
- Data release 2026.10.03.3, data as of 3 Oct 2026, schema 0.3.9.
- Legal review
- Not reviewed by a lawyer. TwinEthos derived this rule from the official text it cites: treat it as research to check against that text; it is not legal advice. No TwinEthos rule has been legally reviewed yet. Open questions for counsel on this rule: 1.
- Audit standard
- Audit-grade: meets all 10 checks of the TwinEthos audit standard that apply to it. The audit standard is TwinEthos's own quality bar for provenance, dates, applicability, detectors, fixtures, remediation and licences; it is not a legal review.
- Detectors
1 detector (data flow), experimental: written from the rule's text and not yet measured for precision on real code, so treat a hit as a lead to verify.
Known limits:
- Measures specified in a code of conduct and applied outside the code
- Decisions that are not based solely on automated profiling, or have no legal or substantial effect, are outside s. 71.
Who it applies to
- Duty falls on: controller
- Systems covered: automated decision, consequential decision
- Responsible parties whose decisions with legal consequences or substantial effect on a data subject rest solely on automated profiling, where POPIA applies (s. 3(1)(b): a responsible party domiciled in the Republic, or not domiciled there but using automated or non-automated means in the Republic). s. 71 commenced on 2020-07-01 and processing had to conform within one year (s. 114(1)), by 2021-07-01. Whether a juristic person is a data subject here ('him, her or it') and what makes an effect 'substantial' are counsel questions.
- Not covered:
- Processing in the course of a purely personal or household activity, de-identified information, listed public-body national-security and law-enforcement processing, the Cabinet and Executive Councils, and judicial functions of courts (s. 6(1))
- Whether it applies depends on facts outside the code; a person has to decide.
The guard to add
Route significant automated decisions through meaningful human review, or wire in an automated-decision notice, reasons, human intervention, a way to give a view, and contest.
At the point where model output becomes a significant decision about a person (approve, deny, underwrite, set_status), either queue the case for a reviewer who weighs the evidence and can change the outcome before it takes effect (review_queue.enqueue, requires_human_review), or, where the decision stays solely automated, record the permitted basis for that decision type and wire the safeguards in. Those safeguards are a notice in the decision message that it was made by automated processing, reasons the person can read, and request_human_review or contest routes where the person can give their view and have a human reconsider. A reviewer who approves every case without examining it does not make the decision non-automated, so the review records reviewer identity, the evidence viewed, and the outcome.
Where it goes: 1 application source code, 9 AI output handling, 15 agent action surface, 14 user-facing text.
What this provision adds:
- Where a solely automated profiling decision relies on the contract exception, let the person make representations about it and give them enough information about the underlying logic to do so.
Example (Python + OpenAI SDK), before:
verdict = client.chat.completions.create(model=MODEL, messages=msgs).choices[0].message.content
if verdict.strip() == 'deny':
deny(applicant)
send_decision_email(applicant, 'Your application was not approved.')After:
out = client.chat.completions.create(model=MODEL, messages=msgs,
response_format={'type': 'json_object'})
result = json.loads(out.choices[0].message.content)
if result['decision'] == 'deny':
if requires_human_review('credit'): # a person decides
review_queue.enqueue(applicant.id, proposal=result)
else: # solely automated, recorded basis
deny(applicant, basis=DECISION_BASIS['credit'], reasons=result['reasons'])
send_decision_email(applicant, render('adm_denial.txt', notice=ADM_NOTICE,
reasons=result['reasons'], contest_url=f'{BASE}/decisions/{applicant.id}/contest'))Control: Solely-automated significant decision without human-intervention safeguards. The same guard addresses 15 items with binding law in 15 jurisdictions. Engineering guidance, not legal advice.
Related incidents
No guardrail sits on this exact control; these incidents are cited by guardrails on related controls.
- UnitedHealth nH Predict claim-denial litigation (2023-11; alleged (not proven)). A class action filed in November 2023 alleges that UnitedHealth's nH Predict model had a 90% error rate, measured by denials reversed on appeal, while only about 0.2% of members appealed. UnitedHealth disputes the allegations; the litigation is ongoing. Source: STAT News · evidence grade: primary · cited by Monitor how often adverse AI decisions are reversed, and suspend models that are usually wrong
- Cigna PXDX batch claim denials (reported) (2022; alleged (not proven)). ProPublica, citing internal Cigna records, reported that Cigna's PXDX system was used to reject more than 300,000 claims over two months in 2022, with physicians spending an average of 1.2 seconds on each. Cigna disputes the reporting; related lawsuits are ongoing. Source: ProPublica / The Capitol Forum · evidence grade: press of record · cited by Make human review of adverse AI decisions substantive, not nominal
Rule id za-popia-s71.automated-profiling-decision-representations-and-logic · review status: primary source derived