security & trust

Built for
the procurement review.

Public records, retention, audit, and data sovereignty are first-class concerns at Civagent — not afterthoughts. Here is exactly how each one is handled.

Request a security review→Browse compliance documents

Why this matters

Government data is different. Constituent records, financial disclosures, permit history, FOIA holdings, meeting minutes — these are public trust assets governed by law, not just policy. A vendor that treats them like enterprise SaaS data will get a jurisdiction sued, fined, or in the press.

Most AI tools in market today were built for commercial use. Their default posture sends your data to a foundation model provider, retains conversation history for product improvement, and offers no audit trail a clerk could hand to a state archivist or a judge.

Civagent’s posture is the inverse. Your data stays in your tenant. Nothing trains a foundation model. Every action an agent takes is written to a tamper-evident audit log. Retention windows and legal holds are configured at the tenant level and enforced in the database, not by policy.

We design for the procurement officer, the CISO, and the records clerk before we design for the demo.

Our posture

The specific things government cares about.

01
SOC 2
Controls mapped to the SOC 2 Trust Services Criteria — security, availability, processing integrity, confidentiality, and privacy — with the audit posture documented in the open.
02
NIST 800-53
Controls mapped to NIST SP 800-53 Rev. 5 — the baseline federal civilian agencies and most state and local jurisdictions reference in procurement.
03
Audit log
Every agent action — read, send, decision — written to an append-only, cryptographically verifiable log. Append-only alone is not enough.
04
Retention
Per-tenant retention, configurable per record type. Conversations, agent actions, and uploaded files each have their own clock, enforced in the database.
05
Legal hold
Place a hold on a conversation, user, or agent and the retention clock stops. Standard practice for litigation, FOIA disputes, and internal investigations.
06
Sovereignty
Your tenant, your data. Nothing trains a foundation model. No third-party sharing. Hosted on infrastructure you can name in a contract.

How agents are built

Human in the loop

Agents draft, recommend, and prepare. Staff approve. Every consequential action passes through a human reviewer — by default and by design.

Your data stays yours

Civagent does not train foundation models on your data. We do not share it with third parties. Your tenant is isolated, and your records belong to your jurisdiction.

Explainable decisions

Every answer traces back to its source. Every action is logged with the prompt, the tool calls, and the outputs. Nothing is a black box, and nothing has to be.

Government rules first

Records law, FOIA, retention, legal hold, archive — we treat these as primary requirements, not edge cases. The product is shaped by how government actually works.

Documentation

The library.

Procurement officers and security reviewers should not have to ask for a PDF. Civagent’s compliance documentation — security policy, data handling, sub-processor list, incident response — is published and current.

Browse compliance documents→

For security teams

Bring the hard questions.

We’d rather answer them on a call than in a one-pager. Tell us what your CISO, your clerk, or your records officer needs to sign off, and we’ll walk through it directly.

Request a security review