Skip to content

Data Handling and Agreements

This page covers who touches your data, what you must not send us, when we tell you about an incident, and which agreements apply to regulated work.

For who is responsible for what, read Shared Responsibility. For how scores are calculated, read SPRS Scoring.

Do not upload Controlled Unclassified Information (CUI), Covered Defense Information (CDI), or Federal Contract Information (FCI) to GovConHouse at this time.

GovConHouse’s hosting environment has not been authorized or assessed for CUI. DFARS 252.204-7012 places requirements on any system that stores, processes or transmits covered defense information, and GovConHouse does not meet them today.

This matters for ordinary-looking actions. Uploading a solicitation attachment or a past performance write-up is fine if the content is not CUI. The same action with a CUI-marked document is not. If your workflow needs a tool that holds CUI, talk to us before you start.

This list matches the Subprocessors page and the Privacy Policy. It is grouped by when a provider is used.

Always used

Provider Purpose
Supabase Primary database
Fly.io API and background job hosting
Vercel Web application hosting
Upstash Job queue and cache
Anthropic AI processing of solicitation and proposal text when AI features run
OpenAI Text embeddings for search
Stripe Payments
Our email delivery provider Account and notification email
Cloudflare Hosting for the documentation, help, and compliance sites (no account data)

Used only if enabled

Provider Purpose
Twilio Phone verification at signup
PostHog, Plausible, Sentry Product analytics, web analytics, and error monitoring, only when enabled and, where required, with your consent
Google Firebase Cloud Messaging Push notifications
DeepSeek Alternate AI provider, off by default

Integrations you connect

Google Workspace, Microsoft 365, Slack, Microsoft Teams, HubSpot, Salesforce, and DocuSign receive data only when your company connects them, and only the data your configuration calls for.

An authorization held by one of these providers does not transfer to GovConHouse, and does not reach you through GovConHouse. If you need an authorized service, you need one that is itself authorized.

Changes to this list are governed by the Data Processing Agreement.

Obligation Window Whose
GovConHouse notifies affected customers 24 hours from confirmation Ours, by contract
Defense contractor reports a cyber incident to DoD 72 hours from discovery (DFARS 252.204-7012) Yours

If you are a defense contractor, note these two windows run on different clocks: ours starts when we confirm, yours starts when you discover. Your obligation to the Government is yours regardless of when we notify you.

Audit records are append-only. The database rejects attempts to modify or delete them, and each record is hash-chained to the one before it so out-of-band alteration is detectable rather than silent. Audit records are retained for security and compliance; there is no automatic purge today.

This exists so that if you are asked to show who changed a control state and when, the answer is evidence rather than assertion.

If you operate under CMMC or other federal security obligations, these govern your use. Contact us for current copies before putting regulated work on the platform.

Agreement Covers
Terms of Service (Customer Agreement) The baseline commercial terms
Data Processing Agreement Roles, sub-processors, data location, retention, deletion, breach notification
CMMC Addendum That you hold your own certification, flow-down, evidence handling, and how our 24-hour customer notice and DoD’s 72-hour reporting window interact
Supplemental Terms That GovConHouse holds no authorization, that no control may be inherited from it, and the boundary on what the OSCAL export features do

Why there is an addendum at all, given GovConHouse holds no certifications: not holding a certification settles what we may say. It does not settle what happens if you rely on an artifact the platform produced. The addenda exist to make that allocation explicit rather than leaving it to be argued later.

To request a copy of your data or deletion of your account, email support@govconhouse.com. Support handles these requests within 30 days. On termination, deletion follows the Customer Agreement and the Data Processing Agreement.

Whether a specific workflow puts your data in scope depends on your contracts and your data. That deserves a real answer rather than a documentation page. Ask us.