POPIA Compliance
Documentation in progress. This page describes technical controls relevant to POPIA (Protection of Personal Information Act); it is not a POPIA compliance certification. The carrier deploying Hoziron remains the responsible party under POPIA — Hoziron provides mechanisms, the carrier owns the compliance determination, including appointing an Information Officer and registering with the Information Regulator.
Current capabilities
The platform provides technical controls relevant to POPIA's conditions for lawful processing:
- Purpose limitation (§13) — Competency-level permissions and required-skill declarations restrict what tools and data each agent can access; unsatisfied contracts block an agent from activating at all.
- Information security (§19) — Optional native TLS termination, IP/CIDR allowlisting, RBAC, and a tamper-evident audit trail. Note: a surface's own listener can terminate TLS directly (
[surfaces.<name>.tls]), or TLS can be terminated at a reverse proxy in front of it — either way, POPIA §19's "appropriate technical measures" is the carrier's determination based on its deployment topology. - Data minimization — PII is tokenized before it crosses an agent or LLM boundary; hydration to real values requires an explicit rule in the operator-owned PII policy (
carrier-pii-policy.toml), not an agent-level setting an agent author can loosen. - Operator accountability (§8) — The Merkle-hash-chained audit trail records every authenticated API operation and is independently verifiable, supporting an operator's ability to demonstrate what happened to a given piece of personal information.
- Data sovereignty — Air-gapped deployment with local-only models keeps data on infrastructure the carrier controls. Hoziron does not host or route data outside the deployment the carrier chooses; if the carrier hosts on South African infrastructure and disables cloud providers, data does not leave that infrastructure — Hoziron does not itself guarantee or enforce a specific hosting jurisdiction.
- Cross-border transfer control (§72) — The PII policy's
local_onlydesignation lets an operator mark specific PII types (e.g. SA ID numbers, bank account numbers, medical records) as never permitted to leave the box, even in tokenized form, regardless of which LLM provider is otherwise configured.
Coming soon
- POPIA-specific configuration guidance and worked examples
- Information Officer notification/reporting templates
- Cross-border data transfer documentation aligned to §72 conditions
- Impact assessment framework
Related: