South Africa: POPIA & FAIS/FSCA
Evidence requirements for South African financial-services organizations using AI-generated output: POPIA's automated decision-making safeguards and the FAIS General Code of Conduct's accountability for advice and client communications. Generic and enterprise-wide: any AI artefact with legal or client effect gets a named, organization-attested human reviewer.
Pack metadata
The default clause applies to review requests that name no clause and match no scope. That is what makes activating the pack organization-wide plug-and-play.
Clauses
Each clause maps a legal obligation to the attestation evidence that satisfies it: an allowlist of accepted review kinds, a minimum signer tier, and whether the attestation must carry a named signer role.
| Reference | Clause | Obligation | Accepted review kinds | Min signer tier | Named role |
|---|---|---|---|---|---|
| POPIA s 71(1)-(3) | Automated decision-making safeguardspopia-s71 | A decision with legal or similarly significant effect on a data subject may not be based solely on automated processing; the responsible party must provide for meaningful human intervention and review. | reviewed, revised, endorsed, rejected | Org attested | Required |
| FAIS General Code of Conduct s 7(1) | Accountable advice and client communicationsfais-gcoc-s7 | Financial services must be rendered with due skill, care and diligence, and records of advice must identify the provider or representative accountable for the advice given to the client.scopes: advice, client-communication, financial-advice | reviewed, revised, endorsed | Org attested | Required |
| FSCA outsourcing & operational-risk guidance | Demonstrable oversight of outsourced and automated functionsfsca-oversight | An accountable institution remains responsible for functions performed by systems or third parties on its behalf and must be able to demonstrate effective oversight of them.scopes: oversight, monitoring | reviewed, endorsed | SSO verified | No |
Immutability
This published version never changes. The canonical JSON is what attestations reference via policy_uri, and it resolves, byte-identical, forever. Amendments ship as a new version of the pack, published alongside this one; see governance.