Security and trust

Built to stay out of CUI and out of your government accounts.

Our agents read public data and your shared mailbox, draft the work and stop. People log in, sign and submit. That one rule shapes everything below.

Isolation
One environment per customer
CUI
None held, by design
Gov logins
Never held or used
Safeguards
FAR 52.204-21 basic safeguards
SOC 2
Type I planned for 2027

Boundaries

What agents may do, with care, and never

Allowed

  • Read public SAM.gov, DIBBS, USAspending and award data through official sources
  • Read the shared mailbox you connect
  • Draft emails, quotes, invoice packets, renewals and proposal sections in your Microsoft 365
  • Prepare files for a person to upload

With care

  • Your awards, orders and forwarded RFQs: kept in your environment only, never reused for others
  • Every rep, price, claim and invoice routed to a named approver
  • Each solicitation checked for instructions on AI use

Never

  • Hold or use your government logins, keys or certificates
  • Log in, submit, sign or certify
  • Download CUI, drawings or controlled attachments
  • Use competitor proposals or source-selection information

How it works

Security in detail

Your own environment

  • Every customer gets a separate server (or, for Essential and Standard agents only, a separate container), with its own agents, database, files, secrets and backups. Customers never share a process or a database.
  • Your dashboard sits behind Cloudflare Access at your own address, for example yourcompany.govconagents.ai, with every agent you use inside it. Staff sign in with their work email and a one-time code; only your email domain is allowed. No customer server is exposed to the internet.
  • Backups run nightly, are encrypted with a key unique to you, and are restore-tested every month.

Microsoft 365 permissions

  • Your admin runs our setup script in your own tenant. It creates a single-tenant Teams app and an app for one shared mailbox, limited to that mailbox with Exchange RBAC for Applications.
  • Agents read and draft in that one mailbox and answer in Teams chats where they are mentioned. They cannot read other mailboxes, files or chats.
  • You own these apps and can revoke them at any time, which stops every agent immediately.

AI model and your data

  • Agents use an AI model through a business API under terms that do not train on your data. We request zero data retention from the provider.
  • Your data is used only to do your work. It is never used to draft another customer's work or to train a model.
  • The Managed option keeps AI processing in the United States.

Government systems

  • We never hold your DIBBS, SAM.gov, PIEE/WAWF, eBuy, SPRS or CPARS credentials, keys or certificates, and agents never log in to them.
  • Public government data comes through official APIs and downloads under our own accounts, within published limits. Logged-in systems reach agents only through emails you forward to your mailbox.
  • Every submission, signature and certification is made by a named person on your team.

CUI and export control

  • Agents work only with public data and documents without CUI markings. They never download drawings, technical data packages or controlled attachments.
  • Files marked Distribution B–F, CUI, ITAR or EAR are refused and flagged to you. Customers agree not to share CUI or export-controlled technical data.
  • Holding no CUI keeps the service out of DFARS 7012 cloud requirements and out of CMMC Level 2 scope as a service provider.

Audit and oversight

  • Every draft, status change and tool call is logged with its reason and visible in your dashboard.
  • Every representation, price, past-performance claim and invoice packet goes to a named approver before it leaves.
  • Changes to how an agent works are proposed in Teams and applied only after an approver says yes; each change is versioned and can be undone.
  • Whatever name you give an agent, its email signature labels it as an AI assistant, so suppliers and agencies always know.

Compliance roadmap

Where we are and what comes next

NowFAR 52.204-21 basic safeguards for federal contract information; legal pages in placeattestation available to customers
2027SOC 2 Type I report, then Type II 6–9 months laterwe will publish the report date here
CloudsMicrosoft 365 Commercial and GCC tenants supported; GCC High under studyapps cannot cross national clouds

Report an issue

Security contact

To report a security concern or ask for our security questionnaire answers, email [email protected] with "Security" in the subject. We acknowledge reports within one business day.

Read more in our data processing agreement, AI disclosure and acceptable use policy.

See an agent work on your own data

A 30-minute call. We show you what the DIBBS Agent finds in today's DIBBS feed, or walk you through the agents coming next.

Book a demo