Authenticated access
Application access is designed around authenticated users, tenant/workspace context and role-aware workflows rather than public project records.
Trust Centre
Trust should be inspectable.
CivilQuant handles commercially sensitive built-environment information. Our public trust position is therefore based on explicit controls, evidence provenance and claims we can defend—not certification theatre.
Trust model
Govern the evidence before you govern the AI.
Evidence lineage
Source documents, revisions, measurements, assumptions, formulas and approvals are intended to remain linked to controlled outputs.
Reviewer gates
Professional or monetary decisions should not silently become authoritative merely because an AI model proposed them.
Deterministic calculation
Authoritative arithmetic belongs in recomputable, unit-aware calculation logic rather than free-form model generation.
Private working data
Project and asset evidence is treated as private application data unless a user deliberately publishes or exports it.
Operational traceability
Review states, evidence relationships and issued outputs are designed to support audit and incident investigation.
Responsible AI
Automation should become stronger only when its controls become stronger.
| Area | Public position |
|---|---|
| AI interpretation | Useful for extraction, classification, matching, summarisation and exception prioritisation. |
| Calculation | Material numerical outputs should be produced or verified through deterministic logic. |
| Professional opinion | Formal opinions remain subject to appropriate professional responsibility and engagement terms. |
| Research | Experimental capabilities are labelled as research or preview until production controls are ready. |
| Certification claims | CivilQuant does not claim ISO 27001, SOC 2 or another certification unless the certification is explicitly documented and current. |
Procurement
Need a security questionnaire, data-flow discussion or deployment review?
Use the contact channel for enterprise security, privacy, integration and procurement questions. Deployment-specific controls should be confirmed in the executed agreement rather than inferred from marketing copy.