0
Immutable workflow entries
Append-only ledger — update & delete blocked by the database
This page is maintained by the CitiZone team to answer the security, privacy and compliance questions municipalities, NGOs and residents ask before trusting a civic platform. It describes controls that are actually enabled in the product — it is not an independent certification.
0
Immutable workflow entries
Append-only ledger — update & delete blocked by the database
0
Public audit trail entries
Readable by anyone on the open-data portal
0
Registered territories
Each territory isolates its own civic data
Email/password and Google sign-in with leaked-password screening (HIBP) enabled. Sessions are short-lived and refreshed with rotating tokens.
Roles (authority, manager, citizen) are stored in a dedicated table and evaluated server-side by a security-definer function — never in the browser.
Every civic table enforces row-level policies scoped to the signed-in user and their territory. Private evidence media lives in a non-public bucket behind signed, expiring URLs.
Data is encrypted in transit with TLS 1.2+ and at rest with AES-256 on managed Postgres and object storage. Media is never served from a public bucket.
Status changes, assignments and escalations are appended to a workflow ledger that the database blocks from being updated or deleted — history cannot be rewritten.
Territory statistics, public works and the civic action trail are readable by anyone through the open-data portal, without exposing personal data.
Exercise your rights
Export or delete your civic data from Profile & settings, or write to privacy@citizone.africa. We answer within 30 days.
Read the public audit trail, budget execution and works progress without an account — or report a vulnerability to security@citizone.africa. We acknowledge reports within 72 hours and never pursue good-faith researchers.