POPIA & PAIA, explained
One right to privacy. Two manuals it makes you write.
POPIA and PAIA don't just ask for documents, they create legal duties, a named role inside your business, and a compliance cycle that keeps going after the manuals are delivered. Here's exactly what that means.
01
The Constitution
Section 14 (privacy) and Section 32 (access to information)
02
The Acts
POPIA (2013) and PAIA (2000) give effect to those rights
03
The Manuals
Your POPIA Manual and PAIA Manual, the written record of compliance
04
The Role
A named Information Officer, registered with the Regulator
05
The Cycle
Review, respond, train, and back to the manuals
The last step points back to the manuals, this isn't a document you file once. It's a cycle you maintain.
This isn't a once-off deliverable
The manuals are the starting document, not the finish line. POPIA and PAIA both expect ongoing action, not a policy that sits in a drawer.
Annually
Review and version-update both manuals to reflect any change in how the business processes personal information.
As they arrive
Log and respond to data subject access, correction or deletion requests within the statutory timeframe.
Per new hire
Onboard new staff with POPIA awareness training and record their sign-off.
On readiness
Keep a tested data breach response plan, with notification templates ready to use, not drafted after the fact.
Per new vendor
Review and sign an operator agreement whenever a new third party will process personal information on your behalf.
Ongoing
Keep the Information Officer's registration and details current with the Information Regulator.
Important: lawvero (Pty) Ltd provides document-preparation and compliance-support services and does not provide legal advice. This page is general information on South African law current as at July 2026. Key legislation: Protection of Personal Information Act 4 of 2013; Promotion of Access to Information Act 2 of 2000. © lawvero (Pty) Ltd 2026 · law, verified.