Municipal systems accumulate documents: proof of residence, affidavits, ID copies, burial records, asset photographs. This is where they live, how they are protected, and how long they are kept.
A scanned affidavit belongs to an application, not to a shared drive somebody has to search. Every upload is attached to the record it supports.
Files are encrypted in storage and in transit, with keys held in a managed key service rather than in the application.
Who opened which citizen document, and when. Personal information under POPIA needs an access trail, not just a password.
Records have different lifespans. Retention is configured per document type rather than everything being kept forever by default.
Automated backups with a retention window, and restores we have actually run. An untested backup is not a backup.
Citizen documents are stored in the AWS Cape Town region, which is what POPIA and municipal data sovereignty policy require.
Storage comes with the systems that need it rather than being bought separately.
Supporting documents for every application, attached to the household and the verification that used them.
Burial records, plot documents and the photographs that go with a grave site.
Condition photographs and supporting paperwork against each asset in the register.