Policy version register
This register identifies the policy documents presented during registration and re-attestation. Each acceptance record stores the document versions, stated purpose and acceptance evidence. A material change advances at least one version and triggers re-attestation before protected Gazette material is released.
Current change summary. Expanded responsible-party disclosures; clarified Gazette-source and authentication processing; added retention, rights and complaints procedures; strengthened professional-use obligations; and introduced an archived policy version register.
| Document | Current version | Effective | Status |
|---|---|---|---|
| Terms of Use | 2026-07-v2 | 15 July 2026 | Current |
| Privacy Notice | 2026-07-v2 | 15 July 2026 | Current |
| Professional and POPIA responsible-use attestation | 2026-07-v2 | 15 July 2026 | Current |
Superseded version 2026-07-v1
The initial prototype policy set is preserved for users whose historical acceptance records refer to version 2026-07-v1.
| Document | Version | Status |
|---|---|---|
| Terms of Use | 2026-07-v1 | Superseded |
| Privacy Notice | 2026-07-v1 | Superseded |
| Responsible-use attestation | 2026-07-v1 | Superseded |
How re-attestation works
- The administrator publishes revised text and advances the applicable version property.
- Existing acceptance records remain unchanged as historical evidence.
- At the next sign-in or protected request, a user with an older bundle is redirected to the re-attestation page.
- The user reviews the change summary and current documents, confirms the stated purpose and separately accepts or acknowledges each document.
- A new acceptance record and audit event are stored; the earlier record remains available.