Security

How Civil 360 protects project data, stated as it is today.

Draft for legal review. This text has not yet been approved by a lawyer and may change before it takes effect. Questions: help@civil360.app.

Access control

Row-level security is enabled on every table in the Civil 360 database. Each person reads only the companies, projects and departments they belong to. Changes go through database functions that check the person's role before they run.

Money and approvals

Project books are double-entry, append-only and hash-chained, with periods that lock. Payments are marked confirmed only when matched to a bank or mobile-money record. Approvals keep who approved, when and what changed.

Files

Documents, evidence, HR and compliance files are kept in private storage buckets. Access follows the same project and role rules.

Authentication

Sign-in uses an email code or password, with a passcode to unlock on your device. Company accounts are approved by Civil 360 before they open.

AI

The Civil 360 Assistant receives only what the person's role may see. It cannot post journals, approve or pay. Numbers it explains come from the database.

Certifications

Civil 360 does not currently hold ISO 27001, SOC 2 or similar certifications, and has not yet completed an independent penetration test. We will publish these here if and when they are obtained.

Reporting a vulnerability

Email help@civil360.app with the subject "Security". Please do not access other customers' data.

Last updated 19 November 2026.